What does a web scraping API cost?

What those figures buy

The $19 basic figure is ScrapeOps’ 100,000-credit monthly plan, and a successful normal-site response without added functionality consumes 1 credit. ScrapeOps counts HTTP 200 and 404 as successful, so the figure covers 100,000 responses under that billing definition, not 100,000 records that pass a buyer’s acceptance test. ScrapeOps pricing and request-cost documentation, retrieved July 26, 2026.

The $90 rendered figure is ScrapingDog’s Standard monthly plan containing 1,000,000 credits. JavaScript rendering costs 5 credits per request, so 100,000 rendered requests consume 500,000 credits and fit that plan; a rotating-proxy request costs 1 credit. The plan price therefore has no meaning until the request class is fixed. ScrapingDog pricing, retrieved July 26, 2026.

Other billing shapes produce different cash totals without being directly interchangeable. Bright Data Web Unlocker charges $1.50 per 1,000 successful requests on pay as you go, includes browser rendering and CAPTCHA solving on the published offer, and therefore produces a $150 usage charge for exactly 100,000 billable successes. Bright Data Web Unlocker pricing, retrieved July 26, 2026.

ScrapingFish charges $0.002 per successful request and sells a $200 pack containing 100,000 paid requests plus 5,000 bonus requests; JavaScript rendering and its other available request features use the same request price. The pack expires after six months, and the vendor bills HTTP 200 and 404 responses while other failed requests are free. ScrapingFish pricing and request packs, retrieved July 26, 2026.

The bill changes when the target triggers a domain multiplier, a request needs premium or residential routing, rendering is enabled, extraction is added, or the plan cannot supply the required concurrency. ScrapeOps, for example, publishes 10 credits for standard JavaScript rendering, 25 for residential routing plus rendering, and an additional 25 for LLM extraction. ScrapeOps request costs, retrieved July 26, 2026.

The defensible comparison unit is the vendor-defined billable response for one stated request class, not an assumed usable record. Oxylabs bills target 2xx and 4xx responses but not its own 5xx and 6xx system errors, while Bright Data changes its normal success-based rule when Custom Web Unlocker features are enabled. Oxylabs pricing and Bright Data billing documentation, retrieved July 26, 2026.