Skip to main content
Limits rise with what the account has topped up in all: Free before the first top-up, then steps at $10, $100 and $500. A call over a limit answers 429 and costs nothing. GET /v1/limits returns yours, see Usage.

Limits

  • The step counts top-ups, not the balance left. A new step applies within a minute of the top-up.
  • A job is a crawl, batch, extract or agent run. A start is POST /v1/crawl, /v1/batch/scrape, /v1/extract or /v1/agent.
  • A browser start is POST /v1/browser, a browser task or an interact call.
  • The calls limit counts each endpoint on its own, so busy scrapes do not use up your search limit. The other limits are shared.
  • GET /v1/concurrency-check is free and returns concurrency (running now, counting the check) and maxConcurrency. Size your worker pool to maxConcurrency.

Without a key

Search, scrape, map and parse work with no key over HTTP and MCP. Which fields need a key is in Get credentials. GET /v1/keyless/eligibility returns eligible, remainingToday and remainingThisMinute.

Headers

X-RateLimit-Limit and X-RateLimit-Remaining show the calls in the window. X-RateLimit-Reset is the reset in Unix seconds. Without a key they describe the day’s allowance.

When you go over

Read the message as well as the code. Every case is 429. Wait as long as the answer says and add random jitter. Retry rules are in Troubleshooting.