Jev AI Review (2026): Fast, Cheap, Literal

I tested Jev for under $0.005, and got 98% accuracy on the 332 answers it was sure about (unsure on 52) when asking it 384 yes/no questions on how startup ideas are described in 8 different languages. This is a quick review of the Jev AI model that was launched on Sep 15th 2026, by TypeSafe. I ran my test four days after launch. Do you need it in addition to Claude and ChatGPT?

Be careful, Jev interprets your text literally. If you say "Small building managers pay $20 monthly to coordinate urgent repairs", Jev missed in 4 of 8 languages that a code reviewer read this as describing a problem. If your app needs a little bit of fuzziness, Jev may not be for you.

Disclaimer: I am the creator of Preuve AI, which sells startup idea validation. I am not affiliated with TypeSafe in any way, and didn't get any free access, and paid the published rate with my own API key. I based my review on my own test, the TypeSafe website, and a couple other people's tests, all linked below.

Will your idea survive the market?

Preuve AI runs 10 agents against live market data and links every claim to a source. Free analysis in 60 seconds.

Validate My Idea FreeRated 5/5 · 15 reviews

What is Jev AI, and how is it different from ChatGPT or Claude?

Jev is a decision model created by TypeSafe AI. The model was released in early access on Sep 15th 2026. It processes texts, and you can also type questions to it. It then answers your questions by giving you a probability for all the answers you allowed. It doesn't write anything. Here is the description from the TypeSafe launch blog post by founder Diogo Almeida, who writes that at OpenAI, Almeida helped create the methods that led to the research behind ChatGPT: "unstructured state in, typed probabilistic decisions out."

You can find all the types of questions you can ask Jev on TypeSafe's documentation: Yes/no questions: you can ask it something like whether the text is in English, and it will answer with a probability of being yes (a Noul). Choice: you can ask it to choose from a list of answers, and it will answer with a probability for each answer. Score: you can ask it to score your text according to levels you specify. You can ask it many questions about one text, all at once.

From the TypeSafe launch blog post comes the "can't hallucinate" line. From a person testing it out as a router for their app, on r/LLMDevs:

"Their 'can't hallucinate' claim also just means it can't return something outside your list." (r/LLMDevs, read October 4, 2026)

TypeSafe also claims on their website that it is "193.6x faster, 444.6x cheaper." Those numbers are based on workflows they created, and compared against the average answer of GPT-6 Astra and Fable 5.1. From the TypeSafe launch blog post: their published tests are generally run on their team's laptops, located on the West Coast. The workflows were created by their own model team, "so some bias could exist." On price, they write: "We can't prove it isn't subsidized." In general, they expect these numbers to be "on the higher end of real world gains."

I like that they wrote their own footnotes.

How I tested Jev on 128 startup idea descriptions

For Preuve's scan form, I want to add a hint when a startup idea doesn't describe the 3 key aspects of a startup: a customer, a problem, and a way to make money. I don't have this feature online yet, but in the first version I was thinking about looking for keywords, which would give false positives and false negatives, so I thought about using Jev to help me.

To test it, I wrote 16 different short scenarios, and had them translated in 8 languages (English, French, Spanish, German, Italian, Portuguese, Arabic, Korean), to create 128 different "startup ideas", of one or two sentences. The 128 "startup ideas" are not real, they are synthetic. Here are 4 of the original scenarios, in English:

For each startup idea, I asked Jev three yes/no questions: does the idea identify a concrete group of intended users or customers? Does it state a concrete problem, unmet need or undesirable situation it aims to improve? Does it state how the business will earn money? This makes a total of 384 yes/no questions. I used jev-1.13.0, with TypeSafe's API.

My rule for reading Jev's answer: a probability of 0.8 or more counts as yes, 0.2 or less counts as no. Otherwise (that is, if Jev's probability is between 0.2 and 0.8), I assume that Jev is not sure about its answer, and instead ask the keyword check to decide.

These results are the best case, because I wrote the questions myself and tuned them on this set of ideas. But I also tried the same wording on 24 new idea descriptions (that I also wrote myself, and that describe different scenarios). For those 24 ideas, Jev + keyword check was right in 72/72 cases, while keyword check alone was right in 47/72 cases.

How accurate is Jev? My results across 384 decisions

Surprisingly, Jev is very correct, at least when the text is short and not complicated. When Jev was sure about the answer (332/384 decisions), it was correct in 326/332 of them. Remember that in my test I used Jev only as a support for the keyword check: when using only the keyword check, it was correct in about 2/3 of the cases. When I add Jev's sure answers, the combined method is correct in 349/384 of the cases, and both kinds of mistakes are reduced by roughly three quarters.

Source: Preuve AI's own test, run September 19, 2026 on jev-1.13.0, stored results read October 4, 2026. 128 synthetic idea descriptions in 8 languages, 3 yes/no questions each. Counts are decisions, not descriptions.

To be fair, Jev was not sure in 52 decisions and delegated them back to the keyword check. In only 6 decisions it was incorrect.

Source: Preuve AI's own test, run September 19, 2026 on jev-1.13.0, stored results read October 4, 2026. 128 decisions per question. Confident means a probability of 0.8 or more, or 0.2 or less.

Note: I changed one label, because only after writing the code a code reviewer pointed out that "coordinate urgent repairs" was indeed a problem, so I re-labeled it in all 8 languages and re-graded the saved answers (with no new request to Jev). The original labelling was more favorable for Jev, because there were 87 false warnings from the keyword check alone and only 19 from the combined method. Now I report 95 and 27, respectively, as shown in the above table.

Where did Jev get it wrong?

All 6 of Jev's mistakes were on the problem question. 4 of them were for the idea description "Small building managers pay $20 monthly to coordinate urgent repairs", which I labelled as a customer, a problem, and a way to make money. Interestingly, Jev never said that it was not a customer nor a way to make money, but in 7/8 languages it leaned towards it not being a problem.

Source: Preuve AI's own test, run September 19, 2026 on jev-1.13.0, stored results read October 4, 2026. One description, eight translations, one yes/no question each. Probabilities as returned by Jev.

Indeed, the description is not explicit about the problem, it just describes what the app would do. This is the first item in TypeSafe's limits page, which says that Jev "answers the question you wrote, not the one you meant." So, depending on your perspective, maybe it was not a mistake. The code reviewer thought that the original labelling was wrong, and that it did state a problem.

The remaining 2 mistakes were for the idea description "Annual subscriptions are planned, but there is no audience or pain point yet", in Italian and in Portuguese. Jev said with 0.86 probability that it stated a problem, while in English it got it right. Again, it is in the limits page, because it uses negation and Jev takes things literally.

Finally, notice how the results are a little bit different depending on the language. This is expected and also in the models page, which says that "English is the primary training language and where accuracy is currently best."

Source: Preuve AI's own test, run September 19, 2026 on jev-1.13.0, stored results read October 4, 2026. 16 descriptions per language, 3 decisions each, so 48 decisions per language.

But again, with only 16 idea descriptions per language, a difference of 3 decisions is not enough to rank the languages. I would only consider the number of cases where Jev was not sure, and take into account that it was not so sure for Arabic and Korean.

How much does Jev cost, and how fast is it?

According to the models page (read October 4th 2026), the model jev-1.13.0 costs $0.042 per 1 million tokens in the input, and nothing for the output. I made 128 requests with a total of 88,675 tokens in the input, for a total cost of $0.0037.

This means that it costs about $0.000029 for one idea description and for 3 decisions. Or, in other words, it costs about $0.03 to process 1000 idea descriptions. Remember, though, that most of the tokens are for the questions, not for the idea description. So, the cost will depend more on the length of the questions that you will ask.

As far as I can tell, Jev is quite fast. From my own test, running on my machine and sending four requests at a time, the median response time was 273 ms. 19 out of 20 requests were done in 407 ms or less. None of the 128 requests I sent failed. These results fit the speed range of 70ms to 500ms mentioned in the TypeSafe launch post, and are close to what an independent guide measured.

Source: my test (September 19, 2026); Jev AI Guide review (last checked September 19, 2026); r/AI_India and r/LLMDevs posts and TypeSafe's launch post, all read October 4, 2026. Milliseconds per request, network included. Different machines, places and request sizes, so compare ranges, not winners.

From a test by a developer on the subreddit r/AI_India, it seems like it might be a bit slower when using OpenRouter. They got a median speed of 380ms, and note that TypeSafe claims a speed range of 70-100ms, "and through OpenRouter I got 4 to 5x that." In the same test, the developer found that per 1000 text classifications on the Banking77 dataset, Jev cost $0.08 while the same task on Claude Sonnet 5 cost $6.43.

Skip weeks of manual research

Get complete market research, sourced proof, competitor map, and pricing data for your idea instantly.

Run a Free Analysis

What are Jev's limitations?

You can find a list of limitations from TypeSafe, which was last reviewed on 2026-10-02. They list nine limitations, and for each limitation they have listed a workaround that you can use:

1. Jev reads literally, and might not understand the meaning behind a question, only the question as it is written. Negations and scoping might be read literally.
2. Jev can't reliably do math or work with numbers, it can't count reliably. "Jev is not a calculator."
3. Jev struggles with dates. Dates are simply read as text, and for example it can't accurately tell which date came first out of two dates.
4. Jev can have problems when you use double negatives or multiple hops in questions.
5. Jev might struggle with long inputs that contain a lot of non-relevant information. In the TypeSafe wording, "Jev suffers from context rot."
6. Jev can be misled by the text. "State is data, and jev-1.13 does not treat it as hostile by default."
7. Jev can be confused by contradictory instructions.
8. For questions that ask to choose from a number of options, Jev has a tendency to lean towards the first option.
9. Jev is not trained for generating text.

In my test, I avoided most of these limitations. Most importantly, I tried to keep the descriptions short and clean. Therefore, my result is likely a best case. One of the limitations that might be problematic for the example I'm working with here is limitation number 6, where the text might contain misleading information. An independent tester has tested how well you can trick Jev, so have a look at that below.

What do independent Jev tests show?

The biggest independent test that I could find was done by Will Kelly, and the full test can be found on GitHub. Will says the test is not affiliated with or endorsed by TypeSafe. Will did the test by first writing all the predictions, and then sent a long batch of requests to jev-1.13.0.

Jev had a confidence level that was very close to the hit rate when it came to a task that Jev is supposed to be good at, namely routing support tickets. When it came to a logic puzzle, on the other hand, Jev did very poorly, and said that all the formulas could be solved. Trying to trick Jev by simply telling it to ignore the instructions didn't work very well, but a more polite text that said that a support lead had already decided on a label worked for 147 out of 200 support tickets.

It is also worth noting that if you want to ask many questions about the same text, and you can do so in a single request, then this is, in Will's words, "genuinely free."

Another test was done by a developer on the subreddit r/AI_India. They worked with voice AI for healthcare, and tested out six different classifiers on three different public datasets for under $10. Jev had an accuracy that was within 0.2 to 4 points of that of Claude Sonnet 5, but the cost was 50 to 77 times lower.

In the same test, the developer tested out Laya, an open weights model from Convai that is described as an answer to Jev. Laya had similar accuracy to Jev on tasks with 2 and 4 labels, but struggled more on the task with 77 labels. A quote from the developer:

"If you already have labelled data, a small fine-tuned encoder is still the strongest and cheapest option." (r/AI_India, read October 4, 2026)

Source: Will Kelly, "Evaluating jev" on GitHub (one September 2026 run on jev-1.13.0), and the r/AI_India benchmark post (500 held-out examples per dataset), both read October 4, 2026. Accuracy gaps are percentage points; the r/AI_India author puts the noise at about plus or minus 2.5 points.

In an independent guide to Jev, they ran into a similar issue as I did when testing the wording of questions. For example, when asking "Is the customer asking for money back?" they got a score of 0.50 for a text where the customer said that they thought that the charge might be wrong. When asking "Does the customer say a charge might be wrong?" they got a score of 0.97 instead.

The guide also mentions the lack of a research paper, a model card, public benchmark scores or open weights. The independent accuracy figures I found are the ones above, mine included.

Jev vs Claude or ChatGPT: which should you use?

Use Jev for narrow, repeated yes/no or pick-from-a-list decisions, and Claude or ChatGPT for anything that needs written text, math, dates or several steps of reasoning. A commenter on r/ArtificialInteligence put the trade in one line:

"Jev can't do everything the LLM can." (r/ArtificialInteligence, read October 4, 2026)

Why would you want to use Jev anyway? Here's what I think:

Finally, as someone pointed out in r/learnmachinelearning, you could combine Jev with a more capable model, and only run the more expensive model when Jev isn't confident in its answer. In my test it cost about $0.03 per 1k descriptions, so paying a more general model for every decision is hard to justify for a task like this one.

How do you get access to Jev?

TypeSafe's own domains are typesafe.ai, docs.typesafe.ai and api.typesafe.ai, and API keys are created on console.typesafe.ai. As of Oct 4, 2026, their rate limit, according to the models page, is 100k tokens per second, and 80 requests per second, which they say they adjust dynamically. The context is 64,000 tokens per request and they only support text.

Shortly after launch, TypeSafe opened up signups for 2 days, starting Sep 20, 2026, according to the Jev AI Guide. They paused signups, but you can access Jev via OpenRouter, Vercel, or Cloudflare, without needing a TypeSafe account. Each of these providers have different names for the Jev models, and different rate limits. The TypeSafe signups seem to have been paused on Sep 22, 2026, according to jevpricing.com (as of Sep 26, 2026). Check typesafe.ai for the current status. Also, if you're tuning any parameters or thresholds for your use case, make sure to pin your model to jev-1.13.0 instead of using jev-latest, according to the models page.

Why validate the business idea before building on Jev?

The exercise of having Jev look for customers, problems, and money in 128 business idea descriptions, for $0.0037, highlights an important point:

It's increasingly easy to write a sentence that sounds plausible. While Jev can read what the sentence about building repairs says, it's much harder to tell whether a building manager will actually pay $20/month.

I talk more about this in why startups really fail, and show what to do about it in how to validate your business idea.

If you'd like to validate your business idea, you can use Preuve AI to scan it against 60+ live data sources. The Reality Check is free, and takes less than a minute. After that, talk to 5 potential buyers.