ScraperAPI review

ScraperAPI is a web scraping API and collection toolkit for gathering public website data without running your own proxy rotation, browser handling, or CAPTCHA workflows. The core API handles those parts of a request; other options include structured-data endpoints, asynchronous scraping, and no-code automation through DataPipeline.

Structured endpoints return JSON for supported popular sites, including Amazon, Google, and Walmart. The SERP tool collects search results such as rankings, ads, shopping results, and news. ScraperAPI also lists a pool of more than 40 million proxies across over 50 countries for geotargeting, and says its async scraper can send millions of requests asynchronously.

There is a free account with 1,000 API credits and up to five concurrent connections, plus a seven-day free trial. Paid plans start at $49 per month, or $44.10 per month with annual billing, according to the pricing details checked November 6, 2026.

The appeal is breadth: ScraperAPI combines a general scraping API with structured endpoints, SERP data, async requests, and no-code collection automation. That gives teams several ways to collect data without separately managing proxy rotation, browser handling, and CAPTCHA handling, according to the published product details.

The plan ladder also makes the published starting capacity easy to compare. Hobby costs $49 monthly ($44.10 monthly equivalent with annual billing) for 100,000 API credits and 20 concurrent threads. Startup is $149 monthly ($134.10 annually) for 1 million credits and 50 threads. Both include US and EU geotargeting. Business is $299 monthly ($269.10 annually), with 3 million credits, 100 threads, and global geotargeting.

For a small project, the free account provides 1,000 credits and five concurrent connections. Larger plans list up to 21.5 million credits and 500 threads on Advanced, at $1,975 monthly or $1,777.50 with annual billing. Enterprise is available for custom volume and control needs. One Reddit discussion also frames provider choice as domain-dependent rather than a simple cheapest-price contest—a useful caution for teams scraping multiple retailers.

The headline plan price does not tell you what a successful scrape will cost across your target sites. ScraperAPI sells API credits, but the published pricing details do not publish a per-credit rate for pay-as-you-go. That option is listed only for Scaling, Professional, Advanced, and Enterprise. The cost per landed record by domain is also not published, so a mixed retailer workload needs more than a plan-price comparison.

Credit exhaustion can change the bill or interrupt work. Auto-upgrade is available on Hobby, Startup, Business, Scaling, and Professional; the account moves to the next plan when credits run out. Concurrency overages do not incur an extra charge, but excess requests are rejected with a 429 response. That is a hard operational limit, not extra capacity.

Business starts at $299 monthly for 3 million credits; Scaling is $475 for 5 million, and Professional is $975 for 10.5 million. Enterprise pricing is not published. Reddit commenters warn that credit use can vary by domain and that a successful HTTP response may still fail to provide the needed product fields. Treat those as user reports, not verified ScraperAPI performance results, and validate parsed records before committing to a volume plan.

ScraperAPI has a free account with 1,000 API credits and up to five concurrent connections. Paid plans start at $49 monthly for Hobby, or $44.10 per month equivalent with annual billing. That buys 100,000 credits and 20 concurrent threads. Startup is $149 monthly for 1 million credits; Business is $299 for 3 million. The jump from Business to Scaling is $176 monthly, for 2 million more credits and 100 more concurrent threads.

Scaling costs $475 monthly, Professional $975, and Advanced $1,975. Annual billing cuts listed prices by 10%, but charges annually. Enterprise pricing is not published. A seven-day free trial is listed.

Pay-as-you-go is available from Scaling upward, but its per-credit rate is not published. Auto-upgrade can move eligible accounts to the next plan when credits run out. Concurrency overages do not cost extra, but excess requests are rejected with a 429 response. Budget around that failure mode, not just the headline credit allowance.

Migration effort depends on whether you use ScraperAPI’s API, structured endpoints, asynchronous requests, or DataPipeline. The product offers both API access and no-code collection, but the published material does not document migration tooling, export formats, or how easily existing jobs transfer. Check those details before moving scheduled workflows; test that the replacement returns the fields and volume your downstream systems expect.

The pricing material flags two issues worth weighing before committing: pay-as-you-go rates are not published, and requests above the concurrency limit are rejected with a 429 response. Those can matter when costs or uninterrupted collection are priorities. But we were not given Reddit posts or comments for this review, so we can’t attribute common reasons for leaving to Reddit users. Data portability and account offboarding details are also not published on the vendor's site. Get answers on exports and job configuration before you make ScraperAPI a dependency.