TroubleshootingTroubleshooting
401, 403, 404: key, access, and model name
The three most common setup mistakes.
By the end: You can fix a rejected request without contacting support.
Almost every failed first request is one of these three.
401 — the key
- The header is missing
Bearer. - The key was revoked, or belongs to a deleted account.
- A surrounding quote or newline was copied along with the key.
403 — the account
A valid key on a suspended account returns 403. Check the account status, not the key.
404 — the URL or the model
/v1appears twice in the final path.- The model name differs in case or version from the catalog —
gpt-6.1-solis notGPT-6.1-Sol. - The model exists but is disabled for this deployment.
Confirm the endpoint is right
curl -i https://www.ary4n73.com/v1/models \
-H "Authorization: Bearer $ROUTEFORGE_API_KEY"If this succeeds, the key and base URL are correct and the problem is the model name or route.