Troubleshooting errors and incorrect decisions
Identify whether the problem is access, protocol, judgment or execution.
Diagnose HTTP errors by layer
| Symptom | Check first | Avoid |
|---|---|---|
| 401 | Key validity, provider identity, Bearer header | Posting a secret to a public chat |
| 422 | JSON, required fields, question type, criteria | Changing models without reading the error |
| 429 | Account limits, concurrency, bounded backoff | Unlimited parallel retries |
| 529 / overload | Service status, limited retries, review fallback | Assuming an action succeeded |
| Timeout / network failure | Network path, provider reachability, timeout | Universal regional-availability claims |
Follow your provider's actual errors; gateways may wrap or replace upstream formats.
Why there is no prose reply
That is expected: Jev's main interface returns constrained decisions. Use templates, a person or a separate generative model when you need text. Do not copy a chat completion response parser.
Missing confidence or fractional scores
Noul has no separate confidence. Score can be a weighted value on the defined rubric rather than an integer level. Parse by question type. Multiplying a score by 100 does not produce accuracy.
Valid JSON but a wrong answer
Inspect missing evidence, overlapping options, fallback choices, implicit requirements and known weak tasks. Reproduce failures with recorded versions. Schema validation cannot repair semantic errors.
Why not call directly from a public page
Do not put a long-lived key into HTML to work around CORS. Use your own authenticated backend for secrets, rate limits and logging. This static guide has no inference proxy and never asks visitors to submit an API key.
What to include in a support request
Provide a redacted request, response status/body, model version, SDK version and reproduction steps. Remove keys, customer identities, internal links and confidential records.
Sources and verification boundary
Reviewed September 19, 2026. Documentation-based guidance, not a live API or business-performance test.
TypeSafe · HTTP API →TypeSafe · Models, pricing and limits →TypeSafe · Confidence →TypeSafe · Jev 1.13 limitations →TypeSafe · Quick start →