Skip to documentation

Limits & errors

Plan, credit, concurrency and protocol limits are enforced before execution.

Updated October 31, 2026

Shared input bounds

Native text, messages and schemas share a 128 KiB serialized bound, 128 messages/items, up to eight functions/calls and 16 KiB arguments/results. The transport schema accepts bounded output values, but the selected model and operational ceiling determine the effective maximum. The current default operational output ceiling is 4,096 tokens unless explicitly raised. Messages requires an explicit maximum.

Response status

400 means invalid or unsupported input; 401 invalid credentials; 403 missing admission or scope; 402 insufficient funds/allowance; 404 unavailable resource/model; 409 conflicting operation; 429 rate/concurrency limits; 502/503 inference/service failure; 504 deadline exhaustion. The native protocol determines the error envelope.

Recovery

Keep the safe request identifier when available. Never share a provider or customer key in a support report. A timeout or network error may leave usage pending; a new independent request may cost again.