Developers test what they can build with TypeSafe's fast, typed decision model
TypeSafe’s Jev, launched last week, behaves differently from the standard frontier models that everyone is now used to and has therefore quickly attracted plenty of scrutiny and interest as developers explore how to work with this technology.
Jev’s output is more restricted than the chatty ask-me-anything approach of other LLM-powered chatbots. Jev is a classifier with brains. When given a set of data, it returns predefined “typed” decisions that the developer decided on beforehand, along with probability distributions and, for some query types, a confidence level that can then be used to make decisions and automate processes.
As Brian Eno has often said, greater limitations frequently spur greater creativity.
In the week since Jev’s release, developers have flocked to the service, at least to test it out. FPV Ventures partner Nikunj Kothari set up a site called Jevable to collect prototype Jev apps posted on X.
Jevable hosts developer tools and productivity utilities, some frivolous. One app translates plain English into “unnecessarily fancy prose.” Another allows the user to add an “Urgency” column to spreadsheet rows, which Jev can then rate from “no follow-up needed” to “urgent.”
Another app gives people a virtual way to see what clothes would look like on them. In a mockup, Jev reads the transcript, consults a list of clothing and changes the outfits on an image of the user in real time. Cost is $0.0011 per decision, and it takes Jev ~620 ms to show how awful you will look in that Hawaiian shirt you're thinking of buying.
Gaming hacks are another favorite. There are apps for speeding through Doom, Tetris, League of Legends, Settlers of Catan, and chess (where Jev lost to the GLM 5.3 open-weight model but was far cheaper to run).
Perhaps the expression of coder curiosity has been to use Jev to emulate a CPU, which is useful mostly in terms of entertaining the geek fixation with recursion. To this end, someone coined the term “JevOps” to describe the “end game” of “running all code” on Jev-based virtualization.
“JevOps” is still only a meme, not a discipline. For now.
Jev has been likened to a smart function call. You give it an input and it returns a defined output, using a structured decision model. TypeSafe calls it a “ System One ” model, one designed to make fast, structured decisions.
Users submit data to an API for analysis, and can interrogate their data with three possible types of questions: A Choice, a Score, or a “Noul” (a probability score of truthfulness between 0 and 1), which are all Jev primitives. Jev provides confidence levels with the answers it returns to the Choice and Score inquiries.
Because Jev does not generate free-form text, the user must explicitly define the schema and candidate options beforehand for Choice and Score queries. So using Jev requires some old-school manual configuration ahead of time, compared to the free-wheeling prompting required to generate LLM responses.
The developer must think about what they want to accomplish in terms of these questions, perhaps by breaking up their task into a series of them.
TypeSafe’s documentation recommends using a question like “Does this message convey urgency?” over a more open-ended question like “Analyze this message and determine the best course of action.”
The structured response brings a number of advantages. One is that it means Jev doesn’t have to contemplate how to structure the answer for the user. TypeSafe says Jev can return an answer in as little as 150 ms, fast enough for some interactive and real-time applications (hence the coder fascination with using Jev to speed through games).
Likewise, Jev’s service is cheaper than standard frontier LLMs – input tokens are $0.042 per million tokens and there is no charge at all for output tokens.
“If many useful semantic judgments were affordable within our application’s response-time budget, what would we design differently?” asked TypeSafe technical staff member Eugene Shvarts, in a GitHub README page for an LLM prompt to evaluate Jev’s usefulness for any given project.
Possible workloads that might benefit from the Jev format could include job recruiting, as well as screening scientific papers to ensure they have all the required sections. It could manage software that otherwise would require a human in the loop. Jev creator Diogo Almeida suggested using Jev to route tools, and MCP calls for other models.
“How intelligent is this model? That’s what I’m not able to figure out,” said AI YouTube personality Mo Bitar in a video. The demos are fun, but how accurate are the results? Jev is an LLM, but thus far, we have limited insight (or benchmarks) into Jev’s intelligence. “I know it’s fast. I know it’s cheap, but is it good?”
Bitar suspects it would work best with static self-contained training sets, such as for e-mail spam or online shopping. He said predictive work, like suggesting stock picks, may not be a smart use of Jev.
Digging a bit deeper was engineer Archer Hume, who reported how he probed Jev with 10,000 API calls. (TypeSafe runs Jev as an API-based service, though others have built several open source classifiers similar to Jev itself, such as Jeff and Nimble.)
Hume surmised that Jev has the deep knowledge of an LLM, but it doesn’t try to predict the text it needs to feed back to the user. It calculates decision probabilities directly from the model's internal representations.
Nonetheless, others see Jev as a move in the right direction, namely beyond the loquacious and sometimes deceptive interface of today’s super-powered LLMs.
“It’s time to move past the idea that what we need is smarter frontier models. What we need is smarter systems,” noted Adam Jacob, CEO of the agentic software provider Swamp Club, in a X message. Intelligence is fine, but correct, repeatable results are also necessary.
Anthropic researcher Andrej Karpathy agreed that Jev carves out a new space in the emerging AI market. Jev “revealed latent demand [..] that was under-invested into because of a race to higher intelligence,” he wrote on X. The demand that Jev may address is for a single-token LLM with low latency and “acceptable intelligence,” he wrote. ®