Salesforce MVP Hall of Fame (Shivanath Devinarayanan) · Founded 2022
Model routing
Jev picks which model answers each request. The cheap model gets the easy work. The expensive one earns its cost.
Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio
- 01Models · Claude, Gemini, OpenAI, Bedrock
- 02Agentic systems · Agentforce, CrewAI, ADK, A2A
- 03Agentic memory · Neo4j, Cognee, IndyKite
- 04Automation and voice · n8n, Retell
- 05Deployment and governance · identity, evals, policy, audit
The stack
How we would assemble it.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
The decision
The decision, drawn.
Choice model tier per request from complexity/risk
Jev · Choice
Which model tier should answer this request?
- small
- mid
- frontier
- human
Summarise this 3-line status update for Slack.
- small0.91
- mid0.08
- frontier0.01
- human0.00
The flow
One request, to the model it deserves.
Arrives
A request reaches your gateway
From your app, your agent or an internal tool.
Jev decides
Which tier should answer
Small, mid, frontier, or a person.
Above the line
The chosen model answers
Easy work goes to the cheap model. Jev only picks. It never writes the answer.
Below the line
A larger model or a person
When Jev is unsure, the request goes up, not down.
The job
What has to be true.
Act at 0.90 confidence or higher. Below that, a person or a larger model.
The figure
Builder's figure. Not reproduced by us.
Multiple routers; Vercel: about 13% of paid gateway teams used Jev in 24h
apimodels.app/jev-use-casesJev's two fit passes disagreed here (gap 0.46), so pilot it against your own routing labels.
Who runs it
Who would run this, and what changes.
Example
CTO, Dubai software company with an AI feature
Today: Every request goes to the frontier model, three-line summaries included. The model bill grows with usage, not with value.
After: Simple requests go to a small model and the frontier model earns its cost on the hard ones. You pilot it against your own routing labels first.
For CTOsExample
Platform lead, Riyadh fintech building agents
Today: Engineers pick one model per feature and never revisit it, even when a cheaper one would do.
After: Each request gets one routing decision with a probability you can log. Unsure requests go up a tier.
Financial services
The brief
Name the decision your team makes a thousand times a day.
We read the process and write down where Jev fits, where it does not, and where the line sits.