Symptoms

• Authentication succeeds and other models work.
• The failing model is tagged for a different access tier or group.

Likely causes

• The model requires balance, Plus access, a permitted group, or an enabled route.
• The API key has model restrictions that exclude this ID.

How to diagnose

• Check the model access badge and enabled groups in the current catalog.
• Review API key model restrictions and account status.
• Try an allowed model with the same key to isolate access from authentication.

Fixes

• Choose a model available to the current account and key.
• Update the key restriction only when broader access is intended.
• Add the required balance or plan through the documented billing flow.

How to verify

The same key succeeds on an allowed model, and the intended model succeeds only after legitimate access is granted.

Resources

• Base URL and authentication
• FAQ and troubleshooting