- AI Gateway
- next
- Gateway Artifacts
- LLM Provider
LLM provider¶
An LLM Provider represents a connection to an AI backend service such as OpenAI, Azure OpenAI, or other LLM APIs. Platform administrators configure LLM Providers to define:
- The LLM Provider Template
- The upstream LLM service URL
- Authentication credentials (API keys, tokens)
- Access control rules for which endpoints are exposed
- Budget control policies, such as token-based rate limiting
- Organization-wide policies such as guardrails
Once configured, the LLM Provider allows traffic to flow through the gateway to the AI backend.
Who configures this¶
Platform administrators own LLM providers. An administrator holds the upstream credentials, decides which endpoints the provider exposes, and sets the organization-wide policies that every LLM proxy consuming the provider inherits.
In this section¶
Every template the gateway ships has a provider page under Supported Providers. Three of them — OpenAI, Anthropic and AWS Bedrock — carry a fixed upstream URL, the authentication the provider expects, and a definition you can deploy as it stands. For the other four, the endpoint and the credential belong to your own account or resource, so those pages name what to obtain and link the provider that defines it. A further page covers a service with no shipped template at all. Provider templates is the reference for what each template extracts.
This section contains the following pages:
| Page | What it covers |
|---|---|
| Create and configure an LLM provider | Create an LLM provider on the AI Gateway: choose a template, set the upstream URL and credentials, deploy it with the management API, and test the connection. |
| OpenAI | Connect the AI Gateway to OpenAI: the upstream URL, API key authentication, the endpoints the provider exposes, and a request that tests the connection. |
| Azure OpenAI | Connect the AI Gateway to Azure OpenAI: the values your Azure resource supplies, what the azure-openai template extracts, and OpenAI-format compatibility. |
| Anthropic | Connect the AI Gateway to the Anthropic Messages API: the upstream URL, x-api-key authentication, and the endpoint the provider exposes. |
| Gemini | Connect the AI Gateway to the Gemini API: the values Google supplies, what the gemini template extracts, and OpenAI-format compatibility. |
| MistralAI | Connect the AI Gateway to the Mistral AI API: the values Mistral AI supplies, what the mistralai template extracts, and OpenAI-format compatibility. |
| AWS Bedrock | Connect API Platform AI Gateway to AWS Bedrock using a bearer API key or AWS Signature Version 4 authentication, then invoke a model through the gateway. |
| Azure AI Foundry | Connect the AI Gateway to Azure AI Foundry: the values your Foundry resource supplies, and what the azureai-foundry template extracts from responses. |
| Custom provider | Connect the AI Gateway to an LLM service with no shipped template: define an LlmProviderTemplate of your own, deploy it, and create a provider that uses it. |
Related guides¶
- Set up a governed multi-model LLM proxy — adds Azure OpenAI as an LLM provider, then distributes requests across models behind a single proxy.