Skip to main content
A model provider entry gives the gateway somewhere to send inference, and the credential to send it with. Catalog providers know their own connection details; an OpenAI-compatible endpoint needs a base URL as well.

​
What a provider needs

Most take a name and an API key. The name is not cosmetic — it is what appears in routes and in every trace, so openai-prod will serve you better than OpenAI the first time two entries exist. Some providers do not authenticate with a single key:
Azure Foundry routes through one of four API surfaces, chosen per instance:Foundry OpenAI v1 chat and Foundry OpenAI v1 responses call /openai/v1/..., and Foundry Anthropic messages calls /anthropic/v1/messages. All three ignore API version entirely; only Azure OpenAI deployments uses the classic deployments path and needs it. Pick the surface that matches how the deployment was created in Azure — it decides the path, the request and response shape, and the authentication headers the gateway sends, not just which model names resolve.
Keys are stored encrypted and never shown again. On an existing entry, leaving the key blank keeps the stored one; typing a new one replaces it. Rotating a credential is therefore an edit on the entry, and nothing downstream has to change — applications, policies and access all point at the entry, never at the secret.

​
Contract pricing

Cost in Analytics, on every trace, and in any budget policy is only as true as the rates behind it. By default TrustGate prices traffic at list rates. If you negotiated something else, the reporting is wrong until you say so here. Overrides win wherever they match; the discount covers everything else. A flat contract needs only the discount. Add overrides for the models priced outside it. This matters beyond reporting: a budget policy that stops spend at a threshold is counting with these numbers.

​
Instances

A provider entry holds as many instances as you need — production and staging keys, two Azure deployments, one key per cost centre. Each is configured and tested on its own, and each is selectable independently when routing or an application picks a destination.

​
Prompt caching

Providers differ in what they cache on their own and what a request has to mark. Anthropic and Bedrock cache only what the client marks, OpenAI and Azure cache long prefixes automatically, and Mistral takes a cache key. TrustGate carries the client’s markers to whichever provider answers, and prices cache reads and writes at the rates above. Prompt caching has the full table, including which Bedrock models accept a cache checkpoint.

​
Every provider

These are the providers the gateway knows how to talk to. Anything not listed connects through the Custom Model button, the flow for self-hosted models and vendors that expose an OpenAI-shaped API. The format column is the wire protocol the gateway translates to. It matters in exactly one situation: a provider speaking the openai format accepts an OpenAI-shaped request unchanged, so moving traffic between two of them is a routing change and nothing else.