Rate Limits & Usage

Usage is metered per organization on a monthly calendar window (UTC). Two independent controls apply: monthly quotas and short-term burst limits.

Monthly quotas

• Free — 250 leads analyzed, 50 API requests
• Developer — 5,000 leads / month (coming soon)
• Growth — 50,000 leads / month (coming soon)

Each analyzed lead counts toward the leads quota; each request counts toward the request quota. A batch of 100 leads consumes 1 request and 100 leads.

When you exceed a limit

Requests that would exceed a monthly quota return 429 and are not metered:

HTTP/1.1 429 Too Many Requests

{
  "error": {
    "code": "usage_limit_exceeded",
    "message": "Monthly lead analysis limit exceeded.",
    "request_id": "req_xxx"
  }
}

Burst limits

A per-key burst limit protects the service from spikes. Each response includes rate-limit headers:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 41
X-RateLimit-Reset: 1735689600
X-Request-Id: req_xxx

When the burst window is exceeded you will receive 429 with a rate_limit_exceeded code and a Retry-After header.

What we meter

We record only privacy-safe metadata: endpoint, lead counts, batch size, response status, and latency. We never store your raw lead payloads.