Authentication and model issues

These issues commonly appear as 401, 403, model-not-found errors, or no eligible route.

401

Check, in order:

1. the full API key was copied,
2. the key is still enabled and valid,
3. the authentication header matches the protocol,
4. the environment variable is visible to the running process,
5. the client is not loading an old key.

403

Aikey365 keys can include model restrictions, IP allowlists, groups, and routing policies. Review these controls before creating another key.

Model not found

Call GET /v1/models again with the same key and use a model ID returned for the current account.

No eligible route

Possible causes include an unavailable group, manual routing that is too narrow, advanced constraints filtering all candidates, temporary upstream unavailability, or endpoint incompatibility.

Start with fewer constraints, confirm basic connectivity, then add policy restrictions gradually.

Quota

A key can have its own quota, while the account can also be constrained by wallet or other billing state. Review both key-level and account-level status.