What Is Jev? TypeSafe AI's Decision Model Explained
Direct answer: Jev is a probabilistic decision model from TypeSafe AI. It takes state plus typed questions and returns structured decisions with probabilities. It does not write Magicdoor's answers. Magicdoor uses Jev as a routing signal, then DeepSeek V4.1 Flash, GPT-5.6 Luna, or GPT-5.6 Sol responds.
Fact-checked September 21, 2026. This page owns the Jev and decision-model explanation. See the automatic model selection pillar and exact Magicdoor Auto policy for routing details.
Decision model versus chat model
| Question | Jev decision model | Generative chat model |
|---|---|---|
| Primary job | Evaluate state and return typed decisions | Generate text, code, or other content |
| Output | Choice, Score, or yes/no probability | Free-form token sequence |
| Typical use | Route, classify, score, verify, branch | Answer, explain, draft, reason, create |
| Magicdoor role | Supplies routing probabilities | Writes the user-facing answer |
TypeSafe calls Jev its first System One Model, borrowing the fast, intuitive “System 1” idea from Daniel Kahneman. That is TypeSafe's category and framing, not a claim that every decision is infallible.
What typed decisions mean
TypeSafe exposes Noul for a yes/no probability, Choice for one defined option plus a distribution, and Score for an ordered rubric. The application defines the question and threshold. A Noul value of 0.30 is not “30% difficult”; it is a probability for the stated condition.
Decision models matter for model routing because they return bounded results that software can apply directly. They can also choose a tool, score risk, verify output, or send uncertain cases to review. The surrounding policy still owns thresholds, capabilities, fallbacks, accounting, and observability.
How Magicdoor uses Jev
For each Experimental Auto message, Magicdoor asks whether the latest turn requires substantive inference/judgment or reconsidering a disputed answer, and whether it requests code/data execution.
| Policy result | Answer model |
|---|---|
| Quality probability at least 0.30 | GPT-5.6 Sol |
| Otherwise, execution at least 0.50 or hard OpenAI capability | GPT-5.6 Luna |
| Otherwise | DeepSeek V4.1 Flash |
Jev does not choose from a hidden catalog or generate the answer. Magicdoor owns the pool and quality-first-v5 policy. Manual model selection bypasses Jev. See all available models on the models page.
TypeSafe's claims, with attribution
TypeSafe's September 15 launch reports a $0.042 per million input-token price, output tokens described as free, and 70-500 ms end-to-end TypeSafe response time. Its workflow evaluations reached up to 193.6 times faster and 444.6 times cheaper than compared language-model workflows.
Vercel describes Jev as a probabilistic decision model and repeats those figures as claims reported by TypeSafe. TypeSafe also publishes caveats: speed tests were generally run from West Coast laptops, the largest workflow gains are expected to be at the high end, workflow authors can introduce bias, and comparison setup matters.
These are TypeSafe vendor claims, not Magicdoor measurements. Magicdoor does not claim that Auto runs at those speeds, saves those percentages, or produces better answers because it uses Jev.
Magicdoor's evidence is different
Magicdoor ran 164 synthetic scenarios and made 324 live TypeSafe requests. That tested route selection and policy behavior. It did not generate and compare final answers, so it does not show real answer-quality superiority.
Limits and trust boundaries
- Jev is a routing component, not the answer model.
- Typed shape does not guarantee the decision matches user intent.
- Probabilities require policy thresholds and evaluation.
- The 2.5-second deadline can fail closed to Sol.
- Magicdoor excludes files and tool payloads, but user text can contain sensitive strings or URLs. This is not full redaction.
- TypeSafe created Jev. Its use does not imply partnership or endorsement.
FAQ
What is Jev from TypeSafe AI?
Jev is TypeSafe AI's probabilistic decision model. It evaluates supplied state against typed questions and returns choices, scores, or yes/no probabilities instead of writing a free-form chat answer.
Is Jev a replacement for chat models?
No. Jev is designed for structured decisions inside software. A generative model is still needed to write an answer, explanation, or other free-form output.
How does Magicdoor use Jev?
Magicdoor uses Jev to evaluate two routing signals for each Experimental Auto message. Magicdoor's quality-first-v5 policy then chooses DeepSeek V4.1 Flash, GPT-5.6 Luna, or GPT-5.6 Sol to answer.
Did Magicdoor create Jev or receive a TypeSafe endorsement?
No. TypeSafe AI created Jev. Magicdoor uses its API as one component of Magicdoor's routing policy, which does not imply TypeSafe endorses Magicdoor.
Sources
Accessed September 21, 2026.
- TypeSafe launch for terminology, price, speed, workflow results, and caveats.
- TypeSafe API and Noul documentation.
- Vercel AI Gateway announcement.
- Vercel Jev overview.
Related Resources
Automatic vs Manual AI Model Selection: Which Should You Use?
Decide when automatic model selection saves time and when choosing an AI model manually gives you better provider, capability, and cost control.
Automatic Model Selection: How AI Model Routing Works
Learn how automatic model selection routes each prompt, what a trustworthy AI model router should disclose, and when manual choice is still better.
Image Model Comparison - When to Use Each magicdoor.ai Image Model
Practical guide to choosing between magicdoor.ai's current image models for generation, editing, background cleanup, higher-resolution output, and upscaling.
Selecting the Right AI Model
Current magicdoor.ai model lineup and practical guidance on when to use each option.