import { AgentInfo } from "../signaller/types.js";
import { BrowserApiOptions } from "./types.js";
export type BrowserApi = ReturnType<typeof makeBrowserApi>;
/**
 * each browser peer exposes these functions to the signalling server.
 * each exposed function is like a lever that the signalling server can pull to remotely control the browser peer.
 * thus, the signalling server is really the one calling the shots and driving the webrtc negotiation.
 * think of the signalling server as a traffic cop (with the whistle) commanding each browser peer throughout the negotation process.
 */
export declare function makeBrowserApi<Cable>({ rtcConfigurator, cableConfig, signallerApi, allow, welcome, }: BrowserApiOptions<Cable>): {
    v1: {
        /** somebody wants to join a room you are hosting.. will you allow it? */
        knock(buddy: AgentInfo): Promise<boolean>;
        startPeerConnection(attemptId: string, buddy: AgentInfo): Promise<void>;
        produceOffer(attemptId: string): Promise<any>;
        produceAnswer(attemptId: string, offer: RTCSessionDescription): Promise<any>;
        acceptAnswer(attemptId: string, answer: RTCSessionDescription): Promise<void>;
        acceptIceCandidate(attemptId: string, candidate: RTCIceCandidate): Promise<void>;
        waitUntilReady(attemptId: string): Promise<void>;
        completed(attemptId: string): Promise<void>;
        cancel(attemptId: string): Promise<void>;
    };
};