JEV - A lab could build this. Why it still might not.

TypeSafe released Jev on 15 September 2026, still in early access. This piece sets the official price and training account next to an incumbent price list, and explains why a judgment model with free output collides with selling long output by the token.

Folkbench folkbench.com

Co-author: folkbench.com (Folkbench is a reviewable evaluation and selection platform for AI APIs, model services, and related sites. It draws on published service information, prices, availability, latency, and evidence windows to help users compare and choose a path.)

Ten pieces in this series:

On 15 September 2026, TypeSafe released Jev, and it was still in early access. This is their first System One model. It only makes judgments. It does not rely on small talk. The founder, Diogo Almeida, used to work on instruction following at OpenAI, on the research that became ChatGPT.

Jev itself has no technical moat. Any model lab, with a small team, could make its own version in half a month. Technically, nothing blocks it.

The official work did make something new. They built a new architecture. The sampler is parallel: one query finishes the judgment, without generating one token after another. They built a separate training method, called RLCD, reinforcement learning on calibrated decisions. The confidence the model reports has to line up with the share of later decisions that are right. Those are their implementation. What someone else would imitate is the product shape: do not generate strings, and emit calibrated probabilities only on closed questions. The question is fixed in advance, the model hands back a judgment with a probability, and code branches on that number. Half a month imitates that shape. It does not copy TypeSafe's research as it stands. The person imitating it does not have to take that research apart first.

A moat is hard to claim. Once the shape is fixed, the implementation can be swapped out as a whole. After the swap, the system it plugs into still receives the same thing: state in front, a judgment behind.

A chat model's product is a string. A string can be written very long, and software that actually needs that string has to parse it once more. Jev does not produce strings. Without that stretch of text that can be lengthened, output has no bill that rises with length.

The incumbents' price list

The price makes it plain. Jev's input is $0.042 per million tokens, close to free, and output is free. The official account says output is too cheap to meter. They also admit they cannot prove this price is not subsidized. Over the long run, they expect the price to go down, not up.

The incumbents' price list is the other end. Input runs from $0.20 to $10 per million tokens, and output is about five times more expensive again. A chat model's money sits on long output. An answer for a person to read, and the steps an agent continues to execute, both have to be written as text. Once the text is long, the money lands on the output side. Even if input is pressed very low, one long write is still the bulk of the call.

The two sides do not meet. Incumbents sell tokens. A model whose output is free, and whose input is close to free, eats the token business.

The conflict is structural. The more widely a judgment model with free output is used, the fewer people buy the tokens that used to mean "let a large model classify, route, and score". An expense report is checked against a receipt, and someone has to judge whether the description matches the evidence. A security alert fires, and someone has to judge whether this machine is isolated now. Joints of that kind used to be handed whole to a chat model, which wrote a reason, after which the conclusion was dug out of the text. The dug-out text is priced as output, on the more expensive tier. A closed question hands the judgment over directly. What comes back is a set of probabilities, the length is fixed in advance, and there is no text that can keep being written downward. The reason can go unwritten, and that tier of charges has nowhere to land.

What the incumbent damages is its own report. The more widely the model is used, the faster the old column falls. This is a business that enters from below. Cheap judgment travels with the flow and replaces the small decisions that used to call a large model. What gets replaced is not the call above that writes a long piece. It is the small decision that has to be made halfway through the flow. Calls that still have to be written out slowly can still be sold. The official expectation that their own price keeps going down does not fill the column the incumbent lost.

The name Jev comes from William Stanley Jevons. The official analogy is coal and the steam engine. After the steam engine raised the efficiency of burning coal, coal was not burned less. It was burned more. Efficiency goes up, and use does not shrink. It grows. Cheap judgment calls use into existence. Asking a model once used to be not cheap, so people handed it only the few most valuable steps, and wrote the rest as dead rules, or looked themselves. Once judgment is cheap enough to be asked again and again inside code, questions that were not worth asking all arrive together. What goes up is the count.

The use that gets called into existence is not the kind of token incumbents most want to sell today. The length written on a single call drops, and output is not charged. However high the count stacks, it does not enter the table they use today, the one that makes money on long output.

The person who defines this kind of model

The hard part is the person.

Only someone who holds a business view and a model view at the same time sees joints all through a system. What a joint needs is not what a brain needs. A brain needs a stretch of words that can keep going. A joint does not want words. It wants a result that can be branched on. If the probability is sound, the program continues. If the probability is unsure, it is left to a person. Someone who only builds models easily sees this as an output format. Someone who only does the business easily feels that calling the large model once more is enough. The two views have to sit on one person before that person defines this kind of model. Such people are few. The item does not appear on a roadmap by itself.

Using this kind of model well, a person meets the same difficulty. Instinct can only answer questions that instinct can answer. Whether something is so, and which of a fixed few items to pick, instinct can answer. Writing a stretch of content that was not there, or thinking the steps through on a question that has not been framed, instinct cannot hold. That is another kind of model's work. Instinct is fast, and it is cheap. When the program needs to ask, it asks once, and the time and the money can bear it. However many times it asks, the questions are still the ones instinct can hold. So it stays inside a program that keeps running.

The large labs can build it. The people and the compute are there. Closing output from a string into a closed question is something engineering can get through, and that is not the same as reproducing TypeSafe's research in half a month. What half a month produces is a usable shape. TypeSafe's implementation is still in their own hands.

That column is still taking money in. Once judgment is changed into a closed question, and output is made free, the column loses a stretch. The lost part is visible in a quarterly report. The place further forward is left to projects that are still writing output long. Context keeps growing, agents run a few more loops, and what comes out extra is exactly the token this price list recognizes.

They can build it. It will not be scheduled at the front.

Sources

Series