Our current rate limit configuration is:

• 2 requests capacity
• Refill rate: 1 request per second

This means you can make up to 2 requests in quick succession, after which the limit refills at a rate of 1 request per second.

Rate Limit Headers

To help you manage your API usage, we include the following headers in our responses:

1. X-Rate-Limit-Remaining: Indicates the number of requests left for the current time window.

2. Retry-After: When the rate limit is exceeded, this header is included in the response. It specifies the number of seconds to wait before making another request.

Exceeding Rate Limits

If you exceed the rate limit, the API will respond with:

• HTTP Status Code: 429 Too Many Requests
• The Retry-After header will be included, indicating how long to wait before retrying.

Best Practices

• Monitor the X-Rate-Limit-Remaining header to track your remaining requests.
• If you receive a 429 response, wait for the duration specified in the Retry-After header before retrying.
• Implement exponential backoff in your client for more robust handling of rate limits.