Documentation
Documentation menu

Errors and troubleshooting

Check the URL, key, model and restrictions without exposing secrets.

On this page

Request and access

Read the HTTP status alongside safe error text: a code alone does not explain every cause. A 400 often concerns the body or an unsupported parameter. For 401, check key transmission and validity. Funds or restriction errors, including 402/403, call for checking credits, limits, expiry and model access. For 404, check the complete path and exact Model ID. These are diagnostic pointers, not an exhaustive status-code contract.

Retries and temporary unavailability

For 429, reduce concurrency and respect a waiting-time instruction if one is provided. For 503 or a network failure, retry later with bounded attempts and increasing delays; do not run endless retries. If a response was lost, the previous request may have executed. Check retained usage records, but do not treat a missing record as a guarantee of no charge.

What to include in a report

Record the time with its time zone, Model ID, protocol, HTTP status and a short description. Include the request ID if the response provides one. Reproduce with neutral text. Remove secrets and personal data before sharing diagnostics; do not send the complete client configuration.