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