Use case · Routing
Use Jev for Model Routing
Stop paying frontier-model prices for every request. Let Jev decide which model tier should handle the task.
Input
User request
Structured state sent to the decision layer.
Decision
nano · mid-tier · frontier · human
Which model should handle this request?
4Routes
1Decision
fastPer request
lowerAverage model cost
How it works
Turn the workflow into decisions.
Define the available model tiers.
Describe routing criteria.
Send request state to Jev.
Route to the selected model.
Measure quality and adjust thresholds.
Try this pattern
Which model should handle this request?
state: {
source: "...",
context: "..."
}
question:
"Which model should handle this request?"
pattern:
"Routing"
When not to use Jev
If the task requires open-ended writing, deep synthesis, or novel code generation, keep a generative model in that step. Use Jev around the decision points.