Model routing
Not every request needs your most expensive model. Contextwaise judges how hard each request is and tells you whether another approved model fits better.
What it does#
You list the models you approve. For each request, Contextwaise rates the task as simple, standard or advanced from the question and your instructions, then compares the cost of staying on your current model with switching, including the one-time cost of a cold prompt cache.
Turn it on#
Add models (2 to 10 approved models, any mix of providers) and send the model you call today in model. system, outputTokens and promptTokens are optional and sharpen the estimate.
Each model must be in the catalog or priced in Settings → Models. Provider prefixes and date suffixes are accepted, such as anthropic/claude-sonnet-5.
Read the advice#
switch: whether to change model. Follow this, not the tier alone.model: the model to use. The recommended one whenswitchis true, otherwise yours.message: a one-line explanation you can log or show internally.estimate: cost per turn staying and switching, the one-time switch cost, and how many turns it takes to pay back.
Reasons#
| Reason | Advice | Meaning |
|---|---|---|
cheaper_fits | Switch | A cheaper approved model handles this as well. |
needs_bigger | Switch up | The task looks harder than your current model handles well. |
long_context | Keep | The prompt is long: losing its cache would cost more than switching saves. |
already_best | Keep | Your current model is already the best fit. |
unsure | Keep | The request couldn't be judged confidently. |
no_current_model | Keep | Send model so a switch can be priced. |
Switching and the prompt cache#
A new model reads the whole prompt once without cache. Contextwaise only advises a switch when cheaper turns repay that cost within 3 turns of a conversation, or within the request itself when there is no conversation id.
With a conversation id, the tier is decided once and kept for the whole conversation. Avoid switching models mid-conversation on your own: it loses the prompt cache and, on newer Claude models, the reasoning so far.
Rolling it out#
- Send
modelsand keep calling your usual model. - Watch the Model routing card on the dashboard's Overview for what following the advice would save.
- Follow
route.modelfor one agent first, then widen.