Failover

22Failover and routing

A model can have more than one route. When the first provider fails with a server error, a rate limit, or a problem with our account there, the request moves to the next route and you get the answer rather than the error. Whichever route served is the one billed, at its own price, and the response reports provider and fallbacks_tried.

A genuine mistake in your request is not retried. A malformed body or a refusal is returned immediately, because sending it to three more providers only wastes your time.

You can steer this per request with a provider object carrying only or ignore, or set a default in your dashboard. If your preferences leave no usable route, you get 503 rather than a silent substitution.