Errors· Last updated 2026-09-21

Jev schema mismatch errors

Symptom: 422 (or a gateway validation error) that names a question field, or a 200 response whose type does not match what your TypeScript expects.

A schema mismatch is not a wrong department Choice. It is a body the door cannot parse, or a client that assumed OpenAPI types from the wrong host. Official validation language: docs.typesafe.ai/api. Unofficial tree below. No keys sold here.

Decision tree

Is the status 2xx?
  ├─ no, 422 → read `field` in the error body
  │     ├─ questions.ID.type → noul | choice | score on first-party
  │     ├─ questions.ID.criteria → map vs array vs true/false glosses
  │     ├─ model → alias/version/door id
  │     └─ state → not an image; must be text/object/array
  └─ yes, but client throws
        ├─ expected `noul`, got `boolean` → you called Vercel evaluate
        ├─ expected `confidence` on Noul → Noul has none
        └─ expected `jev-latest` in response.model → you get jev-1.13.0

First-party vs door schemas

Copy-paste across doors is the #1 mismatch we see in support-shaped questions.

Choice criteria must be a map, Score a list, Noul optional {true,false}. Max 255 Choice options; Score 2–10 levels. Exceeding those is a validation problem, not a “low confidence” problem.

jev-1.13 vs jev-1.13.0

If the error is “unknown model,” you likely sent a family string to a host that wants a patch id (or the reverse). Matrix: decision endpoint.

FAQ

Does TypeSafe return a separate “schema mismatch” status? No. Structural failures are 422. Semantic mismatch (criteria contradict instructions) may still 200 with a confused distribution — jaggedness, not HTTP.

Max tokens exceeded? Context limits live on the models page (64k / 32k first-party). Marketplace cards may list 32k. Over-limit behavior is a size error; shrink state rather than inventing a status we did not see documented.

Hub: Errors. Siblings: invalid input, request schema.