ScrapingBee
A scraping API billed in credits, where a basic request costs one credit and JavaScript rendering raises what a request draws.
Plans
| Tier | Per month | Credits | Concurrency |
|---|---|---|---|
| Hobby | $19.99 | 75,000 | 25 |
| Freelance | $49.99 | 250,000 | 50 |
| Startup | $99.99 | 1,000,000 | 100 |
| Business | $249.99 | 3,000,000 | 200 |
| Business+ | $599.99 | 8,000,000 | 400 |
| Enterprise 14 | $999.99 | 14,000,000 | 500 |
| Enterprise 24 | $1599.99 | 24,000,000 | 600 |
| Enterprise 41 | $2399.99 | 41,000,000 | 700 |
| Enterprise 69 | $3599.99 | 69,000,000 | 800 |
| Enterprise 120 | $5799.99 | 120,000,000 | 900 |
Read from ScrapingBee’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
- 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.
- basic request
- 1 credit
Keep comparing
- Where ScrapingBee says its addresses come from they do not say, and what that means
- Cost calculator, what ScrapingBee actually costs at your monthly volume