Which AI providers does Cognocient support?
Cognocient proxies 7 AI providers through a single base_url. Change the model name to switch providers — no separate SDK, no re-authentication, no new keys.
Cognocient proxies 7 AI providers — OpenAI, Anthropic, Google Gemini, Mistral, Groq, Together AI, and Azure OpenAI — through a single base_url. Change the model name to switch providers with no separate SDK, no re-authentication, and no new keys.
Provider overview
| Provider | Supported models | Model name prefix |
|---|---|---|
| OpenAI | GPT-4o, GPT-4o-mini, o1, o3 | gpt-, o1, o3 |
| Anthropic | Claude 3.5 Haiku, Sonnet, Claude 4 family | claude- |
| Google Gemini | Gemini 1.5, 2.0 Flash, 2.5 Pro | gemini- |
| Mistral AI | Large, Nemo, Codestral, Mixtral 8x22B | mistral-, open- |
| Groq | Llama 3.1/3.3 70B, Gemma 2, Mixtral | llama, mixtral, gemma (via Groq) |
| Together AI | Llama 3.1, DeepSeek, Qwen, 100+ OSS models | Full Together AI model names |
| Azure OpenAI | GPT-4o, GPT-4 via Azure deployments | Configured via deployment name in Settings |
One client, all providers
All providers use the same base_url. Cognocient detects the provider from the model name and handles any format translation automatically. Switch from GPT-4o to Claude by changing one string.
Quick setup
Replace your api_key and base_url — that's the only change needed.
Native Anthropic SDK
If you use the Anthropic Python or TypeScript SDK directly (not via the OpenAI SDK), the base URL is slightly different — omit /v1:
The /v1 suffix applies to the OpenAI SDK route. For the native Anthropic SDK, use https://api.cognocient.com without a path suffix. Both routes work for routing to Anthropic models.
Switching providers at runtime
All providers share the same client — switch by changing the model name:
Adding your provider API keys
Your provider keys are stored encrypted in Cognocient. Configure them once in Settings → Providers:
- Go to Dashboard → Settings → Providers
- Click Add Provider Key for each provider
- Paste your provider API key — it is encrypted before being stored
- All requests to that provider now use this key automatically
You only need to configure each provider once. To rotate a key, paste the new one and the old is replaced immediately.
Keys are not recoverable after saving
Cognocient does not re-expose stored provider keys. Store your provider keys in a secrets manager independently of Cognocient.
Azure OpenAI: tell us the underlying model if your deployment name doesn't match it
Azure resolves which model actually answers a call purely from your deployment name in the URL — the model field your application sends in the request body is not authoritative, and Azure itself effectively ignores it for routing.
If you named your deployment something like my-prod-deployment rather than the model name itself, Cognocient has no way to know which real model that maps to unless you tell it. When adding or editing your Azure key in Settings → Providers, fill in the Underlying Model field (e.g. gpt-4o) — Cognocient uses that value for cost calculation instead of trusting whatever string your application happens to send.
Leave it blank if your deployment name already matches the model name exactly — Cognocient falls back to the request's own model field in that case, same as before.
Frequently asked questions
Related articles