Symptom and fix
| Symptom | Likely cause | Fix |
|---|---|---|
401 with invalid_auth | Key missing, wrong, or not sent as Authorization: Bearer <key> | Re-copy the key from where you stored it; check for a missing Bearer or a trailing newline |
404 with an HTML page | Wrong path: missing /v1, doubled /v1/v1, a trailing slash, or an endpoint luv13 doesn't serve | Use https://api.luv13.ai/v1 as the base URL; see Endpoints |
405 with an HTML page | GET sent to /v1/chat/completions | Use POST |
522 | luv13's servers unreachable behind Cloudflare | Wait and retry; see Health Checks |
| Error naming a model as unavailable | That model is out of capacity | Switch ids; see Model Fallback |
| Requests slow or failing under load | Capacity saturated; requests queue or fail | Retry with backoff; see Retrying Requests |
| CORS error in the browser console | luv13 rejects cross-origin browser calls | Call luv13 from your server; see Browser Requests |
| JSON parse error in your code | The error body was HTML (404 or 405) | Check the status code before parsing |
| Tool feature fails, chat works | The feature uses an endpoint luv13 doesn't serve, such as embeddings | Turn that feature off, or use another service for it |
Base URL mistakes
Many tools add /chat/completions to whatever you enter. Enter the base URL, not the full endpoint:
| You enter | Tool calls | Result |
|---|---|---|
https://api.luv13.ai/v1 | https://api.luv13.ai/v1/chat/completions | Works |
https://api.luv13.ai | https://api.luv13.ai/chat/completions | 404 |
https://api.luv13.ai/v1/chat/completions | .../v1/chat/completions/chat/completions | 404 |
Still stuck
Email [email protected] with the time, endpoint, model id, status code and error body. See Contact and Support.
