Request Costs
Every successful request to the ScrapeOps Proxy API that returns a successful status code 200 or 404 consumes API credits from your monthly API credit quota.
Each subscription plan contains a particular amount of API credits that can be used during the subscription period. Unused API credits are not transferable to the next subscription period.
The number of API credits consumed depends on the functionality enabled and the domain being scraped.
Functionality Costs
The following is a list of the number of API credits used with different functionality enabled:
| Parameter | API Credit Cost | Description |
|---|---|---|
| - | 1 | Successful response |
render_js=true | 10 | Request with Javascript rendering enabled |
residential=true | 10 | Request using residential proxy pools |
residential=true&render_js=true | 50 | Request using residential proxy pools & Javascript rendering enabled |
Domain Costs
Certain domains are much harder and costlier to scrape than your normal website, as you have to use higher quality proxies and more advanced anti-bot bypassing techniques. As a result, certain domains consume more API credits than other domains.
The following is a list of the number of API credits consumed for each domain:
| API Credit Cost | Description |
|---|---|
| 1 | Normal website (not on list) |
| 1.25 | Amazon.com (and other Amazon sub domains, amazon.co.uk, etc.) |
| 1.25 | Walmart.com |
| 5 | Google.com (and other Google sub domains, google.co.uk, etc.) |