Jev model routers and tool routing

Shann³

@shannholmberg

how to add a decision model to your AI workflow 1,000 yes/no decisions can cost around: ~$10 on GPT-6 Astra ~$4 on Claude Opus 5.5 ~$0.04 on JEV use language models for planning, writing and coding, and decision models for decisions a decision model can: > check your agent’s output before it ships > approve a draft or request revisions > route a task to the right agent or tool > classify leads, tickets or comments > score fit, quality or priority > check whether content follows your brand rules > pick an option from a shortlist > decide whether to continue, stop or request a review at a much faster speed as well than any regular LLM here’s how to add one 1. find the decisions in your workflow look for repeated steps that need a choice, classification or score start with one decision you can compare against examples you’ve already reviewed 2. define the question and allowed answers give the model the information and references it needs for a content workflow, that could include your draft, voice DNA file, anti slop rules and approved examples ask it to return a choice such as approve, revise or human review 3. connect the answer to an action your software uses that answer to decide what happens next approved drafts move to your review queue, revision requests return to the writing agent, and uncertain cases go to you 4. test before letting it act compare its answers with your reviewed examples if it returns confidence scores, check whether those scores match how often it gets the decision right start with actions you can easily reverse 5. put simple checks first use code for fixed rules, such as required fields and character limits then use the decision model for checks that need context, before starting more expensive work 6. track quality and cost measure cost per completed task, incorrect decisions and how often another model or a person needs to review use the failures to improve your questions, references and allowed answers

Desert Ant Labs

@desertantlabs

Jev + on-device models = results in seconds with no LLM in the loop. Quick demo app to show the possibilities. Drop in an audio file: Ear detects the language, Voz transcribes it and Redact removes PII. Then @typesafeai's Jev makes about 20 decisions in one call in milliseconds, and picks which of our on-device models to run. Voice memo to to-do list. Meeting to redacted transcript. Podcast to clips.

OpenRouter

@OpenRouter

1/ Jev, a decision model by @typesafeai, sparked a burst of projects and discussion. We tested it using Ori Eval against popular LLMs on OpenRouter at judging. Jev was >5x faster than the next fastest model, and even its slowest requests beat every other model's median.

Sarah Drasner

@sarah_edo

🎇 I made a small Chrome extension: a side panel that drives any site's WebMCP tools with Jev! When you type, on every keystroke it picks the relevant page's tool, fills in the arguments, and tells you how sure it is. Here it is grocery shopping:

idan levin

@0xidanlevin

We just ran Jev on our WebMCP benchmark. The result: basically broke the benchmark. Jev + Mercury 2.5 (a fast, low-cost LLM) using WebMCP solved 100% of the tasks at roughly 112× lower model cost than GPT-6 Astra using computer use with code execution. Compared to Astra using screenshot-based computer use, the model cost was 245× lower (!). We also compared Jev operating the browser with and without WebMCP. We used Browser Use’s open-source Ultrafast, with some improvements to the harness to make it more reliable across the benchmark. Jev’s browser-control accuracy on its own was not amazing - adding WebMCP nearly doubled the number of solved tasks, from 25/49 to 49/49, while reducing model cost by 18% (more on why below). The benchmark and methodology are fully open and reproducible. Full results: https://webmcp.com/benchmark A few words on how the Jev + WebMCP harness works and why this is exciting: Jev receives text as input and a set of discrete options it can choose from. With WebMCP, those options are the tools exposed by the website. At each step, Jev sees the task, the available tools and previous results, then picks what to do next. The limitation is that Jev can’t generate arbitrary text, which you need for tool arguments. For example, it can choose the search_products tool, but it can’t generate the search query itself. So we split the work: Jev picks the tool and Mercury 2.5 generates the arguments if needed. This works well because turns out most of the cognitive load in these tasks is around choosing the right action. The argument generation itself is relatively simple, so we can delegate to a small and very fast model. We used Mercury, which outputs 1,000+ tokens/sec and is very cheap. The result is a pretty simple combination: Jev for tool selection + Mercury for arguments + WebMCP for the interface. It ends up being very reliable, very fast, and very cheap. A few words about Ultrafast and why do we think it underperforms: Without WebMCP, Jev chooses from the page’s controls: which button to click, which field to fill, or which option to select. But choosing a valid button is different from choosing the right next step. The agent still has to navigate menus, understand forms, recover from errors and recognize when the task is actually complete. Our hypothesis is that WebMCP makes the decision space much simpler. Instead of figuring out a sequence of clicks through a website, Jev chooses explicit actions that directly advance the task. @typesafeai itself documents weaker accuracy on questions requiring multiple reasoning steps. WebMCP moves much of that complexity into the website’s tools, leaving Jev with clearer decisions and fewer opportunities to go wrong (in a sense WebMCP "compresses" a sequence of clicks into one tool call). Our modified Ultrafast setup solved 25/49 tasks - that is a result for our particular implementation and benchmark, not a universal limit on Jev or Browser Use. We are open to more harness optimization to get this result to perform better, feel free to directly contribute to the benchmark here: https://github.com/nekuda-ai/WindTunnel Browser-use ultrafast: https://github.com/browser-use/jev-ultrafast

Hassan

@nutlope

Jev + Kimi K3 for fraud detection! TLDR: Jev classified 100 emails in 1.42 seconds, then I routed the uncertain cases to Kimi K3. The full pipeline got 96/100 correct for only ~$0.07. Video is not sped up, check out the live run! Here was my process: I gave Jev 100 emails to classify (a mix of 50 legit & 50 fraudelent emails). It classified all of them in 1.42 seconds. An underrated feature about Jev is it will give you the confidence score for a classification, so I routed any prediction under 95% confidence to Kimi K3 to be fully sure. 31 emails fell below that threshold. After routing those to Kimi K3, the combined pipeline reached 96% accuracy. The full run took 16 seconds & ~$0.07 in inference costs: - $0.068 from Kimi K3 on @togethercompute - $0.003 (1/3 of a cent) from Jev on @typesafeai. I think this is a really interesting pattern: use a fast specialized model like Jev for the narrow task, then route the uncertain cases to a larger LLM. I feel like this kind of approach could be a game changer for use cases like fraud or anything realtime. You can use the speed & low cost of Jev while having a larger LLM as a fallback to ensure high accuracy.

Milind S

@milindlabs

got @typesafeai's new model Jev as a chief of staff for bots Jev reads the task, wakes the right teammates off the bench and gives each one the right model It is possible on OpenMausBot as it supports all the LLMs from your existing subscriptions Jev as a decision engine is great

Riley Brown

@rileybrown

Building an agent with model router powered by Jev.

CJ (Coding Garden)

@CodingGarden

I built a chat bot with jev, no LLM at all! Responses are instant, no hallucinations. I hooked it up to web search, wikipedia, weather, todoist and home assistant. Jev decides what tool to call and what args to use based on the prompt. Instant answers cite sources as well!

John Yeo

@johnyeo_

Jev made our Slack agent 2x faster ⚡️ Our agent can be quite slow because it needs to read skills and figure out which tools to call. We used @typesafeai's new model to speed this up by first passing it the prompt and classifying the best skill, tool and params to use before handing it to the agent

Duncan

@ephraimduncan

Built a model router with Jev by @typesafeai. Jev decides what model fits your request best and the request is sent to that model.

Sawyer Hood

@sawyerhood

thanks to @typesafeai jev I no longer have fill out all of those fields on prompt boxes. It picks the agent / model / computer / folder for me. - For a major rewrite it uses Fable + Claude Code. - Changes to an ios app run on one of my macs

t0t0

@t0t0_build

Un JEV me está monitoreando más de 25 grupos de whatsapp con clientes en tiempo real y evaluando si tengo que saber algo por urgencia problemas, pedidos irresueltos etc. Si tengo algo que saber, le avisa a una LLM que me escriba. 🔥

Jiaqi Gu

@droidqw

github.com/droid-Q/jev-sk… ，基于 jev 的 skills 路由

codila

@0xCodila

Jev + GrokBot is the best AI agent system I’ve built in my life It just made my setup CHEAPER and FASTER than what 95% of people are running... setup takes literally 7 minutes: prompt → GrokBot → Jev decision → GrokBot execution → result step 1 → open @typesafeai , create API key (keep it off chat paste) step 2 → tell Grok Bot: store TYPESAFE_API_KEY in the secure field step 3 → prompt Grok Bot: install typesafe-sdk on Agent Computer + smoke system_one (Choice) step 4 → tell Grok Bot: build the usage lab (router, dry-run, config, logs) - or clone Github below step 5 → add skill jev-usage-router: before browser / research / retry / extra bot → call the router, honor action step 6 → stay shadow first, read logs, then active when you trust it - kill switch: bypass jev or enabled: false step 7 → flip active: GrokBot obeys route - Jev decides - GrokBot executes - humans control irreversible actions the result: Jev + GrokBot the best and fastest agent running directly on your computer rn, I’ve already tested it on routine tasks - and the results are genuinely incredible You can come up with endless ways to use Jev + GrokBot - but the most important thing is to install it as soon as possible Copy this 2028 setup, explore my repo below - then read the full Jev deep dive ↓

VertrAI

@vertr_ai

154ms vs 860ms is a useful routing result, scoped to these 200 synthetic classification cases—not a blanket ChatGPT comparison. We credited your latency and cost charts in our Jev video, alongside the game/browser demos: x.com/vertr_ai/statu…