Skip to main content

Rate limiting

To ensure stability and optimal performance during the beta testing phase, especially while we monitor for potential bugs or inefficient queries, we are enforcing initial rate limits.

  • Standard limit: 100–300 API calls per minute

  • Burst allowance: Up to 600 calls per minute (short bursts allowed)

  • Burst control: Implemented to prevent sustained overuse

These limits are subject to adjustment as we gain confidence in system performance and usage patterns. We plan to gradually increase these thresholds post-beta, based on system reliability and user demand.

What Happens When You Hit the Limit​

If you exceed the rate limit:

  • You’ll receive an HTTP 429 response.

  • A Retry-After header will indicate how long to wait before retrying.

Sample 429 Response:

{
  "status": "RateLimitExceeded",
  "message": "You have exceeded the allowed rate limit of 300 requests per minute.",
  "data": null
}

Response Headers:

HTTP/1.1 429 Too Many Requests
Retry-After: 60
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 0