Model routing

Model routing sends a request to whichever model should actually serve it, rather than hardwiring an application to one specific model. That can mean choosing a cheaper model for a simple task and a stronger one for a complex task, or falling back to a second provider automatically when the first one is degraded or unavailable.

An enterprise that wants to standardize on one credential and one endpoint, while still choosing the most appropriate model for each task or reacting when a provider has an outage, needs routing rather than one model wired directly into every application.

Routing simple classification requests to a smaller, cheaper model and complex drafting requests to a larger one, both reached through the same endpoint with no client code aware of the difference.

In Dynamiq, the AI Gateway resolves a router model slug to whichever provider actually serves it and relays the request, so switching between the models it serves is a one-line change to a model name. The SDK's fallback configuration can also retry a secondary model automatically when the primary one hits a rate limit or a connection error.