Salesforce MVP Hall of Fame · Salesforce consulting partner since 2010
Model routing
Jev picks which model answers each request. The cheap model gets the easy work. The expensive one earns its cost.
Salesforce consulting partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE, India and US desks
- 01Models · Claude, Gemini, OpenAI, Bedrock
- 02Agents · Agentforce, CrewAI, ADK, A2A
- 03Memory · Neo4j, Cognee, RAG
- 04Identity · IndyKite, SSO, entitlements
- 05Governance · policy, audit, human override
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 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.
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.