ENPT

Jev

Last updated:

Waitlist70–500ms$0.042/M input

Quadrant scores

See the full quadrant

Scored with the public quadrant rubric (maturity × capability; bubble = adoption). Revise as evidence lands.

  • Maturity4.1/10

    Waitlist / early access keeps availability low; public docs and early integrations (OpenRouter, framework PRs) help, but there is no public SLA yet.

  • Capability7.4/10

    Full choice / score / boolean surface with strong latency claims; RLCD is cited but independent public accuracy benches are still thin (partly vendor-scored).

  • Adoption58/100

    Largest launch-week signal in the category (HN, press, early apps), but still days old — not mainstream awareness yet.

Vendor claims

Jev is the first publicly available System One model from TypeSafe AI. It is not a chatbot and does not generate free text. You send program state plus a map of typed questions; it returns structured answers with calibrated probabilities — typically in 70–500ms (warm calls often cited near ~100–200ms).

The category name borrows Daniel Kahneman’s dual-process framing: System 1 is fast and automatic; System 2 is slow and deliberative. Frontier LLMs behave like System 2 (token-by-token generation). Jev is positioned as System 1 for software — classify, route, score, gate — and leave essays to an LLM when you actually need one.

“Everybody is arguing about which chat model ‘wins’ 2026. Wrong fight. Jev is not trying to write you a prettier paragraph.” — @juliench82

Specs

Attribute Value
Company TypeSafe AI (San Francisco)
Founder Diogo Almeida (ex-OpenAI; RLHF / InstructGPT lineage)
Co-founders Eric Gafni, Stasa Shishik (reported in launch coverage)
Funding $40M seed led by DCVC ($200M valuation in some reports)
Launch
Status Early Access (waitlist)
Current model jev-1.13
Latency 70–500ms
Pricing $0.042/M input tokens; output free
Training story RLCD — Reinforcement Learning for Calibrated Decisions (vendor term)
Architecture Non-autoregressive; answers multiple questions in one parallel pass
I/O shape state + typed questions → typed answers + probabilities / confidence
Docs docs.typesafe.ai

How a call works

Unlike chat APIs (messages → streamed tokens), Jev’s contract is decision-shaped:

  1. Provide context / state (text or structured payload your code already has).
  2. Attach one or more typed questions (choice, score, or yes/no / boolean — docs also discuss related shapes such as Noul).
  3. Receive structured answers your code can branch on — no “almost-JSON”, no narrator preamble.

That is why early adopters describe it as removing the chatbot tax: you do not pay the model to narrate a decision you only needed as a branch condition.

Question types

Choice

Pick among labelled options; get a distribution over options.

Typical use: sentiment buckets, tool selection, ticket category, “which agent should handle this?”

Score

Numeric score on a rubric with a confidence measure.

Typical use: urgency 1–10, lead quality, relevance ranking.

Boolean / yes–no

Probability that a proposition holds.

Typical use: spam?, PII present?, evidence supports claim?, allow tool call?

Why “System One” — and Dual-Process stacks

Kahneman’s Thinking, Fast and Slow is the marketing and architecture metaphor: Jev as the fast path; an LLM as the slow path when ambiguity or generation is required.

In the wild (Sept 2026), builders already ship Dual-Process patterns:

  • System 1 (Jev): cheap gate / classify / route in milliseconds.
  • System 2 (Gemini, Claude, GPT, …): fire only for deep reasoning or text generation.

Open examples include safety gates and Discord bots that keep the frontier model off the hot path until Jev says the request needs it (@taro_president).

Why it cannot “hallucinate” (and what that does not mean)

The vendor claim rests on restricted output: Jev only chooses among provided options / schema slots and never invents free text, so it cannot emit a novel false fact as prose.

It can still be wrong about which option is correct. Restricted output ≠ perfect judgment. Treat confidence as a routing signal (auto-handle vs escalate), not as proof.

Known jaggedness (jev-1.13)

TypeSafe documents the sharp edges of jev-1.13 in Model jaggedness (reviewed 2026-09-17). Short version: it is fast and good at common-sense System One judgment, but literal, weak on math/numbers/dates, and worse when you add indirection, noisy state, or adversarial text. Many of these are expected to improve in later versions.

“jev-1.13 answers the question you wrote, not the one you meant. Scoping words, negations, and implied conditions are read at face value.”

Practical takeaways

Failure mode Do this instead
Literal reading Write the exact condition; put boundary cases in criteria
Math, counting, hex/RGB, score interpolation Keep arithmetic in code; ask semantic questions only
Date / time ordering Extract parts with Choice; compare in code
Indirection / multi-hop Flatten instructions; name the relevant state fields
Large irrelevant state Filter in code first (context rot is real)
Adversarial / injected framing Precise criteria; test edges before deploy
Contradictory instructions vs criteria Align them — treat criteria as part of the instruction
Assumed invariants (Noul vs Choice, P vs 1−P) Don’t transfer thresholds across question shapes
Generation / free extraction Use a generative model or regex; let Jev choose

Also avoid System Two–style tasks (extra layers of indirection), hiding several judgments in one question, and asking for anything code can compute exactly.

Primary source: docs.typesafe.ai — Jev 1.13 jaggedness.

Reception (first 72 hours)

Signal Detail
Hacker News Launch post ~1,890 points / ~495 comments
Press Coverage from The Register, SiliconANGLE, Forbes, Tech Brew, etc.
Naming “Jev” nods to economist William Stanley Jevons (Jevons paradox) in several explainers
Demand Early-access waitlist; API demand spikes reported after launch

Distribution (checked)

  • OpenRouter: typesafe/jev-1.13 — $0.042 / $0 per 1M tokens (in/out), 32K context (page checked 19 Sep 2026).
  • Vercel AI Gateway: changelog id typesafe-ai/jev (see news).

Ecosystem traction

Within days of launch, open-source and product repos started wiring Jev as a decision / router / judge layer rather than a chat model:

Project Role
pydantic/pydantic-ai TypeSafeModel adapter for typed question outputs
NVIDIA-NeMo/Switchyard type_safe_classifier routing
pipecat-ai/pipecat Judge / router / Flows service hooks
LangChain Official langchain-typesafe: TypeSafeClassifier, ModelRouterMiddleware, AutoModeMiddleware
LiteLLM Guardrail jev-compaction: drop stale tool results via Jev relevance scores
Community demos Browser automation (decide → act), email batch classification, NES/Mario “one choice per frame”, agent tool gates

LangChain and others published guides framing Jev inside agent loops as structured decision steps rather than another completion endpoint.

Context compaction (LiteLLM)

LiteLLM ships a TypeSafe compaction guardrail (blog, 18 Sep 2026): before the main model call, Jev scores older tool results for relevance to the latest user question. Results below a threshold (default 0.2) are replaced with a short removal notice; tool-call structure, system/user messages, and the latest assistant+tool exchange stay intact.

Classic example: weather lookup then shop hours — user asks when the shop closes → weather blob can drop, hours stay. Compaction is opt-in (guardrails: ["jev-compaction"] on the proxy / team); if Jev is down, default fail_open sends the original request. Jev is also reachable through LiteLLM’s /typesafe/v1/systemone pass-through.

Primary source: Reduce agent context with TypeSafe Jev and LiteLLM.

Community ecosystem (apps that call Jev)

Community roundup snapshot (@studio_yebisu, 18 Sep 2026; also r/WebAfterAI roundup, 17 Sep 2026). These are integrations and demos that use hosted Jev — not competing decision models. Star counts drift; treat as awareness, not ranking. We did not run every repo.

Also: classifier.dev — public HTTP/CLI/MCP wrapper over Jev (jev-1.13.0); fast = Jev, smart escalates uncertain cases to a reasoning LM.

Community index: awesomejev.com tracks hundreds of Jev-related repos/apps (snapshot ~561 entries / ~479 repos on 19 Sep 2026). Useful as a living directory — not a ModelSystem.One ranking, and not every entry is a catalog model. Our curated ecosystem table below stays selective.

Open logit-classifier stacks (not TypeSafe models — keep off the quadrant): simple-jev / simple-jev.featherless.ai (Featherless — any open LM → typed decisions via next-token logits; demo API + RFDT), SemIf, openjev-sglang.

Browser / PC / mobile

Project Role
browser-use/jev-ultrafast Browser agent: Jev picks ops/elements; small LLM only for typed text
awlevin/typesafe-computer-use macOS computer-use via OCR/accessibility + typed decisions
droidrun/mobile-jev Android phone control via Mobilerun
moritzkremb/jev-voice-browser Voice → intent → Playwright browser actions

AI coding / review

Project Role
tamaratran/fast-jev-compaction Compact Claude Code history by dropping low-value tool noise
thruwire/foreman Supervise Codex agent runs (continue / verify / stop)
devagrawal09/jev-review Structured git/diff review with local dashboard
gargpratyush/jev-router Per-turn model routing for Claude Code / Codex
EliaAlberti/jev-rules Select which Claude Code rules/docs to inject

MCP / skills / CLI

Project Role
kitze/skillbox Agent skill library + MCP; optional Jev skill recommend
itsmostafa/typesafe-mcp Unofficial MCP exposing Jev choice/score/boolean
jkudish/jev-mcp MCP tools: verify claims, screen injection/relevance, rank candidates
mrnugget/jev-shell-history zsh history suggest ranked by Jev

SDKs / language bindings

Project Role
kieranklaassen/ruby_llm-typesafe TypeSafe provider for RubyLLM — structured decisions only (rejects chat/stream/tools)

Search / databases

Project Role
realZachi/pg-jev PostgreSQL NL filter/classify/rank (rows leave to API)
superagents-lab/jev-search Web search pipeline: query + relevance via Jev
jexp/neo4jev Neo4j hop demo with Choice/Noul

Video / browsing

Project Role
kitze/unclutter Browser extension: hide ads/clutter via Jev
ChetasLua/jevmeter Score spoken lines in video (not fact-check)
trungdq88/youtube-sponsor-detection Detect/skip in-video sponsor segments

Guardrails / community

Project Role
DevMortimer/pi-warden Guardrails for Pi agents (loops, unverified “done”)
brainstormity/Jev-Moderation-Bot Discord spam/scam moderation

Marketing / GEO

Project Role
usenotra/notra GEO / AI-answer brand mention tracking (Jev for classify — verify in repo)

Smart home / sims / trading

Project Role
AboveColin/HA-Jev Home Assistant sensors/actions via Jev (not safety-critical)
fhshaik/typesafe-mario Mario emulator control from structured state
standardagents/jevpilot Three.js driving sim autopilot
RomanSlack/jev-drone MuJoCo drone sim tactical choices
jarrodwatts/jev-trader Experimental trading bot (mock/dry-run defaults; PnL unverified)

Fit / anti-fit

Fit when you need: classification, routing, scoring, semantic gates, guardrails, shadow-mode checks, branching in automations — anything where the product output is a typed decision.

Anti-fit when you need: explanations, drafts, multi-step tool-using chat, open-ended research, or any workflow that is the essay.

Architecture (independent reconstruction)

Speculative black-box reconstruction from Archer Hume — Jev’s Architecture Unmasked (17 Sep 2026). Not a TypeSafe confirmation. Numbers below are only those reported in that essay or by open reconstructions; treat MoE and exact head design as inferred.

Independent probing of the TypeSafe API (latency vs context, question isolation, option-set effects) plus prior art suggests a causal transformer reused for decisions: shared-state encoding, isolated question branches, and a direct probability readout instead of autoregressive text.

  1. Numeric readout, not AR decode — probabilities come from a head on hidden states (slot or pointer-style), not from generated “91%” tokens. Billing output_tokens in the essay is treated as accounting, not evidence of decode steps.
  2. Shared state + isolated questions — encode the state once (KV / prefix); each question is a branch that can read state but not sibling questions. Moving a secret from a sibling question into state changes visibility in probes.
  3. Causal backbone — likely a pretrained decoder LM with decision post-training (vendor: RLCD). Bidirectional encoder is not ruled out from the outside but is a worse fit for shared-prefix serving.
  4. Listwise options before choice — options appear to interact before the distribution is formed (irrelevant extra option shifts odds between existing ones; order sensitivity). Fits final-position slot head or pointer scoring over option states.
  5. Train the distribution; derive confidence — proper scoring on outcomes (log / Brier-style), then arithmetic confidence from the distribution (e.g. distance from uniform) — not a second “confidence LLM”.
  6. Sparse MoE — least certain — inferred for prefill-only compute; not measured. Essay flags this explicitly as speculation.
  7. Branches as a batch, not a chat — questions are independent work items over shared state; no answer→next-question decode chain inside one request.

Open reconstructions / peers: Kev (LoRA on Qwen2.5-0.5B), Laya (ModernBERT-large), NanoJev (Qwen3-0.6B + decision heads), jevlike (research option-attention starter). None are TypeSafe products.