Msty Nexus Smart Routes Put the Right Model Behind Every Request

Choosing the right model should not slow users down.

As model usage grows across more workflows, manual selection becomes harder to trust. Users need to know which model fits the request, when to switch, and what happens when the selected model is unavailable. That creates friction, inconsistent behavior, unnecessary spend, and avoidable routing risk.

We released Smart Routes to move that decision into Nexus, where routing can be managed request by request without making the user experience more complicated.

With Smart Routes, users choose a route from the same model selector they already use in Msty Studio or Claw, while Nexus handles model selection in the background. This way, you can keep working without having to think about what model to use for your prompts. Just let Nexus decide the best model for you based on the prompt you are sending.

From Model Guesswork to Managed Routing

Model choice is manageable when there are only one or two options. It becomes inconsistent when each request has different requirements.

Without Smart Routes, users and clients have to decide:

• which model fits the request
• when to switch models
• whether speed or deeper reasoning matters more
• when a lower-cost model is enough
• how to recover when the selected model is unavailable

We built Smart Routes to remove that model-selection burden from the user experience.

A Smart Route gives users one route to select, while Nexus uses a route pack to manage the target routes and fallback model. For clients and API workflows, the same route is available as a synthetic model value like @route/research.

A route pack keeps the routing inputs in one place: route name, target model, fallback model, enabled state, and route descriptions.

How Smart Routes Work

When a supported generation request uses a Smart Route, Nexus loads the matching route pack and reviews the request text against the route names and descriptions. The local router classifier chooses the route that best matches the request.

Once a route is selected, Nexus maps it to a concrete model ID and rewrites the request before calling the provider. Users keep one stable route name, while the provider receives a standard request with the selected model.

Smart Routes use a small local router model prepared through Nexus-managed runtime jobs. The router model can run on MLX, llama.cpp, or Ollama.

Smart Routes can be created using OpenAI chat completions, OpenAI responses, and Anthropic messages. Embeddings, token counting, and compact sibling are not supported in Smart Routes at this time because routing depends on request text from generation calls.

Fallbacks and Gateway Control

We built Smart Routes to improve model selection when routing is available and keep requests moving when fallback is needed.

If classification is unavailable, slow, invalid, or selects a target that cannot be used, Nexus falls back to the configured fallback model. That protects requests from missing router models, classifier timeouts, invalid classifier output, unavailable route targets, and requests without routeable text.

Smart Routes also keep the routing boundary inside Nexus. Route metadata is allow-listed, provider credentials stay protected by the gateway, and providers receive the selected model request without the Smart Route configuration.

Why Smart Routes Make Routing Easier to Trust

Smart Routes make routing easier to trust by moving model selection into Nexus, keeping fallback behavior explicit, and making route decisions easier to observe.

With Smart Routes, you get:

• one stable route name for users and clients
• local route classification inside Nexus
• standard model requests sent to providers
• explicit fallback behavior when routing cannot select a usable target
• safer routing boundaries for credentials and route metadata
• route-level visibility without exposing sensitive content

Nexus records safe route decision metadata such as the route pack slug, selected route ID, resolved model ID, provider ID, fallback status, and fallback reason. It does not expose prompt text, classifier output, route descriptions, headers, or credentials.

A Simpler Way to Route Every Request

We built Smart Routes so users don't have to worry about which models to use for the job-to-be-done or to switch between models during their workflows.

With Smart Routes, Nexus makes model selection automatic, keeps fallback behavior explicit, protects the gateway boundary, and gives clearer visibility into route decisions.