Video
CommunityJev Tools & CLIs
Jev Launches on OpenRouter
OpenRouter's beta announcement for Jev: state plus typed questions returns typed decisions with probabilities, so there is no JSON prompting, parsing layer, or output validation.
- Format
- Video
- Reading time
- 2 min
- Published by
- Community
- Author
- OpenRouter
- Last verified
- Sep 2026
Works forJev for Classification
Highlights
- Beta availability of Jev through OpenRouter.
- Describes the API as typed decisions with probabilities instead of generated text.
- Says no JSON prompting or output validation is needed.
Watch out
A platform announcement with no performance data.
Questions about this entry
Short answers drawn from the linked project or page.
Unknown. OpenRouter labels it beta and the thread gives no SLA, no rate limits, and no deprecation policy. It does publish the price, $0.042 per million input tokens with output free, and a 70 to 500 ms end-to-end range, but that is a latency range for their platform, not a reliability guarantee.
No JSON prompting, no parsing layer, no schema check. You send state plus typed questions and get back typed decisions with probabilities, so a failure is a wrong branch rather than a broken parse. What you still build yourself is the handling for low-confidence answers and the threshold you gate on.
Several, per the thread, with no published cap. The three shapes are Noul for yes-or-no returned as a probability, Choice over an option set you define, and Score on a scale you define. A ceiling of roughly 255 options in one shot is cited elsewhere, not in this announcement.
No. The up-to-190x faster and 440x cheaper figures are TypeSafe's own published workflows restated by OpenRouter, and no independent benchmark appears in the announcement. Measure on your own prompts before you build a latency or cost assumption on those numbers.
Five: route a support ticket to the right team, decide if a message breaks content rules, flag which signups look like fraud, choose the next step for an agent, and decide whether a workflow should pause for a human. They are all bounded classifications, which is the point of positioning Jev as a decision model rather than a chat model.
A distribution over your options rather than a single label. The example given is asking which queue a ticket belongs in and getting billing at 84 percent and technical at 16 percent, not just billing. That lets you branch on the top answer and still inspect how close the runner-up was.
There is a promotion: build something with Jev on OpenRouter, tag @jjacky, and OpenRouter is giving twenty dollars in credits to the ten most creative and interesting projects. The post links the Jev pricing and providers page for details, so it doubles as a launch promotion rather than only an availability notice.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
X: The post behind this entry
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.