Skip to content

Build Reports disagree14 publishers 3 min read Published Updated

Jev turns a catalogue ID from a prompt constraint into part of the decision domain

TypeSafe's Jev answers typed questions with floats and probabilities. An invoice pipeline that handed it classification and catalogue selection still needs a generative model for field extraction and for the note a human reads.

The Engineer · Build desk

Send a correction

What happened

  • TypeSafe left two years of stealth with $40 million in seed funding led by DCVC and launched Jev, its first model, which answers typed questions instead of writing prose.
  • One request carries a state object plus questions in three shapes: Noul yes/no statements, Choice from a provided option set, and Score against numeric levels with descriptions.
  • Jev bills only for input, at $0.042 per million tokens, and charges nothing at all for output.
  • Vercel said nearly 13% of its paid teams were using Jev within 24 hours of the model appearing on its AI Gateway, twice the share the GPT-5.6 family reached.

Why it matters

  • Who has to decide decision The choice is now per question rather than per application: which prompt clauses are type constraints that a decision call should own, and which outputs a person genuinely has to read.
  • Who's exposed exposure A score with no attached signals lands on whoever deploys it, because a rejected applicant or a regulator asking why gets a float and a threshold.
  • What it costs cost With no public benchmark from TypeSafe, any team quoting the 20-200x figure in a budget has to reproduce it on its own stage first, and that eval work is the adoption cost.
  • What's now possible capability Free output plus parallel evaluation makes it affordable to ask one record twenty separate questions where each check previously meant a billed generation.

Next story · Build · Oct 9

Andreessen Horowitz leads a reported $870M round for Jev maker TypeSafe

Confirmed7 publishers

Inside Mokapot Labs' Invoice Assistant, one Gemma 12B call handled four different jobs: extracting supplier, invoice number and amount, classifying how strong the supplier evidence was, selecting a property from the supplied catalogue, and writing the note that explains the recommendation [21]. Two of those are picks from a closed set. The prompt did the constraining, in English. One clause read: "Select exactly one property ID present in the supplied catalogue. Do not invent, rewrite or normalize property IDs." [22] Another required exactly one of three values for `supplierEvidenceStatus`: `EXPLICIT_TEXT`, `STRONG_TEXTUAL_IDENTITY`, `INSUFFICIENT` [23].

Mokapot Labs' write-up calls the Choice version a stronger contract, because with a finite option set a valid ID sits in the decision domain instead of in the prompt [12]. The old design was not failing. "It was not disastrously slow. It was not unreliable enough to force a redesign," the write-up says [24].

Extraction stayed with the generator, and so did the note a human reads. Simon Willison wrote that Jev is a regression further toward black box machine learning: put in all the text you want, and what comes back is a floating point number [15]. The branch that calls a vision model when text evidence is insufficient is still in the pipeline [25].

Input costs $0.042 per million tokens and output is free [7]. GPT-5 Nano's input is $0.05 per million [8], so Jev is about 16 percent cheaper per input token [14]. The price difference is in the free output and the latency: Flavio Copes, reiterating TypeSafe's stated levels, reports most calls finishing in about 100 milliseconds [1]. Almeida's launch post claims 20-200x faster and 40-400x cheaper, with output tokens free [27]. Against 100ms, the bottom of that range implies the call you are replacing takes two seconds, and the top implies twenty [29]. TypeSafe rejects public benchmarks, and Almeida has publicly rejected a generic JevBench [9].

Questions against one state are evaluated in parallel, so a dozen checks take about as long as one [6]. The yes/no shape is called Noul, which the CEO confirmed on Hacker News is short for Bernoulli [5]. Willison has been using the Score shape as a reranker, fetching 100 candidates with BM25 and scoring each for relevance against the query [26].

"I really hope nobody uses Jev to rank job applicants," Willison wrote [16]. His own test scored every city in the San Francisco Bay Area on a yes/no "Good city?" question, and Jev put Cupertino top and East Palo Alto bottom [17]. He argues evals and structured experiments matter more here than on ordinary LLM projects, and that the price is low enough that hundreds or thousands of experimental prompts cost a few cents [18].

Almeida, who TypeSafe says co-invented RLHF and InstructGPT at OpenAI [10], posted on X on September 15: "Look at how LLMs generate sequentially, which is great for a natural conversation, but totally useless for computers." [20] He also claimed System One models "can't hallucinate" because they are "a lot more like code" [28]. Copes described the placement differently, and more usefully for anyone drawing a diagram: "You add it where code needs one judgment, while the rest of the product stays ordinary code." [13]

What to watch

  • Whether TypeSafe publishes RLCD or any reproducible figures after rejecting public benchmarks.
  • Whether Vercel's nearly 13% of paid teams holds past the first day or decays as a launch spike.
  • Whether a later TypeSafe model returns per-question signals a deployer could audit, instead of one float.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence55
Adoption40
Hype gap+30
Incentives65
Confidence55

Perspective Coverage

14 publishers
Builder
Builder 53%
Operator
Operator 31%
Investor
Investor 16%
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Independent developer Flavio Copes, reiterating TypeSafe's stated performance levels, wrote that most calls to Jev complete in about 100 milliseconds.

    Reported Supported Source: Flavio Copes, reiterating TypeSafe's stated performance levelsView cited source
  2. [2]

    TypeSafe emerged after two years in stealth, backed by $40 million in seed funding led by DCVC, to launch its first model, Jev.

    Reported SupportedView cited source
  3. [3]

    Jev is a text-only model that machines can use natively to make decisions inside software; developers send structured questions and get typed decisions with calibrated probabilities.

    Reported SupportedView cited source
  4. [4]

    Jev accepts three question kinds: Noul yes/no statements returning a float between 0 and 1, Choice questions that pick one of a provided set and return a confidence score plus a probability distribution, and Score questions that return a float along numeric levels with descriptions.

    Reported SupportedView cited source
  5. [5]

    Noul is short for Bernoulli, from the Bernoulli distribution, which TypeSafe's CEO confirmed on Hacker News.

    Reported SupportedView cited source
  6. [6]

    The Jev API accepts a single state document and as many questions as fit the context window; questions are evaluated in parallel, so sending many questions should take a similar time to sending one.

    Reported SupportedView cited source
  7. [7]

    Jev charges only for input, at $0.042 per million input tokens, with output free.

    Reported SupportedView cited source
  8. [8]

    OpenAI's GPT-5 Nano is priced at $0.05 per million input tokens.

    Reported SupportedView cited source
  9. [9]

    TypeSafe rejects public benchmarks and optimizes for intelligence per dollar, and Diogo Almeida has publicly rejected the idea of a generic JevBench benchmark.

    Reported SupportedView cited source
  10. [10]

    Almeida is ex-OpenAI where, according to TypeSafe, he co-invented RLHF and InstructGPT, the methods behind ChatGPT and GPT-4.

    Reported Supported Source: TypeSafeView cited source
  11. [11]

    Jev's core innovation is Reinforcement Learning for Calibrated Decisions, a novel unpublished technique that optimizes for answers with epistemically honest probabilities on System One tasks.

    Reported SupportedView cited source
  12. [12]

    In the generative approach selecting a valid identifier is a prompt requirement; with a bounded Choice it is part of the decision domain, which the write-up calls a much stronger contract.

    Reported Supported Source: Mokapot Labs write-up on dev.toView cited source
  13. [13]

    Flavio Copes wrote: "You add it where code needs one judgment, while the rest of the product stays ordinary code."

    Reported Supported Source: Flavio CopesView cited source
  14. [14]

    Jev's input price is about 16 percent below GPT-5 Nano's per input token.

    Derived Supported
  15. [15]

    Simon Willison wrote that Jev represents a regression further towards black box machine learning systems: you can put in all the text you want, and the only thing you get back is a floating point number.

    Reported Supported Source: Simon WillisonView cited source
  16. [16]

    Willison wrote: "I really hope nobody uses Jev to rank job applicants."

    Reported Supported Source: Simon WillisonView cited source
  17. [17]

    In Willison's experiment scoring every city in the San Francisco Bay Area on a yes/no "Good city?" question, Jev rated Cupertino top and East Palo Alto bottom.

    Reported Supported Source: Simon WillisonView cited source
  18. [18]

    Willison argues evals and structured experiments are even more important for Jev than for regular LLM projects, and that Jev is cheap enough that running hundreds or thousands of experimental prompts costs just a few cents.

    Reported Supported Source: Simon WillisonView cited source
  19. [19]

    Vercel said that within 24 hours of Jev launching on its AI Gateway, nearly 13% of paid teams were using it, twice the share of the GPT-5.6 family and more than six times Fable 5.1's share.

    Reported Supported Source: VercelView cited source
  20. [20]

    Almeida posted on X on September 15: "Look at how LLMs generate sequentially, which is great for a natural conversation, but totally useless for computers."

    Reported Supported Source: Diogo Almeida on X, September 15View cited source
  21. [21]

    Before Jev, the Invoice Assistant text-analysis stage sent one Gemma 12B call that extracted supplier, invoice number and amount, classified supplier evidence, selected the property, and explained the recommendation with a note.

    Reported SupportedView cited source
  22. [22]

    Part of the original Invoice Assistant prompt said: "Select exactly one property ID present in the supplied catalogue. Do not invent, rewrite or normalize property IDs."

    Reported SupportedView cited source
  23. [23]

    Another part of the prompt said to classify supplier evidence with exactly one qualitative supplierEvidenceStatus: EXPLICIT_TEXT, STRONG_TEXTUAL_IDENTITY, INSUFFICIENT.

    Reported SupportedView cited source
  24. [24]

    Of the pre-Jev design, the write-up says: "It was not disastrously slow. It was not unreliable enough to force a redesign."

    Reported SupportedView cited source
  25. [25]

    The Invoice Assistant pipeline routes to a vision model when supplier evidence from text is insufficient.

    Reported SupportedView cited source
  26. [26]

    Willison has been experimenting with Jev for search reranking, fetching 100 likely matches with BM25 and having Jev score those candidates for relevance against the original query.

    Reported Supported Source: Simon WillisonView cited source
  27. [27]

    Almeida's launch post lists headline stats for Jev as 20-200x faster, 40-400x cheaper with output tokens free, and frontier composable intelligence optimized for decisions.

    Reported Contested Source: Diogo Almeida's launch postView cited source
  28. [28]

    Almeida claimed System One models output decisions with probabilities and confidence instead of words and "can't hallucinate" because they are "a lot more like code".

    Reported Contested Source: Diogo AlmeidaView cited source
  29. [29]

    For a 20x speedup against a 100ms Jev call, the replaced call must take about two seconds; for 200x, about twenty seconds.

    Derived Contested

Sources

14 independent publishers whose own reporting we read for this story.

  1. blog.bytebytego.com

    1 article · September 26, 2026

    EP227: Top 9 Places to Use Jev
  2. blog.vercel.com

    1 article · September 15, 2026

    TypeSafe AI's Jev now available on AI Gateway
  3. dev.to

    22 articles · September 26, 2026

    This New AI Model Refuses to Write Text. That Is Exactly Why It Runs 100x Faster
  4. latent.space

    2 articles · September 21, 2026

    [AINews] Jev: a “System One Model” that only decides/classifies/routes/scores — >100x faster, >200x cheaper than small frontier LLMs
  5. mezha.net

    2 articles · September 18, 2026

    TypeSafe AI представила Jev: модель без генерації тексту прискорює автоматизацію
  6. runtimewire.com

    3 articles · September 18, 2026

    TypeSafe opens Jev early access for fast, typed AI decisions
  7. seangoedecke.com

    1 article · September 16, 2026

    Jev means structured output is interesting again
  8. simonwillison.net

    2 articles · September 22, 2026

    Jev introduces a new shape of LLM - System One, aka Decision Models
  9. testingcatalog.com

    1 article · September 17, 2026

    ICYMI: TypeSafe AI launches Jev for structured AI decisions
  10. the-decoder.com

    2 articles · September 16, 2026

    Former OpenAI researcher builds an AI model that judges options instead of writing text
  11. theneuron.ai

    5 articles · September 16, 2026

    Everything That Happened in AI Today (Tuesday, September 15, 2026)
  12. thenewstack.io

    1 article · September 21, 2026

    TypeSafe launched Jev because sequential LLMs are “totally useless for computers”
  13. thestack.technology

    1 article · September 20, 2026

    Runtime: Jev is an LLM without the LL
  14. tomshardware.com

    1 article · September 21, 2026

    TypeSafe AI's Jev offers an alternative to LLMs that claims to be 193x faster and 445x cheaper — System One type model is bespoke for probabilistic decision-making

Topics and entities