Scraping API PricesWhat is a credit multiplier?
A credit multiplier is the vendor-defined ratio between a basic request and a higher-cost mode: a 10x JavaScript multiplier turns 100,000 requests into 1,000,000 billable credits instead of 100,000. As of July 26, 2026, sources: https://scrapeops.io/docs/web-scraping-proxy-api-aggregator/account/request-costs/, https://scrape.do/documentation/request-costs/, and https://www.zenrows.com/pricing (retrieved July 26, 2026).
Dated price checked 2026-07-26; cited vendor pages are listed below. This is not a live price check.MethodHow multipliers change the bill
The basic formula is request count multiplied by the applicable credits per request. ScrapeOps assigns one credit to a normal request and 10 credits to a request with standard JavaScript rendering, so 100,000 normal requests consume 100,000 credits while 100,000 rendered requests consume 1,000,000. Its limited-provider cheap JavaScript mode costs five credits per request. Source: https://scrapeops.io/docs/web-scraping-proxy-api-aggregator/account/request-costs/ (retrieved July 26, 2026).
A multiplier can represent a replacement cost for the whole request, not an extra charge added to the basic credit. Scrape.do lists one credit for a normal datacenter request and five credits for a datacenter request with browser rendering. It lists 10 credits for residential routing and 25 for residential routing with browser rendering. Those published totals should be used directly rather than adding every visible feature label together. Source: https://scrape.do/documentation/request-costs/ (retrieved July 26, 2026).
Some vendors express the same relationship through plan capacity. ZenRows lists 250,000 basic requests or 50,000 JavaScript-rendered requests on its Developer plan. Dividing the basic allowance by the rendered allowance gives a 5x capacity ratio for that plan. The ratio describes consumption within that offer; it does not establish a universal cost for JavaScript rendering across vendors. Source: https://www.zenrows.com/pricing (retrieved July 26, 2026).
Other schedules contain additive charges. ScrapeOps lists its LLM extraction option as an additional 25 credits on top of the request’s other cost. It also publishes target-specific totals, including 10 credits for Google and 70 for LinkedIn, showing that destination and feature choice can override a generic baseline. Source: https://scrapeops.io/docs/web-scraping-proxy-api-aggregator/account/request-costs/ (retrieved July 26, 2026).
Not every usage unit is a request multiplier. Browserless consumes one unit for every started 30 seconds of browser time, then adds proxy units by transferred megabyte and CAPTCHA units by attempt. That is a resource schedule, so converting it into a request multiplier would require the actual duration, bandwidth, and attempts for the workload. Source: https://docs.browserless.io/overview/unit-consumption (retrieved July 26, 2026).
Before forecasting, identify whether the published number is a total, an addition, a target-specific rule, or a time-and-bandwidth unit. Where available, compare the forecast with the vendor’s response cost header: Scrape.do documents Scrape.do-Request-Cost, and ScrapingAnt documents Ant-credits-cost. Sources: https://scrape.do/documentation/request-costs/ and https://docs.scrapingant.com/credits-cost (retrieved July 26, 2026).