# What is model routing?

Model routing is directing each AI request to the best model for it through one stable endpoint. Your code calls a route name; the platform decides which model serves it. Swapping models then requires no deploy, and one workload can blend cheap fast models with frontier ones by policy.

Routing decouples product code from model choice. When a better or cheaper model ships, you change the route’s target in a console, not your codebase, and your P95 latency, cost, and accuracy are compared on live traffic.

On Allocate, route names ride the model field of an OpenAI-compatible API, so adopting routing is a one-line change from any existing client.

## See also

- [Browse the model catalog](https://allocate.network/models)

## Related terms

- [Inference](https://allocate.network/glossary/inference.md)
- [Tokens](https://allocate.network/glossary/tokens.md)
- [Inference latency](https://allocate.network/glossary/latency.md)
- [MoE routing](https://allocate.network/glossary/moe-routing.md)
- [LLM gateway](https://allocate.network/glossary/llm-gateway.md)

---

[HTML page](https://allocate.network/glossary/model-routing) · [Machine-readable catalog](https://allocate.network/catalog.json)