Define routing rules across providers and regions. Requests automatically fall over to healthy backends when upstreams degrade, time out, or rate limit.
Funktionsöversikt
multi
providers per model
live
health-aware routing
1 flow
no client code change
Nyckelvärdepunkter kopplade till praktiska produktionsflöden.
Fördel
01
Reduced single-provider risk
When one upstream goes down, traffic shifts to fallback providers instead of impacting your end users.
Fördel
02
Latency-aware routing
Prefer providers with the lowest observed latency and success rate over a rolling window.
Fördel
03
Per-model routing rules
Tune routing priority, fallback chain, and timeout policy independently for each model.
En enkel 3-stegsväg för att integrera denna funktion i gateway-anrop, routningspolicy och faktureringskontroller.
Steg 1
Define route
Map each model id to a primary provider plus an ordered fallback chain.
Steg 2
Set policy
Pick timeouts, retry limits, and health thresholds that match your latency and reliability budget.
Steg 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.
Nästa steg
Börja från dokumentationen, modellkatalogen eller instrumentpanelen och validera denna funktion med riktig produktionstrafik.