Credits and limits
See plan prices, what uses a credit, and the request limits.
Your account has one monthly credit balance. API requests, dashboard checks, and bulk jobs all draw from it.
Plans
| Plan | Monthly price | Credits per month | Requests |
|---|---|---|---|
| Free | Free | 250 | 10 per 10s |
| Pro 25,000 | $12 | 25,000 | 500 per 10s |
| Pro 200,000 | $49 | 200,000 | 500 per 10s |
| Pro 500,000 | $99 | 500,000 | 500 per 10s |
| Pro 1,500,000 | $299 | 1,500,000 | 500 per 10s |
Prices are per month. Every plan uses the same endpoint and returns the same signals; a bigger plan raises the credit balance and the request limit.
What uses a credit
- One completed check uses one credit, whatever the result.
- Invalid input uses nothing.
- A check SignupScore could not complete uses nothing.
- Extra API keys add no credits. Keys are labels, not capacity.
For example, 150 API checks plus a bulk job of 100 unique addresses spends all 250 Free credits.
Monthly reset
- Credits reset at the start of each month, UTC.
- Unused credits do not roll over.
- Your next reset date is on the Billing page, and in the
X-Quota-Resetheader once you run out.
Request limits
Requests are counted in fixed 10-second windows, so short bursts are fine. Spend the whole allowance at once, then wait for the window to roll over.
- Free: 10 requests per 10 seconds.
- Pro: 500 requests per 10 seconds, on every Pro plan.
Go over and you get a 429 with Retry-After telling you how long to wait.
Response headers
| Header | When returned | Meaning |
|---|---|---|
X-Request-ID | Every response | Trace ID for this request. |
X-Quota-Remaining | Accepted authenticated request | Credits left after the request. |
X-Quota-Reset | Out of monthly credits (429) | When monthly credits come back. |
Retry-After | Too many requests (429) | Minimum seconds to wait before retrying. |