Jev Choice mode: typed agent routing at 256ms and $0.42 per 10k calls
The author replaces Claude with Jev's Choice mode for agent routing: pass state, candidate steps and criteria, get back a pick, confidence score and urgency label; 1,316 logged decisions at 256ms median and $0.42 per 10k calls.
we've been using Claude f*cking wrong on agent routing too your agent reaches a decision. it calls Claude, pays for 400 output tokens of "let me think through the options," parses one choice out of a paragraph. 2 seconds of wait. 4 cents per decision. half the time it rationalized itself into the wrong pick. Jev flips that too. it's a mode of Jev that cannot write a single word. you give it the state, the possible next steps and the criteria. it gives back the pick, a confidence score and an urgency label. one call, one typed answer. Choice(instructions="Choose the next step", criteria=...) that's the whole mode. 256 ms median latency. $0.42 per 10,000 calls. 1,316 live decisions in the clip, every one logged with its score. that's not because Jev knows your agent's job better than Claude. it's because nobody asked it to write the next thing. let Claude write the hard parts. let Jev make the typed call. let your code decide what runs next. the catch: it only works when the next step is one of a fixed set. no free-form "come up with something." if the task needs prose, keep the big model on it. if it needs a routed call with known outcomes, you've been overpaying by 1,000x. the orb in the clip is my own visual concept, the data is simulated. the engine under it is real: one typed question, one typed answer, every call written to disk in milliseconds. the full Choice schema and the gate thresholds are in the article below. bookmark this before your next agent build burns $400 on decisions it could have made for 42 cents.
This post quotes another post: x.com/thegreatest_sv/status/2102802378378621355