Skip to content

Build8 publishers3 min readPublished

Jev can't return malformed JSON. It can still pick the wrong allowed answer

TypeSafe's $40 million seed funds a model that returns only predeclared types. Schema errors become impossible by construction. That leaves developers trusting the calibration of its confidence scores.

The Engineer · Build desk

Illustration accompanying Jev can't return malformed JSON. It can still pick the wrong allowed answer

What happened

  • Diogo Almeida, Erik Gafni and Sasha Sheng took TypeSafe AI out of stealth on September 15th with a $40 million seed round led by DCVC and a first model, Jev, that returns bounded decisions instead of prose.
  • Developers declare the allowed response types up front and submit unstructured state; Jev returns choices, scores or boolean probabilities with confidence estimates the application can act on or escalate.
  • TypeSafe prices Jev at $0.042 per million input tokens, or $42 per billion, and does not charge for output tokens at all.
  • In a Pong comparison built by Ably co-founder Matthew O'Riordan, Jev returned 47 decisions in the first 12 seconds while three chat models returned three, two and two.
  • O'Riordan calls the build a latency demo and says the chat models picked the correct Pong move 95% to 100% of the time, so Jev's edge came from answering more often, not playing better.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

  • constraint Anything with a label space above 255 has to run the two-stage score-then-select pipeline, so a team budgeting latency for a large taxonomy has two model calls to budget for.
  • decision Somebody has to pick the confidence level at which software acts without a human. That threshold is application code, and it has to exist before the typed interface buys anything.
  • exposure A buyer who needs calibration has to measure it on their own labelled data, because the vendor's published evaluations score agreement with two other models.
  • cost TypeSafe says its own long-term pricing sustainability is unproven, which leaves repricing risk with whoever builds a high-volume decision loop on the current rate card.

When TypeSafe says zero hallucination, it means Jev cannot return an off-schema answer or a malformed tool call, because its possible outputs are fixed before the call [7]. The company says schema matching is guaranteed and type errors are mathematically impossible [25]. Jev can still pick the wrong allowed answer [7]. The only signal a developer gets for that is the confidence estimate returned alongside the decision [5].

The speed comes from the same restriction. A chat model generates tokens sequentially even when the API pins its final response to a JSON schema [6]. TypeSafe says Jev samples multiple typed outputs in parallel and gives up open-ended string generation entirely [6]. Behind that is a new architecture, a parallel sampler, and a training method the company calls Reinforcement Learning for Calibrated Decisions [9]. The founders spent roughly two years on the architecture, sampler and training process [8].

The Pong recording and the marketing multiples measure different things. Against Jev's 227 millisecond average, Claude Haiku 4.5 at 2.5 seconds is about 11 times slower, Gemini 3.8 Flash at 3.2 seconds about 14 times, and GPT-5.6 Sol at 3.5 seconds about 15 times [27]. The 47 decisions in the first 12 seconds work out to 255 milliseconds each, close to that reported average [28]. TypeSafe's own claim is 40 to 200 times faster on similarly intelligent System One-shaped queries, with a 193.6x speed example on its homepage [11][12].

Those larger numbers come from workflow evaluations that are harder to read across. They use identical compute graphs and score outputs against the average probabilities from GPT-6 Astra and Fable 5.1, not against ground-truth labels [13]. Four workflows are published, and the company's own model-capabilities team built them [14]. The LLM baseline runs through TypeSafe's System One wrapper, which constrains conventional models to compatible structured decisions and may affect their speed and cost [15]. Most tests ran from laptops on the US West Coast, where the service is based [16]. TypeSafe says the homepage figures likely sit near the upper end of real-world results and that long-term pricing sustainability remains unproven [12].

The demo conditions are documented: structured-output requests at temperature zero, reasoning disabled, no retries, one shared Vercel AI Gateway key, and latency measured on the server-side model call [21]. O'Riordan published the source code and the recorded statistics [31]. Every lane also receives an intercept coordinate, so the spatial reasoning that a 2024 Atari-GPT study found multimodal language models struggled with as low-level game controllers never comes into play [23].

"People can't be the only consumers of intelligence," Almeida said in TypeSafe's launch announcement [3]. OpenAI credits him under "Foundational RLHF and InstructGPT work" in its GPT-4 contributor record [2], and he describes Jev in the September 15th launch post as a "frontier-intelligence function call" [4]. For any of this to transfer to another workload, the decision has to fit inside 255 choices, or tolerate the two-stage score-then-select pipeline larger choice sets require [17]. And the confidence numbers have to be calibrated against that workload's own labels. The published evaluations test something else [13].

What to watch

  • Whether developers coming off the early-access waitlist publish calibration curves measured on their own labelled data.
  • Whether TypeSafe releases workflow evaluations scored against ground-truth labels instead of the average probabilities of GPT-6 Astra and Fable 5.1.
  • Whether the Wikiracing comparisons are rerun with the rival models' reasoning modes enabled.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories