제브(Jev): 기존 프런티어 모델보다 40~400배 저렴하고 20~200배 빠른 신규 모델 공개

TypeSafe announces System One models and Jev Read More TypeSafe AI Manifesto Our Team Join Waitlist TypeSafe announces System One models and Jev Read More TypeSafe AI Manifesto Our Team ∵ Back Company News Sep 14, 2026 Introducing System One Models and Jev Diogo Almeida, founder, TypeSafe Models have been superhuman at chat for years, so where is all the automation? This has been my driving question for the last four years. At OpenAI, I helped build the methods that made language models useful at following instructions and talking with people. That work ended up as the research behind ChatGPT. At the time, I thought maybe chat models would lead to AGI, but despite the hype it became obvious to me that there was something really big missing. After two years in stealth, countless technical challenges, and research breakthroughs… I am beyond excited to announce that today, TypeSafe AI is releasing our first System One Model : a new class of frontier models built to make fast, structured decisions that software can use directly. We built a new stack entirely focused on automation: with a new model architecture, parallel sampler for maximum efficiency, and training method we call Reinforcement Learning for Calibrated Decisions (RLCD). Our first public model is Jev , available today in early access. Jev achieves similar levels of intelligence on System One tasks compared to existing LLMs, while being two orders of magnitude faster and more efficient. While Jev gives up string generation, it’s optimized for structured outputs and can’t hallucinate. Think of Jev as a frontier-intelligence function call: unstructured state in, typed probabilistic decisions out. Extraordinary claims require extraordinary evidence so see below for the receipts. 💅 Frontiers, Old and New Evidence / Technical Results We love skeptics, and are skeptics ourselves. There are some claims you can easily verify: Speed per call: We truly are that fast, though our published evals are generally run from our laptops on the West Coast (this is where our service is currently based). Cost per call: We make our pricing transparent. We can’t prove it isn’t subsidized; we’ll need the long-term to prove the sustainability of our pricing (which we expect to go down, not up). No type errors : This would be an easy thing to falsify with just a single counter-example, but it is mathematically impossible. For our bolder claims, we want to provide as much nuance as we can. Side-by-side demonstration Our side-by-side demo shows a key difference between our models and LLMs: Jev outputs all probabilities in parallel instead of autoregressively generating by token. Strings are extremely powerful and general, but costly. “Giving up” strings actually gives us a lot of superpowers! Nuance: For people with early access to TypeSafe, here is the actual query . The query is highly simplified and questions were chosen to have descriptive, human-readable keys so that the output on the screen is understandable. The state is also a short, dense, and detailed paragraph, to emphasize the difference in sampling methodology. The relatively shorter input paints our model in an advantageous light. For the keen eyed, for the recorded run, the only disagreement with GPT-5.6 Terra is on “Churn likelihood level”. The actual answer seems genuinely ambiguous to us. We used GPT-5.6 Terra with default reasoning for this example, because we’ve found it to be the most comparable at intelligence to Jev on average. Fun fact: a similar demo was what convinced us to go all-in in the direction of System One Models! Workflow evals We made a new type of evaluation to measure how well AI works within code. We don’t optimize for a ground truth classification orand allow the harness and model to change (potentially allowing for overfitting via harness engineering). Instead, we assume there is a correct compute graph (a “workflow” represented in code) and use the predictions of the largest, smartest, and most expensive external models as reference probabilities. Rephrased: every model gets the same workflow. We test how they compare to the average of the smartest models (in this case, Astra and Fable). Jev is off the charts – owning the Pareto frontier for almost 2 orders of magnitude. We also compare to models with a generated prompt doing all the logic in their chain-of-thought, but this tends to do significantly worse than using the workflow itself. Note that the calls here are significantly more complex than the side-by-side demonstration above. That’s because they’re more representative of the types of production workloads needed for true business automation. Below is the simplest of the 4 workflows we’re publishing: The most reliable real-world workflows tend to have many independent, decomposed questions, with fine-grained behavior that’s dependent on probabilities instead of discrete decisions. The end result is discrete branching, but how we get to a final answer involves a lot of domain-specific engineering that needs to be done highly consistently. See our workflow evals site for all the details: examples, disagreements, full queries, and each workflow. Nuance: This is where the claims of 193.6x faster, 444.6x cheaper on our home page comes from, and we expect that these are on the higher end of real world gains. These content of these workflows were not deliberately chosen nor constructed to make our model look good, and are not in our training distribution. However, they were made by individuals on our model capabilities team, so some bias could exist. We use the average of GPT-6 Astra and Fable 5.1 as the reference answer, which biases answers towards OpenAI and Anthropic’s models. We likely underestimate the relative performance of our model and DeepSeek’s models. The LLMs use our System One LLM wrapper, which constrains LLMs to output structured decisions compatible with our API. We have found this to be the most accurate way to get decisions from LLMs, but this tends to be slower and more expensive than giving decisions without probabilities. Hallucination and Type-safety Hallucination and type-safety are intrinsically related, and we think the latter is table stakes for automation. Having a hallucinated tool call is inconvenient in an agent, but is an absolute deal-breaker if it’s part of a system with latency guarantees or it’s buried several layers deep in a dependency chain. Existing models, no matter how smart , still hallucinate and have type errors. Nuance: The numbers for LLMs are from OpenRouter i.e., there almost certainly is bias here: more complex queries might be routed to better models. Our number is not empirical. Schema matching is guaranteed, thus we can confidently add 0% into the plots. Fun Demos Perhaps the most exciting part of our work is enabling new use cases. We have a lot more to show you, but here are a couple of the team’s favorites: Doom We love how this doomo doomonstrates real-time intelligence and what can be doone with code + AI. The engineer behind it was worried about making 10 queries a second (which ends up costing ~$7/hour), but the rest of us agreed that was lower than expected! This is so fun we intend to not only release an in-depth walkthrough, but also host some events to hack on this. Nuance: The demo is on structured state as a data structure with text, not on images (yet…) A non-AI doom bot could play better, but we wanted a bot that was reactive to different representations of game state, and most importantly… following instructions was cool as heck! Wikiracing The objective of the game is to start on one Wikipedia page and reach a specific other Wikipedia page using only links you come across while traversing. Each step can mean choosing between hundreds to thousands of links! It’s a great playground for demonstrating not just intelligence-per-second, but also the compounding benefits of not hallucinating with high-cardinality choices. Nuance: As far as we know, it was complete