Supported model providers

Model Gateway supports the provider types below. Available models depend on the provider account, region, credentials, and the catalog your organization enables.

Provider	Connection	Discovery and constraints
OpenAI	API key; optional approved endpoint override	Discovers the provider’s model catalog. Supported operations depend on the model.
Anthropic	API key; optional approved endpoint override	Claude through the Messages API. Azure AI Foundry Claude uses the Anthropic provider type and its resource’s `/anthropic/v1` URL; register deployments by name.
OpenRouter	API key	Discovers OpenRouter models. Upstream capability and pricing vary by model.
Amazon Bedrock	AWS region and an AWS credential, or deployment identity	Uses native Bedrock inference. Access depends on the region, model permissions, and any inference profile.
Google Vertex AI	Project and location URL; service account or deployment identity	Discovers Gemini models and uses native Gemini inference. Claude deployments use `anthropic/<model>@<version>` and are registered explicitly.
Google AI	API key	Uses Gemini’s OpenAI-compatible endpoint.
Azure OpenAI / AI Foundry	Resource’s OpenAI v1 endpoint and API key	Uses the resource endpoint and deployment names. Claude uses the Anthropic connection above.
OpenAI-compatible	Approved `/v1` base URL and API key	Uses the server’s OpenAI-compatible contract; support varies by server and model.
LiteLLM proxy	Proxy root URL and API key	Discovery reads `/model/info`. Use a key that can list the intended models and configure proxy aliases for the upstream model IDs.
TypeSafe	API key	Decision models only. It does not serve chat, embedding, or media requests.

OpenAI

OpenAI-compatible client setup

Anthropic

Messages client setup

OpenRouter

Model capabilities and limits

Amazon Bedrock

Native provider translation

Google

Vertex AI and Google AI

Azure

Azure resource endpoints

LiteLLM

Proxy catalog and inference

TypeSafe

Typed decisions

Catalog administration

Organization administrators can use Providers → Add a provider in the Model Gateway studio. The form changes to the selected provider type. It collects the endpoint and credential fields that provider requires. Custom endpoints must be allowed by your deployment. After connecting a provider, inspect Models before updating clients. Disable a provider to stop its models from routing; disable an individual model to stop only that model. Refresh discovery when the upstream catalog changes. Discovery does not prove that every listed model supports every API operation.

Verify a connection

With the application’s agent key, list models through the gateway, copy an exact id, and make one request for its modality. A successful upstream sign-in or provider discovery alone does not verify inference. See Connect a client and Model Gateway errors.

Skill management

Agent management

Agent monitoring

AI Gateway

Context

OpenAI

Anthropic

OpenRouter

Amazon Bedrock

Google

Azure

LiteLLM

TypeSafe

Catalog administration

Verify a connection

OpenAI

Anthropic

OpenRouter

Amazon Bedrock

Google

Azure

LiteLLM

TypeSafe

​Catalog administration

​Verify a connection

Catalog administration

Verify a connection