Limits and usage
Limits count per account, across all your keys and connected apps.
| Paid plan | Free plan | Beta | |
|---|---|---|---|
| Records per day | Your plan’s volume, e.g. 1,000 (resets 00:00 UTC) | 100 (resets 00:00 UTC) | No cap |
| Requests per day | 500 | 200 | 200 (resets 00:00 UTC) |
| Requests per month | No cap | 2,000 | 2,000 (resets on the 1st, UTC) |
| People per request | up to 100 | up to 100 | up to 100 |
A record is one person returned by a search or a batch lookup. Counting is free of records. When fewer records are left today than a search asks for, it returns what is left with a note; once none are left you get 429 limit_reached until 00:00 UTC. Results carry records_left_today. More records a day: change your plan on the pricing page or in Billing.
What counts#
| Counts as 1 request | Free |
|---|---|
| Search, count and batch lookups (REST and MCP) Calls made from the playground | GET /v1/metaGET /v1/usageGET /v1/openapi.jsonMCP describe_catalog |
A search that returns 100 people costs the same as one that returns 1. A request that fails validation still counts.
Rate-limit headers#
Every metered REST response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (unix seconds). When a limit is hit you get 429 limit_reached with a Retry-After header.
See your usage#
The dashboard shows today, this month and 30 days of history. In code: GET /v1/usage.