Limits by plan
| Plan | Requests per minute |
|---|---|
| Free | 60 |
| Pro | 300 |
| Scale | 1,000 |
Response headers
Every API response includes rate limit headers:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests per window |
X-RateLimit-Remaining | Remaining requests in current window |
Retry-After | Seconds until reset (only on 429 responses) |
How to handle rate limits
When you exceed the limit, the API returns HTTP429 (see error codes for the full list):
Retry strategy
Best practices
Cache responses
Tech stacks don’t change every minute. Cache domain lookups for at least 24 hours.
Use batch endpoints
/v1/technologies/lookup and /v1/companies/batch let you look up multiple items in a single request.Monitor usage
Check
/v1/usage to track request counts and credit consumption.Related pages
Authentication
Set up your API key for Bearer token authentication.
Credits
Credit costs per endpoint and plan details.
Errors
Error codes including 429 rate limit responses.
Account API
Monitor usage statistics and credit balance.
Frequently asked questions
What happens when I exceed the rate limit?
What happens when I exceed the rate limit?
The API returns HTTP
429 with a Retry-After header indicating how many seconds to wait. Your request isn’t charged credits. Wait the specified time and retry. See errors for the full error response format.Are rate limits per key or per organization?
Are rate limits per key or per organization?
Rate limits are enforced per API key on a rolling 60-second window. Since each organization has a single API key, the limit applies to all requests from your organization combined.
How do I avoid hitting rate limits?
How do I avoid hitting rate limits?
Cache domain lookups for at least 24 hours (tech stacks don’t change that often). Use batch endpoints like
/v1/companies/batch and /v1/technologies/lookup to process multiple items in one request. Monitor your usage with the free /v1/usage endpoint.