Intelligent Routing for AI Native Apps

A router for every routing strategy.

Start for Free
Model Router

Pin a request to one model

The base building block: one provider, one model. Point a router at exactly the model you want and call it by name.

Model Router
One model, one provider. The base building block.
ProviderAnthropic
Modelclaude-sonnet-4-6
Provider keyorg-default ••••
System messagereplace
request rt_chatbot claude-sonnet-4-6
Weighted Router

Split traffic by weight

Send a percentage of requests to each model. Ideal for A/B tests and gradual rollouts across providers.

Weighted Router
Split traffic by weight. A/B tests and gradual rollouts.
composes Model
gpt-560%
claude-sonnet-4-640%
request weighted gpt-5 · 60% claude-sonnet-4-6 · 40%
Fallback Router

Never drop a request

Try routers in order and fail over automatically when a provider errors or rate-limits, so no request is left behind.

Fallback Router
Try routers in order. Automatic failover across providers.
composes Model
1claude-sonnet-4-6primary
2gpt-5on error
3gemini-2.5-proon error
claude-sonnet-4-6 gpt-5 gemini-2.5-pro
Claude Proxy

Bring your own Claude tools

An Anthropic-native endpoint. Point Claude Code or the Anthropic SDK at Multi Router and route every call.

Claude Proxy
Anthropic-native endpoint. Point Claude Code at your routers.
Anthropic API
# point Claude Code at your router
ANTHROPIC_BASE_URL=https://api.multi-router.ai
POST/v1/messagesAnthropic-native
Codex Proxy

Point Codex at your routers

An OpenAI-compatible endpoint for the Codex CLI and any OpenAI SDK. Swap one base URL and you're routing.

Codex Proxy
OpenAI-compatible endpoint. Point the Codex CLI at your routers.
OpenAI API
# point the Codex CLI at your router
OPENAI_BASE_URL=https://api.multi-router.ai/v1
POST/v1/chat/completionsOpenAI-compatible
Aliases

Switch traffic instantly, with zero downtime

An alias is a stable name your apps call, like prod. Repoint it to any router and the swap is atomic.

  • Your apps call one stable name and never change a line of code.
  • Flip the mapping to a new router in a single atomic step.
  • In-flight requests finish on the old target; new ones hit the new one.
your apps prod
resolves to
live
rt_chatbot claude-sonnet-4-6
prod → flips atomically