Article
CommunityJev Guides & Articles
TypeSafe AI's Jev offers an alternative to LLMs that claims to be 193x faster and 445x cheaper
Tom's Hardware's launch report on Jev, covering how the API takes program state and typed statements and returns yes/no answers, choices, or probability distributions with confidence values.
- Format
- Article
- Reading time
- 3 min
- Published by
- Community
- Last verified
- Sep 2026
Used inJev for Robotics & Hardware
Highlights
- Diogo Almeida, an ex-OpenAI engineer who co-wrote ChatGPT's core training techniques, built Jev for statement evaluation and decision-making.
- TypeSafe says RLCD training plus parallel processing of independent questions explains Jev's speed and cost profile versus frontier models.
- A call takes state plus statements like "Is the customer requesting a refund?" and answers with a confidence percentage before the code branches.
- Context is capped at 64,000 tokens; extra context lowers accuracy, and Jev keeps no memory or global knowledge across requests.
- The article notes Jev can still misclassify, read wording literally, or fall to adversarial attacks, with docs linking intent routing and citation checking.
Watch out
Vendor-reported numbers in a member-exclusive news piece, with no independent benchmark run by the publication.
Questions about this entry
Short answers drawn from the linked project or page.
Claimed. The fetched page contains only the headline, the site navigation and no article body, because the piece is member-exclusive, so there is no benchmark table or methodology to inspect and the publication ran no independent benchmark of its own. The entry records the figures as vendor-reported, which is the honest reading: a headline number with no visible denominator.
The fetched page does not document this, and it should not be read as if it did. The entry's reading of the article records a cap of 64,000 tokens, that extra context lowers accuracy, and that Jev keeps no memory or global knowledge across requests. Those are the entry's notes on the piece rather than text visible in the retrieval, so verify them against the article itself before designing around the limit.
A state plus statements, such as asking whether the customer is requesting a refund, answered with a confidence percentage your code branches on before anything else runs. The fetched page does not include the body, so request shape, endpoints, payload fields and error handling are not documented there; the entry only records that distinction between statement evaluation and conversation is what the model was built for.
Per the entry, yes, and that is the most useful part of the summary. It records that Jev can still misclassify, read wording literally, or fall to adversarial attacks, with the docs linking intent routing and citation checking as mitigations. The fetch does not contain those paragraphs, so this comes from the entry's reading of the article rather than from the retrieved text.
Per the entry, Diogo Almeida, an ex-OpenAI engineer who co-wrote ChatGPT's core training techniques, built Jev for statement evaluation and decision-making. TypeSafe attributes the speed and cost profile to RLCD training plus parallel processing of independent questions, which the entry records as the explanation versus frontier models.
A System One type model bespoke for probabilistic decision-making. Rather than generating prose, it takes program state and typed statements and returns yes/no answers, choices, or probability distributions with confidence values, which is the distinction the entry draws from conversational LLMs.
Only the headline and site navigation were retrieved, because the piece is member-exclusive. The entry therefore records its content as vendor-reported, and the 193x and 445x multiples, the context cap and the failure-mode notes all come from the entry's reading of the article rather than visible body text.
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.