Errors· Last updated 2026-09-21

Jev invalid input errors

Symptom: the HTTP call never returns answers. You see 422 Unprocessable Entity (TypeSafe’s documented validation failure) or a gateway 400-class “invalid request.”

Jev did not “decide wrong.” The body failed the door’s schema. This unofficial tree is for operators. Canonical table: docs.typesafe.ai/api (401 / 422 / 429 / 529). We do not sell keys.

Decision tree

Did you get JSON answers?
  ├─ yes → not this page. Look at confidence / Noul, not HTTP.
  └─ no
       ├─ 401 → unauthorized page
       ├─ 429 / 529 → back off (SDK default)
       ├─ 402 / customer_verification → marketplace callout below
       └─ 422 or 400
            ├─ missing model, state, or questions → add required fields
            ├─ unknown / door-wrong model string → see version gotcha
            ├─ Choice >255 options or Score not 2–10 → shrink criteria
            ├─ type not noul|choice|score (or boolean on the wrong door) → fix type
            └─ criteria vs instructions inverted → 422 or silent bad answers

Read the JSON body. TypeSafe says 422 names the offending field. Do not retry 422 in a loop.

First-party fixes

Body smell	Fix
No `model`	`jev-latest` or pin `jev-1.13.0`
Empty `questions`	At least one typed question
`type: "boolean"` on `api.typesafe.ai`	Use `noul`
`jev-1.13` rejected	Try `jev-1.13.0` or an alias on this host
Image in `state`	Not accepted — transcribe first
Huge distractor JSON	Filter; unused tokens still bill and `jev-1.13` loses accuracy

Application-level “invalid input” (low confidence, policy miss) is your enum, not an HTTP code.

Channel callouts (not a cloned error tree)

OpenRouter 402 — insufficient credits on their ledger. Top up there. Not a TypeSafe 422.
Vercel “customer verification required” — account/KYC on Vercel, not a Jev criterion bug.
Gateway 400 with modelType / evaluation errors — you hit a chat compatibility path or the wrong model id (typesafe-ai/jev). See serverless channel.

FAQ

Is 400 documented by TypeSafe? The API reference we cite lists 401, 422, 429, 529. Treat other codes as door-specific.

Can invalid criteria return 200 with a confident wrong choice? Yes. Validation is structural. Alignment is on you (jaggedness).

Hub: Errors. Siblings: schema mismatch, error envelope.

Sources

Public TypeSafe or adjacent documentation only. No private claims.