Changelog · September 20, 2026
Parallel requests per plan
A crawl of 5,000 pages costs the same credits however fast it runs; the higher plans finish it sooner.
By Roger Campos · Last updated: September 2026
TL;DR
Plans now sell speed as well as volume: Free runs 1 request at a time, Starter 3, Pro 8 and Scale 20. The limit rides on every response as X-Concurrency-Limit, a /scrape counts as one request, and a cache hit takes no slot at all.
Free plan, no credit card. 1,000 credits a month.
Credits say how much a month buys; they say nothing about how fast you get through it. X-Concurrency-Limit on every response tells a worker pool how wide to be, so it can size itself from the plan instead of discovering the limit by being turned away.
Over the limit, a request is refused with concurrency_limit — distinct from quota_exceeded and rate_limited, because the fix is different: it clears when one of your own requests finishes. There is no Retry-After, because there is no honest number to put in it. Nothing is spent on a refusal.
Waiting on a slow site that we are pacing does not hold one of your slots.
Endpoints
The endpoints on this page
- Run a Lighthouse audit on any URL
Paste a link and get a real Google Lighthouse audit — performance, accessibility, best practices and SEO scores, plus Core Web Vitals — measured against the live page.
Try it free - Check any website for JavaScript errors
Paste a link and see the console errors, warnings and uncaught exceptions logged while the page loads in a real browser — no DevTools, no local setup.
Try it free
FAQ
Frequently asked questions
No. A scrape is one request however many operations it runs, because they come from one page visit.
No. A cache hit does no work, so it takes no slot.
Read the X-Concurrency-Limit header, which is on every response.
Try it on the free plan.
Free plan, no card. Confirm your email and your API key is live — you'll be making real requests in minutes.