Rate Limits

​

Usage Monitoring

• Current period usage - Requests consumed in the current billing cycle
• Remaining quota - Requests available before the next reset
• Historical usage - Usage trends over time

​

Handling Rate Limits

​

Recommended Strategy

1. Check response headers - every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (Unix timestamp); on a 429, honor the Retry-After header before retrying
2. Implement exponential backoff - Start with a 1-second delay, doubling on each retry
3. Add jitter - Randomize retry delays to avoid thundering herd problems
4. Set a max retry count - Cap retries at 3–5 attempts

async function fetchWithRetry(url, options, maxRetries = 3) {
  for (let attempt = 0; attempt < maxRetries; attempt++) {
    const response = await fetch(url, options);

    if (response.status === 429) {
      const delay = Math.pow(2, attempt) * 1000 + Math.random() * 1000;
      await new Promise((resolve) => setTimeout(resolve, delay));
      continue;
    }

    return response;
  }
  throw new Error("Max retries exceeded");
}

​

Need higher limits?

• Higher rate limits and quotas tailored to your volume
• Dedicated support with <4-hour response times
• Custom SLAs for uptime and latency guarantees
• Priority access to new endpoints and features
• Bulk pricing for high-volume screening workflows