Rate limits

Rate limits control how many requests an API key can make within a time window. They protect the service and ensure fair usage across all consumers.

Default limits

Rate limits are configured per API key through the API Console. Limits use a per-second sliding window. The default limit is set when you create a key and can be adjusted based on your needs.

Contact support if you need higher rate limits than what’s available in the console.

Rate limit headers

When your API key has a rate limit configured, responses include rate limit headers:

Header	Description
`X-RateLimit-Limit`	Maximum requests allowed per second
`X-RateLimit-Remaining`	Requests remaining in the current window
`X-RateLimit-Reset`	Unix timestamp (seconds) when the window resets
`Retry-After`	Seconds to wait before retrying (only on `429` responses)

Handling 429 responses

When you exceed your rate limit, the API returns a 429 status code:

{
  "error": "Too Many Requests",
  "message": "Rate limit of N requests per second exceeded"
}

Use the rate limit headers to monitor usage and the Retry-After header to pace retries:

import time
import requests

response = requests.get(
    "https://api.andiai.com/api/v1/search",
    params={"q": "test"},
    headers={"x-api-key": "YOUR_API_KEY"}
)

# Check remaining quota on any response
remaining = int(response.headers.get("X-RateLimit-Remaining", 0))

if response.status_code == 429:
    retry_after = int(response.headers.get("Retry-After", 1))
    time.sleep(retry_after)
    # Retry the request

Monitoring usage

Use the X-RateLimit-Remaining header to track how close you are to your limit in real time. For aggregate usage and credit consumption, see the API Console.

Getting started

Search

Features

Resources

Default limits

Rate limit headers

Handling 429 responses

Monitoring usage

Next steps

Error handling

Authentication

​Default limits

​Rate limit headers

​Handling 429 responses

​Monitoring usage

​Next steps

Error handling

Authentication

Default limits

Rate limit headers

Handling 429 responses

Monitoring usage

Next steps