Troubleshooting
Common errors, explained plainly.
These notes help you separate something you can fix in the dashboard from a temporary service issue that usually resolves with a retry.
You can fix
Missing headers, expired keys, unverified emails, or the wrong model name are all user-side fixes.
Retry later
Rate limits, capacity limits, and temporary upstream interruptions usually clear after a short pause.
Contact support
If an error keeps returning after you have checked your key and request body, use the support link in the dashboard.
Error table
| Code | Meaning | What to do |
|---|---|---|
| 401 | Missing or invalid key | Check the Authorization header and confirm the Genesis API Key is active. |
| 403 | Model not allowed or email verification required | Verify your email and confirm the model is allowed on your key. |
| 404 | Unknown model | Use Anzoth-Core or Anzoth-Coder unless your account has another model enabled. |
| 429 | Rate limited | Wait briefly, lower your request rate, or reduce output size. |
| 500/502 | Temporary service issue | Retry after a short pause. If it persists, it is likely an Anzoth-side issue. |
| 503 | Capacity unavailable | Retry with backoff. If it continues, check status and try again later. |
Next