Scraping API PricesDo scraping APIs charge for failed requests?
A failed scrape can cost 0 credits or 100% of the normal request charge: vendor-side failures are free under several success-based APIs, while some target error responses and resource usage remain fully billable. As of July 26, 2026, sources: Bright Data billing rules, Firecrawl pricing FAQ, Oxylabs pricing FAQ, and Browserless unit rules, retrieved July 26, 2026.
Dated price checked 2026-07-26; cited vendor pages are listed below. This is not a live price check.MethodThe two HTTP layers matter
Bright Data’s regular Web Unlocker bills only successful requests, but enabling a listed Custom Web Unlocker feature changes billing to 100% of requests, successful and failed. The same vendor can therefore answer the question differently for two configurations of one product. Bright Data Web Unlocker documentation, retrieved July 26, 2026.
Firecrawl does not charge for a Firecrawl-side timeout or server error, but it charges when it fetches a page and the target returns a 4xx or 5xx response. Its scrape, crawl, map, and monitor operations cost 1 credit per page under the current schedule. Firecrawl pricing FAQ, retrieved July 26, 2026.
Oxylabs similarly treats its own 5xx and 6xx system errors as unsuccessful and free, while target responses with 2xx or 4xx status codes count as successful and billable. This is why “pay only for success” does not mean every response the buyer rejects is free. Oxylabs Web Scraper API pricing, retrieved July 26, 2026.
Other success-based products publish their own status lists. ScrapingFish bills HTTP 200 and 404 and makes other failed requests free; ScrapingBee bills HTTP 200, 404, and 410; Scrape.do bills 2xx, 400, 404, and 410. ScrapingFish FAQ, ScrapingBee FAQ, and Scrape.do request costs, retrieved July 26, 2026.
Resource-metered browsers use a different boundary. Browserless charges 1 unit for every started 30 seconds that a session remains open, including idle time, and charges 10 units for every CAPTCHA solve attempt whether it succeeds or fails. Proxy traffic adds 6 units per residential MB or 2 per datacenter MB. Browserless unit consumption, retrieved July 26, 2026.
For a forecast, classify responses by the vendor’s published billable statuses, then count client retries as new attempts unless the vendor documents otherwise. Do not insert a vendor success percentage into the calculation without a target-specific benchmark; none is asserted here. Bright Data billing rules, Firecrawl pricing FAQ, and Oxylabs pricing FAQ, retrieved July 26, 2026.