Gateway
Bring your own endpoint
Put your own provider account behind the Conifer wire. You keep your credits, your contract and your data path, and your callers keep one client.
Paste the credential once and your callers keep using CONIFER_API_KEY. The provider bills you directly on your own contract and Conifer adds no fee. The receipt header x-conifer-endpoint reads byok:<provider> when your own key served a request and credits otherwise.
| Endpoint | What it is | |
|---|---|---|
| Azure OpenAI | A resource you own on Azure, billed to your Azure agreement, served through api.conifer.build. | Azure OpenAI |
| Bedrock, Vertex | Not served today. | Where they stand |
A pasted key is verified against the provider before it is stored, then kept encrypted. The console and GET /v1/keys show only the provider, its status, the last four characters and, for Azure, the resource URL. DELETE /v1/keys/{provider} removes it.
Azure OpenAI
An Azure OpenAI credential is two values, the resource URL and the key for that resource. You do not register deployments. You name the deployment in the request’s model field.
Save the endpoint
Open the console keys view, pick Azure OpenAI, and paste the resource URL https://{resource}.openai.azure.com/openai/v1 and the Azure API key. The gateway checks the key against your resource before storing it. If Azure rejects the key, the response is a 422 and nothing is stored. For scripts, the same call is PUT /v1/keys/azure with {"api_key":"...","base_url":"https://{resource}.openai.azure.com/openai/v1"}. The credential lives on the gateway, so your callers keep using CONIFER_API_KEY.
Call a deployment
curl https://api.conifer.build/v1/chat/completions \
-H "Authorization: Bearer $CONIFER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "YOUR_DEPLOYMENT_NAME",
"max_tokens": 1024,
"messages": [{"role": "user", "content": "three names for a build cache"}]
}'Set model to the deployment name, or to azure/<deployment>. Your deployments do not appear in GET /v1/models. Give deployments names that differ from catalog models. A deployment named gpt-5.4 would be served from the catalog rather than your resource. Entra ID and managed identity are not available on this self-serve form.
Bedrock & Vertex
AWS Bedrock and Google Vertex are not served through api.conifer.build today. If that blocks you, tell us on the SDK issue tracker.