Jev AI: the TypeSafe Jev model
Jev is the first System One model from TypeSafe AI. It doesn't write text. It reads a state, answers typed questions, and returns calibrated probabilities your code can branch on.
Also searched as Jev AI, AI Jev, TypeSafe Jev, Jev TypeSafe, Jev by TypeSafe AI and the TypeSafe Jev model. Same model, made by TypeSafe AI.
- latency
- 70 to 500 ms end to end (company-reported)
- input
- $0.042 per 1M tokens
- output
- free
- questions
- Noul, Choice, Score
- status
- early access since 2026-09-15
{
"model": "jev-1.13.0",
"answers": {
"department": {
"type": "choice",
"choice": "technical",
"confidence": 0.78,
"probabilities": {
"technical": 0.85,
"sales": 0.0,
"billing": 0.15
}
},
"frustration": {
"type": "score",
"score": 1.0,
"confidence": 1.0
},
"is_urgent": { "type": "noul", "noul": 1.0 }
},
"usage": { "input_tokens": 392, "output_tokens": 65 }
}
What is Jev AI? The TypeSafe Jev model explained
Jev is TypeSafe AI's first System One model: an AI model built to make fast, structured decisions that software can use directly. You send a state and typed questions, and Jev returns typed answers with calibrated probabilities and confidence. It does not generate text.
TypeSafe AI is an AI lab in San Francisco founded by Diogo Almeida, a former OpenAI researcher who worked on the methods that turned language models into chat assistants. After two years in stealth, the company released Jev in early access on 15 September 2026.
The pitch is simple: chat models are great with people, but software needs an interface it can depend on. Jev trades free-form strings for typed values, so the model can sit inside ordinary code as a fuzzy decision rule: classify, route, score, extract or branch.
The name comes from Daniel Kahneman's fast "System 1" thinking, and Jev itself is named after the economist William Stanley Jevons: cheaper intelligence should unlock far more use cases.
- model
- Jev, API alias
jev-latest(docs show jev-1.13) - maker
- TypeSafe AI, San Francisco
- class
- System One model, not an LLM
- training
- RLCD, reinforcement learning for calibrated decisions
- output
- typed decisions with probabilities and confidence
- access
- early access via typesafe.ai
The LLM answer is illustrative and the Jev answer is trimmed from the TypeSafe docs sample. Many LLMs also offer structured-output modes. The point: with free-form strings, parsing, validation and retries are your job.
How the Jev model works: state, questions and typed answers
Every Jev call has two parts. The state is what Jev reads: a support ticket, an email, a tool call, or a JSON object describing your program. The questions define what you want back, and the possible answers are fixed in advance. Jev evaluates all questions in parallel and returns one typed answer per question.
Adding questions barely changes latency and costs only the extra input tokens. In TypeSafe's parallel-questions cookbook, one call with 13 questions was 12.2x cheaper and 10x faster than asking them separately, with no change in answers. Choice and Score answers also carry a confidence value that you can use to decide when to act and when to escalate.
The three Jev question types
request
{
"type": "noul",
"instructions": "The message conveys
urgency or time-sensitivity"
}response
{
"type": "noul",
"noul": 1.0
}A Noul answers a yes/no question with the probability that the statement is true. Use it for flags such as urgent, spam, off-topic or jailbreak attempt.
request
{
"type": "choice",
"instructions": "Which team should
handle this",
"criteria": {
"billing": "Payment issues",
"technical": "Bugs, integrations",
"sales": "Pricing questions"
}
}response
{
"type": "choice",
"choice": "technical",
"confidence": 0.78,
"probabilities": {
"technical": 0.85,
"sales": 0.0,
"billing": 0.15
}
}A Choice picks one option from a set you define and returns a probability for every option plus an overall confidence. Jev supports up to 255 options per question.
request
{
"type": "score",
"instructions": "How frustrated the
customer appears",
"criteria": [
"Calm, just stating facts",
"Frustrated but civil",
"Very angry, strong language"
]
}response
{
"type": "score",
"score": 1.0,
"confidence": 1.0,
"legend": { "0": "Calm...",
"1": "Frustrated...", "2": "Very angry..." },
"probabilities": { "0": 0.0, "1": 1.0, "2": 0.0 }
}A Score rates the state against ordered levels you describe. You get a continuous score, the distribution over levels and a confidence value, which is handy for composite scoring in code.
Jev API request builder
Build a Jev request and copy it as JSON, cURL or Python. Nothing is sent anywhere: this page never calls the Jev API. To run it, use an API key from the TypeSafe console.
Jev vs LLMs: speed, cost and structured output
An LLM writes anything, so you parse, validate and hope. Jev only writes what you defined in advance, so the answer already fits your types. Both have a job: LangChain's guide frames Jev as a complement to the LLM that drives your agent, not a replacement.
| Typical LLM | Jev (System One model) | |
|---|---|---|
| Trained with | RLHF and RLVR | RLCD, reinforcement learning for calibrated decisions |
| Output | Strings: chat, code, or JSON you still have to parse and validate | Type-safe structured values, defined in advance, with probabilities |
| Sampling | Sequential, one token at a time | Parallel, all answers in one query |
| Input price | $0.20 to $10 per 1M tokens | $0.042 per 1M tokens |
| Output price | Around 5x the input price | Free |
| Latency | 3 to 329 seconds end to end for frontier models | 70 to 500 ms end to end |
| Confidence | Self-reported estimates tend to be overconfident and inconsistent | Returned with every answer |
| Best at | Chat, copilots, coding agents, open-ended generation | Classify, route, score, extract, verify and guardrail inside workflows |
Jev cost calculator
Estimate Jev's monthly input cost at the published $0.042 per 1M tokens, next to an LLM priced with your own numbers. The LLM defaults are placeholders, not a quote.
Read the fine print. Every speed and cost figure on this page comes from TypeSafe AI. The company says its evals were built by its own team, that its reference answers come from OpenAI and Anthropic models, that its latencies were measured from the US West Coast, and that it cannot yet prove its pricing is sustainable. Test Jev on your own workload before you commit.
What is Jev used for? Model routing, guardrails and classification
Jev fits wherever code needs a fast, cheap, calibrated judgment about messy input. Pick a use case to see how it is built.
Model routing: pick the cheapest model that can do the job
Let Jev read the request and choose a model by criteria you define: fast and inexpensive for lookups and extraction, more capable for architecture and high-stakes calls. LangChain ships an experimental ModelRouterMiddleware for this, and the probabilities stay available in agent state.
from langchain.agents import create_agent
from langchain_typesafe.experimental.middleware import (
ModelChoice, ModelRouterMiddleware,
)
router = ModelRouterMiddleware(
choices={
"fast": ModelChoice(model="<cheap-model>",
criteria="Lookups, extraction, small edits."),
"strong": ModelChoice(model="<strong-model>",
criteria="Architecture, high-stakes calls."),
},
instructions="Pick the cheapest model that can finish the task.",
)
agent = create_agent("<default-model>", middleware=[router])
Agent guardrail: block risky tool calls before they run
Agents can be steered by bad instructions or by an attacker. Coding harnesses already classify dangerous actions before running them, and a cheap classifier lets you add the same check to any agent. LangChain's experimental AutoModeMiddleware uses Jev to inspect tool calls and block risky ones before the tool executes.
from langchain.agents import create_agent
from langchain_typesafe.experimental.middleware import AutoModeMiddleware
guardrail = AutoModeMiddleware(tools=["bash"])
agent = create_agent("<your-model>", middleware=[guardrail])
Ticket triage and intent routing
One request can return the team (Choice), the frustration level (Score) and whether the message is urgent (Noul). Your code then decides: auto-reply, escalate or hand to a human. TypeSafe documents intent routing and confidence-gated routing patterns for exactly this.
res = client.system_one(
state=ticket_text,
questions={
"team": Choice(instructions="Who should handle this",
criteria={"billing": "Payments", "technical": "Bugs"}),
"urgent": Noul(instructions="Needs a reply today"),
},
)
if res.answers["urgent"].noul > 0.9:
escalate(ticket_text)
LLM guardrails: screen every message in and out
Describe the hazards you care about, such as "is this a jailbreak attempt?", and score how harmful complying would be. Threshold the probabilities and your code decides whether to pass, review, block or reroute. TypeSafe's cookbook screens both directions of an LLM app with a single request.
RAG passage filtering
Score each retrieved passage with one request, then decide in code which ones reach the answering model. Keep and flag passages that contradict the question, and drop those carrying a hidden instruction or prompt injection.
Re-ranking and semantic search
In TypeSafe's re-ranking cookbook, one question per query and candidate pair lifted top-1 accuracy from 5% to 18% and top-10 accuracy from 38% to 62% on 40 legal queries, starting from BM25 shortlists of 30 passages. A separate cookbook builds line-by-line semantic search over a terms-of-service document.
Citation checking
Catch wrong or hallucinated citations by checking a quote against its source. One Choice question decides whether the surrounding context supports the claim, and its confidence can flag the citation for human review.
Structured extraction and function calling
Ask Jev for the parts named in a document, then resolve and validate them in code with confidence-based review. The same idea maps natural-language requests to ordinary typed functions: function names and closed-set arguments become confidence-aware questions.
Real-time apps and large-scale data
At around 100 ms per call, AI can sit in code paths where UX is critical. TypeSafe's demos include a Doom bot making about 10 queries per second, which it puts at roughly $7 per hour, and a Wikipedia wikiracing agent. For big data, the pitch is turning huge corpora into features and insights with map-reduce style calls.
Jev API, SDKs and LangChain integration
The Jev API is one HTTP endpoint. Send the state, the model name and your questions, and read typed answers back. Official SDKs, a LangChain integration and an agent skill wrap it.
POST https://api.typesafe.ai/v1/systemone
Authorization: Bearer <API_KEY>
Content-Type: application/json
{ "model": "jev-latest", "state": "...", "questions": { ... } }# Python 3.10+ pip install typesafe-sdk from typesafe_sdk import Noul, TypeSafeClient client = TypeSafeClient() # reads TYPESAFE_API_KEY res = client.system_one( state="Checkout fails for every customer since 9am.", questions={"urgent": Noul(instructions="Needs attention right now")}, ) print(res.answers["urgent"].noul)
pip install langchain-typesafe # set TYPESAFE_API_KEY, then: from langchain_typesafe import Noul, TypeSafeClassifier clf = TypeSafeClassifier() res = clf.invoke({ "state": "Deploy failed twice, customers see 500s.", "questions": {"urgent": Noul(instructions="Needs attention now")}, }) print(res.nouls["urgent"].noul)
# Claude Code claude plugin marketplace add typesafe-ai/skills claude plugin install typesafe@typesafe-ai # Other coding agents npx skills add typesafe-ai/skills --skill typesafe-ai
choice(), score() and noul() helpers. Install instructions and the full API reference live in the JavaScript SDK docs, and the source is on GitHub.There is also system-one-adapter-python, a drop-in client that runs the same System One requests on top of LLM APIs, handy for comparing Jev against a general model.
Jev limitations: what the TypeSafe model can't do
- It doesn't generate text. Jev is not a drop-in replacement for an LLM. Keep an LLM for open-ended reasoning and writing, and give Jev the narrow decisions.
- "Can't hallucinate" means "can't break the schema". Every answer fits your types, but an answer can still be wrong. TypeSafe publishes known weak spots for jev-1.13 on its jaggedness page.
- Access is early access. Developers are admitted from a waitlist, and after launch, demand briefly outran the API, according to TechCrunch.
- Text and structured state only, for now. TypeSafe's demos run on structured state rather than images, and it plans versions for other modalities.
- Big candidate sets need a trick. A Choice supports up to 255 options. TypeSafe's Wikiracing demo scores links first, then makes an explicit choice.
- The numbers are the company's own. Benchmarks, speed and pricing are self-reported, and TypeSafe says it cannot yet prove the pricing is sustainable.
Jev pricing and how to get early access
TypeSafe says this is about 238x lower than the input price of Claude Fable 5.1, and expects prices to go down rather than up. Prices and availability can change, so check typesafe.ai for the current terms.
- Join early access on typesafe.ai. TypeSafe is bringing developers off the waitlist as quickly as it can.
- Create an API key in the TypeSafe console.
- Send your first request to
api.typesafe.ai/v1/systemonewith the modeljev-latest, or try it in the playground.
Jev news: TypeSafe AI launch timeline
- pressTechCrunch covers the launch. Early adopters quoted include Vercel, which reports its command-security classifier running 5 to 18 times faster on Jev, and Bryo AI, which found Gemini slightly more accurate at email classification but 10 to 20 times costlier. Source: TechCrunch.
- ecosystemLangChain publishes Building a Harness with Jev, covering TypeSafeClassifier, model routing and an Auto Mode guardrail.
- launchTypeSafe AI introduces System One models and Jev, and opens early access. Read the announcement.
Last updated 2026-09-21.
Jev AI FAQ
What is Jev AI?
Jev (also written Jev AI, AI Jev or TypeSafe Jev) is the first System One model from TypeSafe AI. It reads a state plus typed questions and returns typed answers, meaning yes/no probabilities, choices and scores, each with calibrated confidence, instead of generating text.
Who makes Jev and what is TypeSafe AI?
Jev is made by TypeSafe AI, an AI lab based in San Francisco and founded by former OpenAI researcher Diogo Almeida. Jev launched in early access on 15 September 2026, after two years in stealth.
Is Jev an LLM?
No. Jev is a System One model: it does not generate strings. The possible outputs are defined in advance as typed questions, so every answer fits the schema. TypeSafe positions Jev as a complement to LLMs, which stay better for open-ended reasoning and generation.
What is a System One model?
A System One model is built for fast, structured decisions inside software. The name borrows from Daniel Kahneman's fast "System 1" thinking. It evaluates a state and returns typed answers with probabilities, and is trained with RLCD, reinforcement learning for calibrated decisions.
What question types does the Jev model support?
Three: Noul (a yes/no probability), Choice (pick one option, with a probability for each option and an overall confidence) and Score (rate against ordered levels, with the distribution and a confidence). You can send several questions about the same state in one request and they are answered in parallel.
How do I get access to Jev?
Jev is in early access. Join through typesafe.ai, where TypeSafe is admitting developers from its waitlist. Then create an API key in the TypeSafe console and call POST https://api.typesafe.ai/v1/systemone with the model jev-latest.
How much does Jev cost?
TypeSafe lists $0.042 per million input tokens ($42 per billion), with output tokens free. It says it expects prices to fall, but admits it cannot yet prove the pricing is sustainable. Check typesafe.ai for current pricing.
How fast is Jev?
TypeSafe reports 70 to 500 ms end to end per call, and up to about 200x faster than comparable LLMs on workflows shaped like System One tasks. These are company figures, measured from the US West Coast, so test on your own workload.
Does Jev hallucinate?
Jev cannot make type errors: every answer matches the schema you define. That is not the same as always being right. Answers are probabilistic, and TypeSafe publishes known weak spots of jev-1.13 in its docs. Use the confidence value to send uncertain cases to a human or a stronger model.
Jev vs GPT, Claude or Gemini: which should I use?
It is not either or. Use an LLM for open-ended reasoning and text, and Jev for fast, cheap decisions inside the workflow: classify, route, score, extract, guardrail. In one test reported by TechCrunch, Gemini was slightly more accurate at email classification but cost 10 to 20 times more.
Does Jev work with LangChain and SDKs?
Yes. TypeSafe ships a Python SDK (typesafe-sdk), a JavaScript and TypeScript SDK, a LangChain integration (langchain-typesafe) and an agent skill for Claude Code and other coding agents. See the API and SDK docs for details.
Where does the name Jev come from?
TypeSafe named it after the economist William Stanley Jevons: each drop in the cost of intelligence should unlock far more use cases. The model class, System One, comes from Kahneman's Thinking, Fast and Slow.
Is typesafe-ai.com the official Jev website?
No. typesafe-ai.com is an independent resource, not affiliated with, endorsed by or sponsored by TypeSafe AI. The official site is typesafe.ai, with docs at docs.typesafe.ai.
Try Jev by TypeSafe AI on the official site
Typed decisions, calibrated confidence, one API call.