ScraperAPI
A scraping API billed in credits, where a standard page costs one credit and each plan states a concurrent-request limit.
Plans
| Tier | Per month | Credits | Concurrency |
|---|---|---|---|
| Hobby | $49 | — | — |
| Startup | $149 | — | — |
| Business | $299 | — | — |
| Scaling | $475 | — | — |
| Professional | $975 | — | — |
| Advanced | $1975 | — | — |
Read from ScraperAPI’s own pricing page. A dash means the page states a price without stating that figure beside it, not that the plan has none.
Nothing yet, we'll log every price and policy move we spot.
Whose network is underneath
Not established
A scraping API is a storefront over somebody’s proxy pool. This one does not say whose. We looked twice: through its pricing, about and FAQ pages, and then through the places a supplier has to be named for data-protection reasons — subprocessor, trust, security and privacy pages. Neither names a network. That is not the same as there being no upstream.
It matters because ethics do not stop at the vendor boundary. In July 2026 the FBI seized a residential proxy platform built on roughly two million consumer devices enrolled with little or no meaningful consent, and that network was resold under other brands. A clean storefront can sit on top of one.
- Billed in
- credits
- Concurrent requests
- 20
- JavaScript rendering
- Offered
What one unit of work costs
A credit is not a price until you know what it buys, and the same plan charges different amounts for different work.
- standard page
- 1 credit
Keep comparing
- Where ScraperAPI says its addresses come from they do not say, and what that means
- Cost calculator, what ScraperAPI actually costs at your monthly volume