The cost of scraping pages through a scraping API.
The cheapest scrape is static HTML; JS rendering can cost 5–10× more. Classify pages first and reserve rendering for the ones that truly need it. Compare providers in the search & scraping guides.
The Web Scraping API Cost Calculator estimates your monthly bill for a hosted scraping API. You enter your pages per month and the price per 1,000 requests, and the tool multiplies volume by rate to project your base cost. Because many pages require a browser to run JavaScript before content appears, the calculator also factors in the share of pages needing JS render and the JS-render premium multiplier, which raises the effective per-request price for that portion. The two biggest drivers are simply how many pages you scrape and how many of them need full rendering.
The key trade-off to watch is JS rendering: it is usually the most expensive line item, so pushing every page through it inflates your bill fast. Before assuming you need it, check whether the data is available in raw HTML or a lighter endpoint, and reserve rendering only for pages that truly require it. Small changes to your JS-render percentage often move the total more than volume alone.
Most scraping APIs bill per request (often per 1,000), with a premium for JavaScript rendering and residential proxies. Blended cost = plain requests + JS-render requests at their higher rate.
Because it spins up a real browser per request — far more compute than fetching static HTML. Detect which pages actually need rendering and only pay the premium for those.