Skip to main content
Most issues encountered while using Air API fall into one of four categories: authentication, request validation, billing, or service availability. Use the sections below to identify and resolve your issue.

​
Error Code Reference

​
Authentication Errors

Cause: The secret key is missing, invalid, or has already been deleted.Check the following:
  • Make sure the request includes the Authorization: Bearer YOUR_API_KEY header.
  • Verify that there are no leading or trailing spaces in the API key.
  • If you are loading the key from an environment variable, confirm that it is correctly configured.
  • Verify that the key is still active in the Console.
Secret keys are displayed only once when they are created and cannot be viewed again.Delete the existing key from the Console and generate a new one. We recommend copying it immediately and storing it securely as an environment variable.

​
Billing and Credit Issues

Cause: Your Organization’s credit balance has been exhausted, preventing further API requests.Resolution:
  • Add credits from the Billing page in the Console.
  • Retry your API request after the credits have been added.
  • To prevent interruptions, enable Auto Top-up.

​
Request Validation Errors

Cause: One or more request parameters are invalid or incorrectly formatted.Check the following:
  • Ensure that every item in the messages array includes both role and content.
  • Verify that numeric parameters such as temperature and max_tokens are provided as numbers, not strings.
  • Refer to the API Reference for the valid range and format of each parameter.
Cause: The value provided in the model parameter does not match a valid AirCloud model ID.Resolution:
  • In the Console, click View Code for the selected model. The generated code sample contains the correct model ID, which you can copy directly.

​
Rate Limits and Service Errors

Cause: Your application has exceeded the allowed request rate.Resolution:
  • Check the Retry-After response header and retry after the specified delay.
  • Distribute requests over time or implement exponential backoff.
Air API does not enforce a published per-account request or token rate limit today. A 429 means the model’s serving capacity is saturated at that moment, so backing off and retrying is the right response.
Cause: The model did not complete the request within the allowed timeout. This may occur with long prompts or large max_tokens values.Resolution:
  • Reduce the max_tokens value.
  • Verify that your client-side timeout is not set too low.
  • Retry the request after a short delay.
Cause: The model service is temporarily unavailable or undergoing maintenance.Resolution:
  • Retry the request after a few seconds or minutes.
  • If the issue persists, contact us through the Contact and Feedback page.
Planned maintenance and incidents are announced through console notifications. See Notifications.
Cause: Response latency may increase depending on model load, prompt length, or the configured max_tokens value.Check the following:
  • Use only the max_tokens value you actually need.
  • Test the same prompt in the Playground to compare response times.
  • If latency remains high, consider using a smaller model.

​
Playground Issues

Try the following steps:
  1. Refresh your browser and try again.
  2. Verify that the correct Project and model are selected.
  3. Confirm that your Organization has sufficient credits.
  4. Try using an incognito window or a different browser.
Playground is not supported for Embedding models. This is expected behavior.To use an Embedding model, send requests through the API. See the API Usage Guide for code examples.

​
Model Issues

We continuously add support for new models. If the model you need is not available, you can request it through the Contact and Feedback page.
Cause: Your current account or Project does not have permission to access the requested model.Resolution:
  • An API key can only reach the Air API endpoints selected when the key was created. Check the key’s Air API Access setting in the Console, or create a new key that includes the model you need.
  • Some models are enabled per organization. If the model does not appear in your Console at all, request it through the Contact and Feedback page.

​
Still Need Help?

If your issue is not resolved, please contact us through the Contact and Feedback page. To help us investigate the issue more quickly, include the following information whenever possible:
  • Error code
  • Request payload (excluding secret keys)
  • Time when the issue occurred
  • Any relevant error messages or logs