The same routing logic that powers every copilot in the product is available directly through the API, for teams that want routing decisions without a full copilot session.
Every industry copilot in 9xAI relies on the Model Router to decide which underlying model actually handles a given request. For most integrations, this happens automatically as part of a copilot session and never needs direct attention. For teams building more custom integrations — ones that want routing decisions without the full context of a copilot session — the router is also available directly through its own API.
A copilot session bundles routing together with domain-specific context, conversation history, and session management. That's the right shape for most integrations. But some use cases genuinely just need a routing decision on its own — for example, a custom pipeline that wants to classify incoming requests by complexity and cost before deciding how to handle them elsewhere, without needing a full conversational session wrapped around that decision.
The Model Router API accepts a request description — the task itself, along with any relevant metadata about domain, cost sensitivity, or risk tolerance — and returns the model selected for that request, along with the reasoning behind the selection: which factors weighed most heavily in that specific routing decision.
This mirrors exactly what happens inside a copilot session automatically, just exposed as a standalone call for integrations that need that decision on its own rather than as part of a larger conversational flow.
Most teams don't need this level of direct control — letting a copilot session handle routing automatically is the simpler and usually correct choice. Direct router access is most useful for teams building genuinely custom AI infrastructure on top of 9xAI, where routing needs to be one step in a larger pipeline they're designing themselves, rather than bundled inside a conversational session. Full parameters and response formats are documented alongside the rest of the platform's endpoints in the API Reference.