Bring your own endpoint
Your provider account, our wire
Keep the contract and the credits you already have. Change the client once.
Conifer’s catalog is one way to reach a model. This section is the other: you already hold a provider account, and you want it behind the same client, the same key handling, and the same cost receipts as everything else. You paste the credential once; callers keep using CONIFER_API_KEY and never learn which lane served the turn.
What you can bring
| Endpoint | What it is | |
|---|---|---|
| Azure OpenAI | A resource you own on Azure, billed to your Azure agreement. | Azure OpenAI |
| Any OpenAI-compatible server | vLLM, Ollama, LM Studio, or an internal deployment behind your own URL. | OpenAI-compatible |
| Your own machine | Weights on local hardware. No account, no network, no per-token charge. | Run a model |
| Bedrock, Vertex | Not served today. The signing work exists; the lane is not open. | Where they stand |
How a stored key is handled
A pasted key is verified live against the provider before anything is written: if the provider refuses it, nothing is stored and the error names the reason. What is stored is encrypted, and every later read hands it straight to the request. The console and GET /v1/keys only ever show metadata — the provider, the last four characters, and, for Azure, the resource URL. There is no route that reads a stored key back out.
Removing one
DELETE /v1/keys/{provider}, or the same control in the console, drops the row. The next request that would have used it falls back to the ordinary catalog, or fails with a model error if you were naming a deployment that only your resource serves.