Define routing rules across providers and regions. Requests automatically fall over to healthy backends when upstreams degrade, time out, or rate limit.
Capability Snapshot
multi
providers per model
live
health-aware routing
1 flow
no client code change
Key value points mapped to practical production workflows.
Benefit
01
Reduced single-provider risk
When one upstream goes down, traffic shifts to fallback providers instead of impacting your end users.
Benefit
02
Latency-aware routing
Prefer providers with the lowest observed latency and success rate over a rolling window.
Benefit
03
Per-model routing rules
Tune routing priority, fallback chain, and timeout policy independently for each model.
A simple 3-step path to integrate this capability into gateway calls, routing policy, and billing controls.
Step 1
Define route
Map each model id to a primary provider plus an ordered fallback chain.
Step 2
Set policy
Pick timeouts, retry limits, and health thresholds that match your latency and reliability budget.
Step 3
Monitor and tune
Inspect provider health and fallback rate in the dashboard and refine rules as traffic shifts.
Upstream timeouts, 5xx responses, rate limit errors, or breaching the health threshold all trigger fallback to the next provider in the chain.
Yes. Per-request and per-key policy overrides let you force a specific provider when needed.
Next Step
Start from the docs, model catalog, or dashboard and validate this capability with real production traffic.