Rate Limits

The API uses a token-bucket rate limiter scoped to each API key. Bursts are allowed within reason.

• ›
  Per API key — 300 requests per minute, burst up to 60.
• ›
  Per IP address — 60 requests per minute (web UI only, not the API).
• ›
  Concurrent solves — 20 in-flight per account by default. Contact sales for higher.

429 Response

When you exceed the limit, the API returns HTTP 429 with a Retry-After header indicating seconds until retry:

HTTP/1.1 429 Too Many Requests
Retry-After: 12
Content-Type: application/json

{"success":false,"error":"rate limit exceeded"}

Best practices

• › Always respect Retry-After headers
• › Implement exponential backoff on 429 responses
• › Distribute load — do not burst all concurrent solves at once
• › Cache returned cookies for their full TTL (5-15 min)