Limits by credit tier
Your rate limits depend on the credits you are currently using. Free credits and top-ups below $50 come with the standard limits. A larger single purchase comes with higher limits and more credits per dollar:
Both windows apply. Staying below the per-second limit can still exceed the
per-minute limit.
Higher limits last for as long as the credits from that purchase do. Credits
with the highest limits are used first, so your limits step down to those of
your remaining credits once a purchase is used up. Buying again restores them.
GET /billing reports the limits currently in effect and how
many credits are left at those limits.
Limits are applied per platform and shared across all API keys
belonging to that account. Every LinkedIn endpoint counts toward one LinkedIn
limit, every Reddit endpoint toward one Reddit limit, and so on. Creating another
key does not increase your limit. Requests made through the SDK or MCP server
count toward the same limits as direct API calls.
Need more than the Scale limits? Contact us for a
custom agreement.
Endpoints with lower limits
Because of the high load it is under, the LinkedIn profile endpoint (POST /linkedin/get-profile-from-url) currently has a lower per-minute limit
than every other endpoint:
This limit is counted on its own, apart from your LinkedIn limit. Like your
other limits, it follows the credits you are currently using and steps down
once a purchase’s credits are used up. Going over it returns the same
429
response described below.
When a limit is exceeded
The API rejects the request with429 Too Many Requests. The scrape does not
run, and the rejected request does not consume credits.
The response includes a Retry-After header with the number of seconds to wait
before trying again. For example:
429 responses.
Response headers
The API also reports the shortest configured rate-limit window through:
The remaining count covers that window only; a longer window may still be
exhausted. See Responses & errors for the other API status codes.