Define routing rules across providers and regions. Requests automatically fall over to healthy backends when upstreams degrade, time out, or rate limit.
기능 스냅샷
multi
providers per model
live
health-aware routing
1 flow
no client code change
실제 프로덕션 워크플로에 매핑된 주요 가치 포인트.
이점
01
Reduced single-provider risk
When one upstream goes down, traffic shifts to fallback providers instead of impacting your end users.
이점
02
Latency-aware routing
Prefer providers with the lowest observed latency and success rate over a rolling window.
이점
03
Per-model routing rules
Tune routing priority, fallback chain, and timeout policy independently for each model.
게이트웨이 호출, 라우팅 정책, 과금 제어에 이 기능을 통합하는 3단계 경로.
단계 1
Define route
Map each model id to a primary provider plus an ordered fallback chain.
단계 2
Set policy
Pick timeouts, retry limits, and health thresholds that match your latency and reliability budget.
단계 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.
다음 단계
문서, 모델 카탈로그 또는 대시보드에서 시작하여 실제 트래픽으로 이 기능을 검증하세요.