Errors and troubleshooting
Capture the symptom
Section titled “Capture the symptom”Record the time, client version, endpoint, model ID, HTTP status and error message. Do not share full keys or configurations containing passwords.
Missing key: 401 / API_KEY_REQUIRED
Section titled “Missing key: 401 / API_KEY_REQUIRED”Public probes on 2026-09-10 confirmed that unauthenticated requests to /v1/models and POST requests to /v1/responses or /v1/chat/completions return 401 with API_KEY_REQUIRED.
Check that raw HTTP requests send Authorization: Bearer YOUR_API_KEY. When a client has a separate API Key field, enter only the key.
Model or path errors
Section titled “Model or path errors”Check the base URL, https://api.aoxtoken.com/v1, and whether the client duplicates a path segment. Query and test model permissions with the same key used by the client.
A 429 can have multiple causes
Section titled “A 429 can have multiple causes”Rate, concurrency and quota failures can have different causes. Read the error code and message before checking the relevant settings. Do not interpret every 429 as insufficient balance.
Contact support
Section titled “Contact support”Submit redacted details through the contact page. Other error scenarios require reproduction before being added here; this guide does not invent a status-code mapping.