Cloud models
Routing & failover
Named models
Name a model id and exactly three things can happen: it serves your request, it refuses with a typed error, or you get a 402. There is no configuration under which the gateway substitutes a cheaper model behind a 200. Check the receipt yourself: on a named request, x-conifer-effective-model always equals x-conifer-requested-model.
Failover
A production-router admission may include a same-model fallback seat. If execution advances along that immutable admitted chain, the route reason reads provider_failover. If no admitted seat can serve the exact model, the request fails rather than substituting one.