/**
 * Azure OpenAI connector.
 *
 * Azure exposes the OpenAI Chat Completions dialect, but behind a different URL
 * layout and a different auth header than vanilla OpenAI: requests go to a
 * per-deployment path on the resource endpoint, the model is selected by the
 * deployment name baked into that path (not a `model` body field), and the key
 * travels in an `api-key` header rather than a bearer token. An `api-version`
 * query parameter pins the contract.
 *
 * Because the body/SSE shape is identical to OpenAI's, this is a thin adapter:
 * it resolves the resource key, composes the deployment URL, and hands the wire
 * work to the shared {@link streamOpenAICompatibleChat} streamer. All request
 * assembly, SSE decoding, and chunk→emission translation live there.
 *
 * Serves: any catalog card whose `api` is `azure-openai` (provider `azure`).
 * The deployment segment is taken from `model.id`, so each card's id must match
 * the Azure deployment it targets.
 */
import type { Connector, CredentialResolver } from "../contract";
/** Dependencies this connector pulls from the gateway runtime. */
export interface AzureOpenAIDeps {
    /** Resolves the Azure resource key, honoring a per-call override. */
    readonly resolveSecret: CredentialResolver["resolve"];
}
/**
 * Build an Azure OpenAI {@link Connector}.
 *
 * The lone dependency is the credential resolver (typically
 * `environmentCredentialResolver.resolve`), injected so the connector stays
 * free of ambient environment access and is trivial to fake in tests.
 */
export declare function createazureopenaiConnector(deps: AzureOpenAIDeps): Connector;
