Crawlbase
A scraping API where every product draws on one credit balance, and failed requests are not charged.
Plans
| Tier | Per month | Credits | Concurrency | Per 1,000 requests |
|---|---|---|---|---|
| Starter | $99 | — | — | — |
| Scale 500K | $199 | — | — | — |
| Scale 1M | $349 | — | — | — |
| Growth | $599 | — | — | — |
Read from Crawlbase’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
- Failed requests
- Not charged
- 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.
- screenshot capture
- 2 credits
Keep comparing
- Where Crawlbase says its addresses come from they do not say, and what that means
- Cost calculator, what Crawlbase actually costs at your monthly volume