Scraping API cost calculator
Last checked: 2026-11-06
Enter a plan and how many credits your request uses to see what 1,000 successful requests really cost. A plan's headline credit price only holds for the cheapest request type. Rendering or premium options can multiply it. Take plan numbers from our price database.
How this works
If failed requests are billed, we divide credits per request by the success rate. We then divide the plan credits by that figure to get the successful requests the plan covers. Cost per 1,000 is the plan price divided by that number, times 1,000.
With the example numbers, 10 credits at 90% means 11.11 credits per success. A plan of 1,000,000 credits then covers 90,000 successes. At 149, that is 1.66 per 1,000. The plan's headline price is 0.15 per 1,000 credits, so the real figure is about 11 times higher.
If you need only 50,000 successes, you still pay 149, so your cost at that volume is 2.98 per 1,000.
Are failed requests billed?
- ScraperAPI says it charges only for successful requests, meaning 200 and 404 codes, plus requests you cancel before it has had 70 seconds to finish.
- ScrapingBee describes its credit costs per successful request.
- Zyte prices per successful response, and Bright Data says you pay only for successful Web Unlocker requests. Those two do not use credits, so they do not fit this tool. See our database.
If your provider bills only successes, choose No. Your real cost then depends on credits per request, and the success rate changes only how many attempts you make. Read scraping API credits explained for the credit tables.
Lawful use depends on the place, the data and the site's terms. This is not legal advice. We have not tested these services. For per-GB proxy plans, use the proxy cost calculator.