20 Agentic Use Cases of TypeSafe AI’s Jev

Last week, TypeSafe AI released Jev, its first System One model. Founder Diogo Almeida previously worked at OpenAI on the instruction-following research behind ChatGPT.

Jev does not chat, write code or summarize. It takes unstructured state and returns typed decisions with calibrated probabilities. That makes it a natural fit for the thousands of small judgments inside an agent loop: which model to call, whether a command is safe, which passage is relevant, whether the agent is actually done.

How Jev Works

Every call sends a state (text or JSON) plus a dictionary of typed questions. TypeSafe’s docs define 3 primitives:

• Choice picks one option from a list and returns a probability per option plus confidence.
• Score rates the state on ordered rubric levels and returns probabilities plus confidence.
• Noul returns the probability (0 to 1) that a statement is true.

All questions are evaluated in parallel against the same state in one request. TypeSafe trains Jev with Reinforcement Learning for Calibrated Decisions (RLCD), so higher confidence should track higher accuracy. Choice supports up to 255 options.

The main claims, 193.6x faster and 444.6x cheaper, come from TypeSafe’s own workflow evals. The launch post says these figures sit on the higher end of real-world gains and use GPT-6 Astra and Fable 5.1 as the reference answer.

Interactive Explainer

Race a token-by-token LLM against Jev’s single pass, move a confidence threshold to see how code gates each decision, estimate monthly cost, and browse all 20 use cases.

Routing and orchestration

1. Model routing: Score request difficulty, then send it to a fast or strong model. LangChain ships this as ModelRouterMiddleware; jev-router does it per turn for Claude Code and Codex.
2. Skill selection: TypeSafe’s skill suggestion cookbook picks at most one skill from 182 in Nous Research’s Hermes catalog using 2 requests.
3. Typed function calling: The function calling cookbook maps natural-language trading requests to function names and closed-set arguments, gated by confidence.
4. Ticket triage and intent routing: One call returns department, frustration and urgency. The intent routing pattern sends each request to deterministic logic, a specialist LLM or a human.

Safety and guardrails

5. Tool-call risk gating: pi-warden asks whether a pending bash, write or edit is irreversible or off-task. It tells db:reset after “reset the database” apart from db:reset after “add a column”. LangChain’s AutoModeMiddleware returns an error for risky calls.
6. Read-only auto-approval: jev-auto-approve is a Claude Code hook that auto-approves only at p ≥ 0.95 and approved 0 of 8 state-changing commands in its published calibration.
7. Secret-leak guard: jev-secret-guard sends masked strings to Jev and blocked 6 of 6 secrets and 0 of 6 benign strings in its calibration.
8. Prompt-injection screening: In TypeSafe’s RAG passages cookbook, cosine similarity ranked a planted injection first at 0.584. Jev scored it 0.99 and dropped it.
9. LLM input and output guardrails: The guardrails cookbook thresholds hazard probabilities to pass, review, block or route every message.

Retrieval and grounding

10. Reranking: On 40 CLERC legal queries, the reranking cookbook lifted top-1 accuracy from 5% to 18% and top-10 from 38% to 62%.
11. Citation verification: The citation check cookbook uses one Choice to decide whether a source section supports, contradicts or says nothing about a claim.

Computer, browser and real-time control

12. Browser agents: Browser Use’s Jev Ultrafast picks an operation and DOM element in one request and finished a Google Flights search in about 7.1 seconds.
13. Desktop computer use: typesafe-computer-use OCRs the macOS screen and lets Jev classify the next action for about $0.0002 per step.
14. Mobile agents: Mobile Jev decides each Android tap, reaching an Uber payment screen in about 21 seconds and 9 actions.
15. Real-time game agents: TypeSafe’s Doom demo runs about 10 queries per second, roughly $7 per hour, on structured game state.

Agent quality and memory

16. Loop stagnation detection: ProgressGate judges the trajectory, and code returns CONTINUE, WARN, REPLAN or HALT.
17. “Done” claim verification: jev-belay checks the transcript for evidence before trusting a Claude Code agent’s “done” claim.
18. Context compaction: fast-jev-compaction scores tool calls and drops stale ones instead of summarizing context.
19. Trace mining for memory: Beacon by Asymptote Labs uses Jev to find which runs across Claude Code, Codex, Cursor and OpenCode are worth turning into reusable skills.
20. Semantic linting: jev-lint flags team-rule violations at edit time for Claude Code and Codex.

Jev vs Closest Competitors

Open-model figures are self-reported by each project on its own harness, so treat them as directional. OpenRouter’s Banking77 test is the cleanest head-to-head: Jev was 3.3 points less accurate than Claude Opus 5, 13x faster at the median, and about 1/22 the cost.

Key Takeaways

• Jev returns typed Choice, Score and Noul answers with probabilities, never free text.
• TypeSafe lists $0.042 per million input tokens, free output, and 70 to 500 ms latency.
• Best agent fits: routing, tool-call gating, reranking, citation checks and injection screening.
• On Banking77, Jev scored 81.0% vs 84.4% for Claude Opus 5, at 13x lower median latency.
• Schema-safe does not mean correct: calibrate thresholds on your own traffic first.

FAQ

• What is Jev? Jev is TypeSafe AI’s first System One model. It returns typed Choice, Score and Noul answers with probabilities instead of generated text.
• Is Jev an LLM replacement? No. It sits beside an LLM. The LLM plans and writes; Jev handles bounded decisions such as routing, gating and verification.
• How much does Jev cost? TypeSafe lists $0.042 per million input tokens, with output tokens free.
• Can I run Jev locally? Not TypeSafe’s model. Open projects like Laya and kev implement the same /v1/systemone interface on your own hardware.