Status
The moving parts behind verified output, and where to check each one is alive.
| Component | What it is | Check |
|---|---|---|
| Verified API | POST /v1/verified, /v1/verified/eval, /v1/verified/extract | api.maxmodel.com |
| Gateway | Routes the EXTRACT model call to the provider you named | maxmodel.com |
| Model list | The models verified output can call | models/list.json |
| TypeScript SDK | maxmodel | npm ↗ |
| Python SDK | maxmodel | PyPI ↗ |
Is my call failing — me or the service?
A quick triage:
401— bad or missing key. Verified output uses your normal maxmodel.com gateway token (Authorization: Bearer <key>).400 sources_too_large/too_many_cases— you’re over a documented limit, not an outage.5xx/ timeouts — most often the underlying model the gateway routed to, not the verification layer. Retry, or try a faster model (see Models); aresponses-endpoint model likegpt-5.5-procan legitimately take 10–20s before it’s “failing.”- See Errors for the full HTTP + typed-error reference.
The verification step itself is deterministic local code — when something is slow or flaky, it’s almost always the model call in front of it, not the check.