One integration. Many supported models.
Integrate once. Use the model that fits.
Connect through one authenticated API—or start with the official Go, Python, and command-line clients. Then route canonical messages to any supported text provider and model without adding another provider SDK, credential flow, or request contract to your product.
- Keep one canonical request contract as models change
- Start with HTTP, Go, Python, or the command line
- Keep upstream credentials out of client requests
One endpointRoute across native and compatible provider APIs.
One credentialApplications send a tenant secret, never provider keys.
One contractConsistent request, error, usage, and timeout behavior.
One integration. Choose the exact route.
Choose a model family
Choose an exact model
Claude Fable1 exact model
Claude Haiku2 exact models
Claude Opus3 exact models
Claude Sonnet4 exact models
DeepSeek R11 exact model
DeepSeek V31 exact model
DeepSeek V42 exact models
Gemini7 exact models
GLM-52 exact models
GLM ASR0 exact models
GPT-43 exact models
GPT-58 exact models
GPT Transcribe0 exact models
Grok6 exact models
Grok Build1 exact model
Grok Code3 exact models
Grok Imagine0 exact models
Kimi K23 exact models
Kimi K31 exact model
MiniMax M27 exact models
Muse Spark1 exact model
Qwen4 exact models
SenseVoice0 exact models
xAI STT0 exact models
Choose a provider offering
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings2 routes
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings0 routes
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings0 routes
Provider offerings0 routes
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings0 routes
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings1 route
Provider offerings0 routes
Provider offerings0 routes
No routes match these filters.
Integrate once
Use the API directly or start with a client.
Every integration surface targets the same canonical POST /v2 messages contract. Provider selection changes the route, not the shape your application owns.
- 1Choose an integration
Use ordinary HTTP or an official Go, Python, or command-line client.
- 2Authenticate once
Give the application one client key while provider credentials remain behind the proxy.
- 3Select the model
Use centrally managed defaults or choose a supported provider and model for one request.
Built for the way teams ship
One boundary. Three ways to benefit.
Start with the path closest to your work. Each path reaches the same API, client-key boundary, and supported model catalog.
Turn generated code into a durable integration.
Give coding agents and rapid prototypes one documented request shape instead of accumulating provider SDKs and raw keys.
Start with a copyable requestTest model fit without multiplying integrations.
Compare supported providers behind the same product boundary, then change the route as quality, capability, or product needs evolve.
Compare native providersStandardize access across applications.
Centralize provider credentials, routing validation, usage signals, and client access while product teams keep one contract.
Design an internal gatewayWhat stays stable
Change providers without rebuilding the product boundary.
LLM Proxy owns provider-specific wire contracts, credential handling, route validation, and observable failure behavior so application code can stay focused on the job it performs.
Switch routes, not integrations.
Select a supported provider and model per request, use managed defaults, or update an application-owned model profile without replacing the client contract.
Keep secrets server-side.
Tenant-secret authentication gives each application access without exposing upstream provider keys. Client access can be generated and rotated independently, while managed provider keys are encrypted at rest and explicitly verified before use.
Explore the security boundaryKeep one request and error contract.
Send canonical messages while the proxy maps provider payloads, output limits, timeouts, usage metadata, and provider failures into one documented boundary.
Inspect the API contractUse capabilities the route declares.
Send images or audio, request reasoning or constrained web search, or transcribe audio only when the selected model explicitly publishes that capability.
Inspect model capabilitiesCurrent runtime contract
Providers and model capabilities.
This matrix is generated from the same validated provider registry used by request routing. It describes proxy support—not whether a specific account has configured a provider key.
11Providers
11Publishers
24Families
66Exact models
67Offerings
Anthropicanthropic |
claude-fable-5Claude Fable · claude-fable-5 |
|
Anthropicanthropic |
claude-haiku-4-5Claude Haiku · claude-haiku-4-5 |
|
Anthropicanthropic |
claude-haiku-4-5-20251001Claude Haiku · claude-haiku-4-5-20251001 |
|
Anthropicanthropic |
claude-opus-4-1Claude Opus · claude-opus-4-1 |
|
Anthropicanthropic |
claude-opus-4-1-20250805Claude Opus · claude-opus-4-1-20250805 |
|
Anthropicanthropic |
claude-opus-4-8Claude Opus · claude-opus-4-8 |
|
Anthropicanthropic |
claude-sonnet-4-5Claude Sonnet · claude-sonnet-4-5 |
|
Anthropicanthropic |
claude-sonnet-4-5-20250929Claude Sonnet · claude-sonnet-4-5-20250929 |
|
Anthropicanthropic |
claude-sonnet-4-6Claude Sonnet · claude-sonnet-4-6 |
|
Anthropicanthropic |
claude-sonnet-5Claude Sonnet · claude-sonnet-5 |
|
DeepSeekdeepseek |
deepseek-chatDeepSeek V3 · deepseek-chat |
|
DeepSeekdeepseek |
deepseek-reasonerDeepSeek R1 · deepseek-reasoner |
|
DeepSeekdeepseek |
deepseek-v4-flashDeepSeek V4 · deepseek-v4-flash |
|
DeepSeekdeepseek |
deepseek-v4-proDeepSeek V4 · deepseek-v4-pro |
|
Googlegoogle |
gemini-2.5-flashGemini · gemini-2.5-flash |
|
Googlegoogle |
gemini-2.5-flash-liteGemini · gemini-2.5-flash-lite |
|
Googlegoogle |
gemini-2.5-proGemini · gemini-2.5-pro |
|
Googlegoogle |
gemini-3-flash-previewGemini · gemini-3-flash-preview |
|
Googlegoogle |
gemini-3.1-flash-liteGemini · gemini-3.1-flash-lite |
|
Googlegoogle |
gemini-3.1-pro-previewGemini · gemini-3.1-pro-preview |
|
Googlegoogle |
gemini-3.5-flashGemini · gemini-3.5-flash |
|
Z.AIzai |
glm-5.1GLM-5 · glm-5.1 |
|
Z.AIzai |
glm-5.2GLM-5 · glm-5.2 |
|
Z.AIzai |
glm-asr-2512GLM ASR · glm-asr-2512 |
|
OpenAIopenai |
gpt-4.1GPT-4 · gpt-4.1 |
|
OpenAIopenai |
gpt-4oGPT-4 · gpt-4o |
|
OpenAIopenai |
gpt-4o-miniGPT-4 · gpt-4o-mini |
|
OpenAIopenai |
gpt-4o-mini-transcribeGPT Transcribe · gpt-4o-mini-transcribe |
|
OpenAIopenai |
gpt-4o-transcribeGPT Transcribe · gpt-4o-transcribe |
|
OpenAIopenai |
gpt-5GPT-5 · gpt-5 |
|
OpenAIopenai |
gpt-5-miniGPT-5 · gpt-5-mini |
|
OpenAIopenai |
gpt-5.5GPT-5 · gpt-5.5 |
|
OpenAIopenai |
gpt-5.5-proGPT-5 · gpt-5.5-pro |
|
OpenAIopenai |
gpt-5.6GPT-5 · gpt-5.6 |
|
OpenAIopenai |
gpt-5.6-lunaGPT-5 · gpt-5.6-luna |
|
OpenAIopenai |
gpt-5.6-solGPT-5 · gpt-5.6-sol |
|
OpenAIopenai |
gpt-5.6-terraGPT-5 · gpt-5.6-terra |
|
xAIxai |
grok-4.20-0309-non-reasoningGrok · grok-4.20-0309-non-reasoning |
|
xAIxai |
grok-4.20-0309-reasoningGrok · grok-4.20-0309-reasoning |
|
xAIxai |
grok-4.3Grok · grok-4.3 |
|
xAIxai |
grok-4.3-latestGrok · grok-4.3-latest |
|
xAIxai |
grok-4.5Grok · grok-4.5 |
|
xAIxai |
grok-build-0.1Grok Build · grok-build-0.1 |
|
xAIxai |
grok-code-fastGrok Code · grok-code-fast |
|
xAIxai |
grok-code-fast-1Grok Code · grok-code-fast-1 |
|
xAIxai |
grok-code-fast-1-0825Grok Code · grok-code-fast-1-0825 |
|
xAIxai |
grok-imagine-video-1.5Grok Imagine · grok-imagine-video-1.5 |
|
xAIxai |
grok-latestGrok · grok-latest |
|
Moonshot AImoonshot |
kimi-k2.6Kimi K2 · kimi-k2.6 |
|
Moonshot AImoonshot |
kimi-k2.7-codeKimi K2 · kimi-k2.7-code |
|
Moonshot AImoonshot |
kimi-k2.7-code-highspeedKimi K2 · kimi-k2.7-code-highspeed |
|
Moonshot AImoonshot |
kimi-k3Kimi K3 · kimi-k3 |
|
MiniMaxminimax |
minimax-m2MiniMax M2 · minimax-m2 |
|
MiniMaxminimax |
minimax-m2.1MiniMax M2 · minimax-m2.1 |
|
MiniMaxminimax |
minimax-m2.1-highspeedMiniMax M2 · minimax-m2.1-highspeed |
|
MiniMaxminimax |
minimax-m2.5MiniMax M2 · minimax-m2.5 |
|
MiniMaxminimax |
minimax-m2.5-highspeedMiniMax M2 · minimax-m2.5-highspeed |
|
MiniMaxminimax |
minimax-m2.7MiniMax M2 · minimax-m2.7 |
|
MiniMaxminimax |
minimax-m2.7-highspeedMiniMax M2 · minimax-m2.7-highspeed |
|
Metameta |
muse-spark-1.1Muse Spark · muse-spark-1.1 |
|
Alibabaalibaba |
qwen-plusQwen · qwen-plus |
|
Alibabaalibaba |
qwen3.6-flashQwen · qwen3.6-flash |
|
Alibabaalibaba |
qwen3.7-maxQwen · qwen3.7-max |
|
Alibabaalibaba |
qwen3.7-plusQwen · qwen3.7-plus |
|
FunAudioLLMfunaudio |
sensevoice-smallSenseVoice · sensevoice-small |
|
xAIxai |
xai-sttxAI STT · xai-stt |
|
No models match the selected filters.
4 MiBMaximum JSON request body
25 MiBMaximum input audio
3600 secondsMaximum request work budget
Current support contract
The catalog is the source of truth.
The public matrix is generated from the same validated provider registry used by request routing. It states exactly which providers, models, and capabilities the current proxy release supports.
- Provider and model routes are explicit, validated runtime contracts.
- Unsupported models and capabilities fail before provider dispatch.
- The canonical client contract stays stable while provider adapters own upstream API differences.
- Provider lifecycle, model-onboarding, and hosted uptime commitments are outside the current catalog contract pending an approved support and SLA policy.
One integration, ongoing choice
Start once. Keep choosing the model that fits.
Choose HTTP, Go, Python, or the command line, then use the current model catalog to select the route your product needs.