Errors and retries
Troubleshoot authentication, balance, model access and rate-limit errors without exposing secrets.
Read both the status and the error body
Keep the error code, request ID if supplied, timestamp and model. Do not include secrets or client content in a support request. The exact gateway error mapping will be documented after launch verification.
Common error categories
| Response | What to check |
|---|---|
| 400 · Invalid request | JSON syntax, required fields, model alias and supported parameters. |
| 401 / 403 · Access denied | Key validity, expiry, account state, model allow-list and available quota. Inspect the error body. |
| 404 · Not found | Correct endpoint path and model name; avoid adding /v1 twice. |
| 429 · Rate limited | Reduce requests across all keys for that user. Honour Retry-After when supplied. |
| 5xx · Service error | Check status, use bounded backoff and contact support if errors persist. |
Retry deliberately
Use exponential backoff with jitter and a small retry limit for transient failures. Do not retry invalid credentials or malformed requests unchanged. A timed-out or interrupted request may already have generated billable output; retrying can incur a second charge.
Contact support
Send diagnostic metadata to support@redline.example. The address is a placeholder in this preview and must be replaced before launch.