Group failover

Configure fallback routes and check which route served a request.

A regular API key can have a primary group and an ordered list of fallback groups. This lets eligible requests try another permitted route when a route cannot serve them.

Configure fallback groups

  1. Create or edit a regular API key, select a primary group and configure its fallback groups in the desired order.
  2. Each selected group must be available to your account. Confirm model coverage and prices for both the primary and fallback groups.
  3. Save the key. Keep the same key and model in your client, then inspect request logs to see the route that actually served the request.
Fallback can change the price

A request served by a fallback group uses that group’s applicable billing rate. A fallback route is not a promise that every error can be retried or that a partially delivered stream can resume.

Smart API Keys use their own routing strategy across available groups instead of a manually ordered fallback list.