export declare const CONFIG: { server: string; /** * Where links connect. * * Not the core server: links are carried by their own service, so the SDK holds two * addresses rather than one. */ link: string; healthcheckPath: string; paths: { conversation: { v3: { base: string; }; v4: { base: string; }; v5: { base: string; }; }; history: { chat: { v1: { base: string; }; }; chats: { v1: { base: string; }; }; }; interrupt: { v4: { stop: string; steer: string; }; v5: { stop: string; steer: string; }; }; progress: { v4: { base: string; stream: string; }; v5: { base: string; stream: string; }; }; usage: { policy: { v3: { base: string; }; }; }; jobs: { /** The collection. One job is `${base}/${jobId}`, its cancel `${base}/${jobId}/cancel` and its resume `${base}/${jobId}/resume`. */ base: string; /** The owner's job settings, which live on the user rather than on a job. */ settings: string; }; outreach: { /** The inbox. One delivery's answer is `${base}/${deliveryId}/answer`. */ base: string; }; }; }; export type APIPath = keyof typeof CONFIG.paths.conversation; /** * Which server a link should connect to. * * `linkUrl` names it outright and always wins. Failing that, a `serverUrl` pointing anywhere * other than the hosted core is taken at its word: a self-hosted stack is usually one address, * and sending an API key to a host nobody named would be a worse surprise than a wrong path. * Otherwise it is the hosted link service, which is what the core server used to be and is not. */ export declare function resolveLinkUrl(config: { linkUrl?: string; serverUrl?: string; }): string;