# Jev: The System One Model That Ends the Chat Era — Verified Specs & Pricing (2026) TypeSafe's Jev returns typed decisions with calibrated confidence in 70–500 ms — no chat, no parsing, no type errors. Verified specs, pricing, and the 445× claim. ## 01 What Jev Actually Is TypeSafe AI was founded in **2024** in San Francisco by **Diogo Almeida**, **Erik Gafni**, and **Sasha Sheng**. Almeida, the CEO, spent roughly four years at OpenAI working on RLHF, InstructGPT, ChatGPT, and GPT-4 before leaving in 2024 — he's the "ChatGPT co-inventor" the press keeps pointing at. The company sat in stealth for about two years, then exited on **September 15, 2026** with two announcements at once: the first System One model, and a **US$40M seed round led by DCVC**, at a valuation Forbes reported as **US$200M**. Jev itself is **proprietary** — no weights, no public architecture spec, no technical paper. TypeSafe describes it as transformer-based and trained **exclusively on synthetic data**. The current release is `jev-1.13.0`, served through one endpoint (`POST /v1/systemone`) with aliases `jev-latest` and `jev-preview` (both currently point to the same version). The hosted API opened for early-access developers, with Python and JavaScript SDKs. Jev is **not** fine-tuned or LoRA-adapted with customer data — the same weights serve every account, and you shape its behavior through the request itself, not through per-customer models. The driving question Almeida framed the whole project in one line: "Models have been superhuman at chat for years, so where is all the automation?" His answer, from the announcement: LLMs were optimized for humans — "super human at pleasing humans" — and that was the bottleneck. Jev is built for the opposite consumer: *software*. ## 02 System One vs. System Two — The Core Bet The name comes from Daniel Kahneman's *Thinking, Fast and Slow*: System 1 is fast, intuitive, automatic thinking; System 2 is slow, deliberate reasoning. LLMs are System Two machines — they **think**, one token at a time, in language. TypeSafe's bet is that most production decisions don't need thinking out loud. They need a fast, structured, calibrated answer that code can consume directly. #### Existing LLMs System Two · the thinking era - Trained with RLHF / RLVR — optimized for what human raters prefer, or what can be verified - Input: unstructured text, sequential messages - Output: strings — chat, code, refusals, or type-safe values if you're lucky. Software must parse + validate - Sampling: sequential, one token per step, each conditioned on the last - Cost: input $0.20–$10 per Mtok; output ~5× more expensive - Speed: 3–329 seconds end-to-end on frontier models - Confidence: overconfident and inconsistent, even when prompted for it #### Jev · System One TypeSafe AI · the deciding era - Trained with **RLCD** — Reinforcement Learning for Calibrated Decisions: probabilities optimized against outcomes, not human preference - Input: unstructured text with emphasis on **structured program state** - Output: type-safe structured values, defined in advance. The model *cannot* emit a value outside the schema - Sampling: **parallel** — all outputs in a single query, hardware-aware - Cost: $0.042 per Mtok input; output tokens free ("too cheap to meter") - Speed: **70–500 ms** end-to-end — 40×–200× faster for the same intelligence level on decision-shaped queries - Confidence: every output carries a calibrated probability — higher confidence means higher accuracy, and similar inputs get similar answers The deepest detail in that comparison is the training objective. RLHF taught models to write things humans rate well; RLVR taught them to produce things that can be checked. RLCD teaches a different skill entirely: **being right about being uncertain**. A model that can do a task 95% of the time but can't tell you when it's in the 5% cannot be automated. A model that can, can. ## 03 How a Jev Call Works A request is `state` + `questions`. The state is a string, a JSON object, or an array of text — your proprietary records, your domain context, the live state of your program. The questions are typed. Jev ingests the state once and evaluates every question against it in parallel, returning structured answers instead of prose. There are exactly three question types — TypeSafe calls them primitives: choice #### Pick one from N Select one option from a defined set. Returns the chosen option, per-option probabilities, and a confidence score. Cardinality up to 255 — above that, Jev scores independently then makes an explicit second-stage choice. score #### Rate on levels Rate the state against ordered levels (e.g. churn risk: low / medium / high / critical). Returns the score, per-level probabilities, and confidence. noul #### Yes or no Evaluate a yes/no statement against the state. Returns a probability between 0 and 1 — a number your code can threshold, gate on, or feed into a downstream model. Shaped like this, a Jev call looks less like prompting and more like a database query over natural language: ``` # POST https://api.typesafe.ai/v1/systemone { "model": "jev-latest", "state": "", "questions": [ { "type": "choice", "key": "risk_bucket", "options": ["low", "medium", "high"] }, { "type": "noul", "key": "fraud_likely", "statement": "This transaction is fraudulent" } ] } # → typed answers + per-option probabilities + calibrated confidence, # all questions answered in one parallel pass. 70–500 ms. ``` Context budget is **64k tokens per request** — covering state plus all questions combined — with 32k for the state plus the single longest question. Input is text-only (no image, audio, or video; pre-process non-text into text or structured fields). English is the primary training language and where accuracy is best; CJK and other scripts are handled but not equally well — the docs say to test on your own content and watch the confidence field. Rate limits at launch: 250,000 tokens/second and 1,200 requests/minute, and TypeSafe is explicit that they're adjusting dynamically as GPU capacity lands. Enterprise customers get zero-data-retention options, and customer requests are not used for training. The pattern that matters Because there's no fine-tuning, the architecture of every Jev deployment is the same: **put your domain in the state, encode your rules in the question's instructions and criteria, and decompose broad judgments into atomic questions** — then combine the probabilities in code. TypeSafe's AutoResearch cookbook even documents training a classical downstream model directly on Jev's probabilities, turning the frontier model into a labeling engine. ## 04 The Receipts — and the Hints of Humility TypeSafe's announcement is unusually structured for a launch post: every bold claim is followed by a "Nuance" paragraph. That's the right instinct, so let's sort what's verifiable from what's self-reported. | **Claim** | **Status** | **Notes**| --- | --- | --- | 70–500 ms end-to-end latency | Checkable HIGH | Any customer with an API key can time a call. TypeSafe notes its published evals run from laptops on the West Coast, where the service is currently hosted.| | $0.042/M input, free output | Checkable HIGH | Pricing is public and usage-metered. Their own caveat: "We can't prove it isn't subsidized" — long-term sustainability is unproven, and they expect prices to go down.| | Zero type errors | Guaranteed by construction HIGH | Output schema is defined in advance; a value outside the schema is mathematically impossible. One counter-example would falsify it, and TypeSafe invites exactly that test.| | 40–200× faster, 40–400× cheaper than frontier LLMs | Self-benchmarked MEDIUM | Peaks of 193.6× faster / 444.6× cheaper come from four "workflow evals" TypeSafe designed — reference answers are the average of GPT-6 Astra and Fable 5.1, and the workflows were built by TypeSafe's own team. The company explicitly says "some bias could exist" and these are "on the higher end of real world gains." LLM-side numbers come from OpenRouter pricing.| | Frontier-level intelligence on decision tasks | Self-benchmarked MEDIUM | Their own demo's only disagreement with GPT-5.6 Terra was on an answer they call "genuinely ambiguous." No independent third-party evaluation exists yet — that's the gap to watch.| | "Can't hallucinate" | Defined carefully MEDIUM | Accurate as stated: it can't hallucinate *type errors* or out-of-schema values. The content can still be wrong if the state is wrong, or if the probability itself is miscalibrated. "Zero hallucinations" is the marketing compression of a precise, defensible claim.| The demos are where the abstraction becomes tangible. A **Doom bot** running at ~10 queries per second — roughly $7/hour at list price — making reactive decisions off structured game state. **Wikiracing**, where each step is choosing between thousands of links and not hallucinating matters compoundingly, with Jev finishing in fewer steps than the LLMs. Neither is a benchmark; both are a statement of what 100 ms decision latency makes possible. TechCrunch, The Register, Forbes, and SiliconANGLE all covered the launch from the same core fact set — the "445×" headline number, meanwhile, was correctly flagged by at least one outlet as self-tested. ## 05 The Name Is the Thesis: Jevons Paradox Jev is named after **William Stanley Jevons**, the 19th-century English economist. In 1865 he documented something counterintuitive: when steam engines became more fuel-efficient, coal consumption didn't fall — it *rose*, because efficiency made coal cheap enough to use everywhere it had previously been uneconomical. Efficiency gains, Jevons observed, expand total demand rather than shrink it. TypeSafe is applying that directly to intelligence. Almeida: "We expect machine intelligence to follow a similar path to coal. Every order of magnitude drop in the cost of intelligence unlocks orders of magnitude more use cases." At $0.042 per million input tokens with free output, the economics flip. Decisions that previously cost more than the value of the decision now cost less than the value of the electricity. That's not optimization — that's **category creation**. Why this is the part that's good for us Every prior "cheaper model" story was a substitution story — do the same task for less. Jevons paradox is an *expansion* story: the use cases that never existed because the inference was too slow or too expensive simply appear. A decision engine that costs nothing to query becomes a substrate — the way electricity stopped being a purchased output and became an invisible utility inside everything else. The name on the model is a prediction about its own diffusion. ## 06 What the New Era Looks Like in Practice Strip away the "first of its class" framing and Jev is a description of where production AI is heading anyway. Chat was the demo interface; **decisions are the product interface**. TypeSafe's own use-case list, translated into what a developer actually builds: ### Smart if-statements Structured outputs slot into ordinary software as fuzzy decision rules — classify, route, score, extract, branch where hand-written logic is too brittle. The surrounding code constrains the model's freedom, which is exactly what makes it composable into reliable systems. This is the "AI-powered workflow" in its most honest form: not an agent that chats, but a predicate your code can call 10,000 times a second. ### Real-time applications At 70–500 ms, intelligence moves into the interaction loop. Fraud scoring on a transaction as it arrives, personalization while the page renders, anomaly branching in a game or a robot controller. LLMs at 3–329 seconds can only live in background jobs; Jev lives in the hot path. ### Verification of everything Perhaps the most underrated use case: **score, judge, verify, guardrail, and detect jailbreaks** in other models' prompts, reasoning traces, and outputs. The era of LLM agents arrives with a second model class whose entire job is to be the referee — cheap, fast, and calibrated, so the referee can run on every single output, not a 5% audit sample. ### Map-reducing over big data Parallel question evaluation over a state is, structurally, a map-reduce. TypeSafe's pitch: turn petabytes of unstructured data into features and insights by fanning out atomic questions across it — with the free output tokens meaning the cost lives entirely in what you send, not in what you get back. Notice what all four have in common: none of them need a chat window. They need a *function* — unstructured state in, typed probabilistic decisions out, with the honesty of a confidence score attached. That's the whole era in one sentence. Chat models will keep winning the consumer layer; the infrastructure layer is being quietly re-plumbed around models like Jev. What this is not Jev does not replace frontier LLMs for generation, reasoning chains, coding from scratch, or anything that requires open-ended text. It also doesn't eliminate judgment: a calibrated 0.7 is still a probability, and "higher confidence means higher accuracy" is a property of the *distribution*, not a guarantee per call. The era this model opens is one where the unit of AI value is the decision — fast, typed, priced per input, and honest about its own uncertainty. ## 07 Timeline & What to Watch 2024 #### TypeSafe AI founded San Francisco. Diogo Almeida (ex-OpenAI, ~4 years on RLHF/InstructGPT/ChatGPT/GPT-4), Erik Gafni, Sasha Sheng. Two years of stealth follow. SEP 15, 2026 #### Stealth exit: Jev + $40M seed First System One model released in limited early access. DCVC-led $40M seed round announced the same day; Forbes reports a $200M valuation. TechCrunch, Forbes, The Register, and SiliconANGLE cover it within days. LATE SEP 2026 #### `jev-1.13.0` — the version the API actually serves The current release per the official docs. Versioned IDs are accepted by the API whether or not they appear in `GET /v1/models`; aliases move when new releases ship. Versioned IDs pin your tuned confidence thresholds against a specific build. NEXT → #### Three signals that the era is real (1) An independent benchmark from a third party — Artificial Analysis or a lab-level eval — rather than TypeSafe's own workflow suite. (2) A public technical report: no architecture, weights, or training data details have been published, and "transformer-based, synthetic data" is currently the whole spec. (3) Non-English parity and multimodal input — both explicitly absent at launch. Watch these more than the version number. ## 08 The Bottom Line The most interesting thing about Jev isn't that it's fast. Fast models exist. It's that the *objective function* moved: from writing what humans prefer, to deciding with probabilities honest enough for software to act on. That's a different animal, and it's aimed at the part of AI's promise that kept not showing up — automation, at machine speed, with machine-readable confidence. The numbers TypeSafe can prove today are the boring ones, and they're sufficient: sub-second latency, near-zero output cost, and a guarantee of zero type errors by construction. The 40–200× / 400× headline multipliers are self-benchmarked and self-labeled as such — respect the humility, don't adopt the marketing. If even a fraction of those gains hold in independent tests, Jevons' 1865 coal curve gets redrawn for machine intelligence: the utility that was always coming, priced at the point where it stops being a purchase and starts being an assumption. The chat era taught machines to talk. The decision era teaches software to trust them. Jev is the first model built for that second era — and it's the right name for a bet that the cheapest intelligence will end up being the most used. ## ↺ Related Articles [GPT-6 Astra vs Claude Opus 5.5: The Two Flagships That Never Fully Met](/gpt-6-astra-vs-claude-opus-5-5.html) [Top AI Models 2026: The Verified Ranking](/top-ai-models-2026-claude-fable-5-gpt-5-6-sol-kimi-k3-qwen3-8-glm-5-2.html) [Kimi K3: Moonshot's 2.8T Open Frontier Intelligence Model](/kimi-k3-open-frontier-intelligence.html) **Sources:** TypeSafe AI — "Introducing System One Models & Jev" (Diogo Almeida, Sep 15, 2026, typesafe.ai/blog) · TypeSafe AI official documentation (docs.typesafe.ai/models — specs, aliases, rate limits, data handling) · Wikipedia — "Jev (AI model)" (founding, release, funding, founders, RLCD) · Forbes — "This $200 Million Startup Wants To Fix AI's Overconfidence Problem" (Rashi Shrivastava, Sep 15, 2026) · TechCrunch — "A new kind of AI model from a ChatGPT inventor is thrilling developers" (Tim Fernholz, Sep 18, 2026) · The Register — "TypeSafe AI debuts model for machines that plays Doom" (Thomas Claburn, Sep 16, 2026) · SiliconANGLE — "TypeSafe AI exits stealth with $40M to build AI for use by software" (Sep 16, 2026) · TechStock² — "TypeSafe AI Raises $40 Million for Jev, but Its 445x Cost Claim Is Still Self-Tested" (Sep 17, 2026). All accessed and verified Sep 27, 2026. This article was drafted with AI assistance and reviewed by a human editor. ZVHH — AI Tools & Software Reviews © 2026 [Home](/)[Agent feed](/index.md)