Errors
Documented HTTP failures and application-level failure classes you handle in code.
Documented HTTP failures and application-level failure classes you handle in code.
Prevent repeated Jev processing with your own idempotency — the public evaluation API does not document idempotency keys.
Symptom-to-fix tree for 422 and malformed Jev bodies. Channel 400s belong here as callouts, not a cloned error IA.
Handle Jev answers below a confidence threshold. This is a policy outcome, not a documented HTTP error.
Diagnose incomplete Jev decision context: missing state fields that make answers untrustworthy. Unofficial notes.
Understand blocked Jev decisions: your policy engine acting on typed answers, not a hidden TypeSafe block status.
Respond to Jev 429 rate limits and 529 overload with backoff. Published defaults live on the models page.
Handle unavailable evidence retrieval before Jev scores a passage. Unofficial notes on a common RAG failure class.
When questions do not match the door’s schema: type names, criteria shapes, boolean vs noul, jev-1.13 vs jev-1.13.0.
Handle Jev calls that exceed a client time limit. Official docs emphasize SDK timeouts and retries, not a dedicated timeout status.
401 missing/invalid key vs 403 must-supply-key and stale Vercel OIDC. Symptom-to-fix; no keys from jev.pro.