Jurisdiction-enforced inferenceAccounts are reviewed per jurisdiction and billed from the first token. No free credits, no promotional tier.Contact us for a quotation

Platform · Reliability

Failover is confined to the eligible set

Failover retries only within the declared jurisdiction.


Confined
Failover scope
Documented
Exhaustion behaviour
Per model
Coverage stated

Region by region

01

Design

How this part works

  1. 01

    Eligible-set failover

    When a provider degrades, the router retries against other providers that pass the same policy. Ineligible providers cannot receive retries. The pool can shrink; it cannot widen past a border.

  2. 02

    Documented refusal semantics

    If the eligible set is exhausted, the request fails with the constraint that emptied it.

  3. 03

    Model and region coverage

    Different models have different in-region coverage. The catalogue states coverage per model and region.

  4. 04

    In-region capacity

    Capacity is planned as headroom inside the boundary. The platform does not offer cross-border spillover.

02

Comparison

Boundary-first routing

Example availability-first gateway

  • Widens the provider pool under load
  • Boundary relaxed by an on-call decision
  • Coverage gaps found in production

Menu Items failover

  • Pool shrinks, never widens
  • Refusal semantics fixed in advance
  • Coverage gaps visible in the catalogue
03

Elsewhere on the platform

Other platform features