Limits

Limits keep the service fair to everyone, and to the websites we check. Every authenticated answer tells you where you stand.

Docs menu

Your account

These are the starting values. A new account has the middle column until its first paid top-up. We can change them for one account, and the console shows yours.

LimitTest modeLive, newLive, paid
Pages in one check10020100
Pages waiting or running at once200201,000
Pages per day (UTC)1,000The free allowance only2,000
Monitors10None50
Pages across all monitors100None1,000
Reports per day (UTC)50None200
Keys per mode5510
Webhook endpoints5510
Requests per minute, per key6060120
Writes (POST, DELETE) per minute, per key301030

Over a limit the answer is 429 with one of rate_limited, account_daily_limit, pending_pages_limit, monitor_limit, key_limit, webhook_endpoint_limit or reports_daily_limit. A check with more pages than allowed is refused whole (too_many_pages); we never cut it short.

Fair use

  • Work time: each account gets 7,200 seconds of checking time in 24 hours. When it is used, new live checks answer daily_work_budget_reached with a Retry-After. Work already queued finishes.
  • Pages we could not check are free up to 20% of your live pages over 30 days (at least 100 pages), then cost the price on the Credits page.
  • An account under 30 days old can spend at most 250,000 credits and make 20 reports in 24 hours (new_account_spend_limit).
  • The US$500 and larger top-up packs unlock after 30 days and one top-up with no refund or dispute.

Other limits

  • The console accepts 30 form posts a minute per account. Past that the console asks you to wait.
  • Free live pages are capped across all accounts together: 500 a day (UTC) at most. When the cap is reached the answer is free_allowance_paused until the next day; a check paid from your balance is not affected.
  • An account under 30 days old can top up once a day and at most US$100 in total (new_account_topup_limit).
  • Each webhook endpoint accepts 10 test events an hour (test_event_limit).

Headers

HeaderMeaning
RateLimit-LimitRequests allowed in the current one-minute window.
RateLimit-RemainingRequests left in it.
RateLimit-ResetSeconds until the window ends.
Retry-AfterOn a 429: seconds to wait.
Request-IdOn every answer. Quote it when you write to us.
Idempotent-Replayedtrue when the answer is a replay. See Idempotency.

Wrong keys are limited too: after 30 failures in a minute from one place, further failures answer rate_limited.

Sizes

  • A request body is at most 256 KB; more answers body_too_large.
  • A page address is at most 2,048 characters, with no user name or password.
  • text is at most 50,000 characters and at least 40 words.
  • metadata holds up to 20 keys; a key is up to 40 characters and a value up to 500.

How we fetch a page

  • One fetch per page you send, plus the site’s robots.txt, and at most 5 redirects, each checked again.
  • We do not browse around the site, read its home page or its sitemaps.
  • We obey robots.txt and have no override. A blocked page is reported as could not be checked.
  • We wait at least 2 seconds between requests to one website, longer if it asks.
  • We send no cookies, no credentials and none of your headers.
  • A website owner can ask us to stop checking it. Those pages come back in rejected as host_opted_out.
  • One website can be checked only so many times a day by one account, and only so many times by everyone together (target_host_limit).
  • We do not check personal social-media pages or profiles.

The reuse window

If the same account checked the same page in the last 15 minutes, we may return that result instead of fetching again. It is marked reused: true, keeps its original fetched_at and is not charged twice.