For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
Resources
Log inGet a demo
GuidesAPI reference
GuidesAPI reference
    • Get Started
  • Features
    • Projects
    • Cost Governance and Savings
      • Overview
      • Single Provider
      • Priority
      • Performance
      • Intelligent
    • Context Compression
UnifiedAgent HandlerGateway
UnifiedAgent HandlerGateway
Resources
Log inGet a demo
FeaturesRouting Policies

Priority

Deterministic multi-provider failover in priority order.

Was this page helpful?
Previous

Single provider

Next

Performance strategies

Built with

The Priority strategy tries providers in the order you define. If the first provider fails (timeout, rate limit, 5xx error), the request automatically goes to the next provider in line.

In the API, this strategy uses "type": "fallback" inside default_strategy. The dashboard refers to it as Priority.

Best for: High availability setups and automatic recovery from provider outages.

1{
2 "name": "HA Priority",
3 "default_strategy": {
4 "type": "fallback",
5 "providers": [
6 { "provider": "openai", "model": "gpt-5.2", "priority": 1 },
7 { "provider": "azure", "model": "gpt-5.2", "priority": 2 },
8 { "provider": "anthropic", "model": "claude-sonnet-4-20250514", "priority": 3 }
9 ]
10 }
11}

Requests go to the highest-priority provider (lowest priority number). On failure, Gateway automatically retries with the next provider in the list, continuing until a provider succeeds or all providers are exhausted.

Gateway tracks provider health automatically — if a provider accumulates failures, it is temporarily skipped so requests aren’t wasted on a provider that’s down.