A newly created API key can authenticate successfully and still fail to run a model. Authentication proves which key was presented; model permissions, routing, account limits and the request format are separate checks.
Locate the failing layer first
Keep the final request URL, HTTP status, error code, message and request identifier. Avoid sharing the authorization header or an unredacted key.
| Signal | Check next |
|---|---|
| Invalid or missing key | Issuing service, authorization header, key state and expiry |
| Model not allowed | Exact identifier and key model restrictions |
| No available channel | Group access and eligible routes |
| Insufficient balance | Recorded account balance and key allowance |
| Rate limit / capacity | Request rate, retry policy and current status |
| Invalid path or parameter | Full URL, API family and payload shape |
Confirm that the key belongs to this endpoint
Check where you created the key and where your application is sending it. Review enabled state, expiry and usage limit in API keys. Being signed in to the console does not prove the key is valid.
Check balance without confusing it with permissions
A balance message points to a different layer from a permissions failure. Review Wallet and key allowance. If the response reports no eligible route, adding funds will not fix the configuration problem.