TypeSafe Releases Jev Model for Non-Autoregressive Programmatic Logic
TypeSafe, founded by ChatGPT co-inventor Diogo Almeida, launched Jev to handle structured decisions directly within application code without conversational string generation. The architecture uses parallel sampling to return type-safe values in 70 to 500 milliseconds at 4.2 cents per million input tokens.

Impact: High
Why it matters
You can replace slow, expensive chat completions in agent decision loops with sub-second, hallucination-free deterministic routing.
TL;DR
- 01Jev replaces autoregressive text generation with parallel sampling for type-safe decisions in 70–500 ms.
- 02Input pricing is fixed at $0.042 per million tokens with completely unmetered, free output tokens.
- 03RLCD training ensures output probabilities are calibrated directly to programmatic execution accuracy.
Key facts
- Input Token Price
- $0.042 per 1M tokens
- Output Token Price
- $0 (unmetered)
- Response Latency
- 70–500 ms (internal benchmark)
- Execution Speedup
- Up to 193.6x faster than frontier models (self-reported)
- Selection Cardinality
- Up to 255 discrete options
Bypassing Text Generation for Programmatic Decisions
Software pipelines frequently call conversational frontier models merely to select an action or pick an enum value. TypeSafe AI, led by ChatGPT co-inventor Diogo Almeida, emerged from stealth with Jev—a specialized System One model architected specifically to eliminate strings from the decision loop. Rather than predicting token sequences, Jev consumes unstructured application state and evaluates structured schemas in a single parallel query.
Parallel Sampling and RLCD Calibration
Instead of relying on standard Reinforcement Learning with Human Feedback (RLHF), TypeSafe trains Jev using Reinforcement Learning for Calibrated Decisions (RLCD). This approach ensures confidence scores correlate mathematically with logic execution accuracy. The system's hardware-aware parallel sampler handles candidate spaces of up to 255 discrete choices via a two-stage scoring mechanism, constraining outputs to predefined schemas and avoiding parsing wrappers altogether.
Latency, Pricing, and Real-World Throughput
In vendor evaluations, Jev achieved end-to-end response latencies of 70–500 milliseconds, compared to 3–329 seconds recorded for conversational frontier deployments. Across multi-step decision branching benchmarks, execution speeds reached up to 193.6 times faster than frontier baselines.
Economic metrics are equally striking: input processing costs $0.042 per million tokens, compared to typical API rates ranging from $0.20 to $10. Because outputs are resolved through parallel state sampling rather than autoregressive generation, TypeSafe does not meter or charge for output tokens. In dynamic stress testing running a Doom game bot at 10 queries per second, operational compute costs stabilized at approximately $7 per hour. Early developer access is now open via a deployment waitlist.
Try it in 2 minutes
curl -X POST https://api.typesafe.ai/v1/decide -H 'Authorization: Bearer $TYPESAFE_API_KEY' -H 'Content-Type: application/json' -d '{"state": "queue_depth=420 latency_p99=850ms error_rate=0.04", "options": ["scale_up", "throttle_inbound", "maintain", "failover"]}'bash
✓ When to use
- Replacing slow chat completion calls in high-speed agent routing, feature extraction, and branching logic.
- High-throughput event classification where syntax guarantees and zero hallucinations are mandatory.
- Cost-critical pipelines processing high volumes of input context that demand sub-second decisions.
✕ When NOT to use
- Open-ended conversational generation, long-form copy writing, or customer-facing chat.
- Generative code synthesis requiring token-by-token reasoning and multi-line script creation.
- Tasks that depend on parsing complex natural-language nuances across unbounded string outputs.
What to do today
- Join the TypeSafe deployment waitlist to evaluate Jev on high-throughput decision pipelines.
- Identify backend agent routers that currently use slow chat completions for simple enum selections.
- Benchmark internal decision graph latency against Jev's 70-500 ms response profile.
Sources