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.
次のステップ
ドキュメント、モデルカタログ、またはダッシュボードから始めて、実際のトラフィックでこの機能を検証してください。