Gateway error reference
Gateway errors use an OpenAI-style error object with message, type, code and param; request_id is included when available. Upstream error bodies may differ. Keep the request ID when asking support for help.
| Code | HTTP status | What to do |
|---|---|---|
| unauthorized | 401 | Sign in again or provide valid authentication. |
| account_exists | 409 | Sign in to the existing account. |
| invalid_api_key | 401 | Check the key or create a replacement in Console. |
| missing_api_key | 401 | Send the Authorization bearer header. |
| key_revoked | 401 | Replace the revoked key. |
| scope_denied | 403 | Use a key entitled to this product. |
| insufficient_credits | 402 | Check available wallet credit and add funds. |
| rate_limited | 429 | Wait for Retry-After before retrying. |
| invalid_request | 400 | Correct the input or named parameter. |
| model_not_found | 404 | Choose an available model from the catalog. |
| not_found | 404 | Check the public ID or resource URL. |
| method_not_allowed | 405 | Use the documented HTTP method. |
| not_implemented | 501 | Choose a supported operation. |
| provider_unavailable | 503 | Check availability before trying later. |
| upstream_error | 502 | Check Usage before deciding whether to retry the call. |
| console_disabled | 503 | Console is unavailable on this deployment. |
| forbidden | 403 | Check account access and permissions. |
| internal_error | 500 | Contact support with the request ID. |
A failed billable call is not charged. For a transport timeout with an unknown outcome, check Usage or the existing run before starting another paid execution.