Request Costs
Every successful request to the ScrapeOps Proxy API Aggregator 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 | 25 | Request using residential proxy pools & Javascript rendering enabled |
mobile=true | 25 | Request using mobile proxy pools |
mobile=true&render_js=true | 50 | Request using mobile proxy pools & Javascript rendering enabled |
Premium Proxy Usage
For more details on premium proxies, see the Premium Proxies documentation.
| Parameter | API Credit Cost | Description |
|---|---|---|
premium=level_1 | 1.5 | Request using premium datacenter proxy pools (level 1). On large plans the credit multiple will be increased to maintain a flat rate of $0.1 per thousand requests. |
premium=level_2 | 3 | Request using premium datacenter proxy pools (level 2). On large plans the credit multiple will be increased to maintain a flat rate of $0.175 per thousand requests. |
premium=level_1&render_js=true | 15 | Request using premium datacenter proxy pools (level 1) with Javascript rendering enabled. On large plans the credit multiple will be increased to maintain a flat rate of $1 per thousand requests. |
premium=level_2&render_js=true | 30 | Request using premium datacenter proxy pools (level 2) with Javascript rendering enabled. On large plans the credit multiple will be increased to maintain a flat rate of $1.75 per thousand requests. |
Using our anti-bot bypassing functionality also consumes more than 1 API credit per request:
| Bypass | API Credits | Description |
|---|---|---|
generic_level_1 | 10 | The generic level 1 anti-bot bypass is designed to bypass simple anti-bots. |
generic_level_2 | 35 | Generic anti-bot bypass that is designed to bypass most anti-bots. On large plans the credit multiple will be increased to maintain a flat rate of $3.50 per thousand requests. |
generic_level_3 | 50 | Generic anti-bot bypass that is designed to bypass the most complex anti-bot systems. On large plans the credit multiple will be increased to maintain a flat rate of $6.50 per thousand requests. |
generic_level_4 | 85 | Generic anti-bot bypass that is designed to bypass the most extreme anti-bot systems. On large plans the credit multiple will be increased to maintain a flat rate of $8 per thousand requests. |
cloudflare_level_1 | 10 | Use to bypass Cloudflare protected sites with low security settings enabled. |
cloudflare_level_2 | 35 | Use to bypass Cloudflare protected sites with medium security settings enabled. On large plans the credit multiple will be increased to maintain a flat rate of $3.50 per thousand requests. |
cloudflare_level_3 | 50 | Use to bypass Cloudflare protected sites with high security settings enabled. On large plans the credit multiple will be increased to maintain a flat rate of $6.50 per thousand requests. |
incapsula | 35 | Use to bypass Incapsula protected sites. On large plans the credit multiple will be increased to maintain a flat rate of $3.50 per thousand requests. |
perimeterx | 35 | Use to bypass PerimeterX protected sites. On large plans the credit multiple will be increased to maintain a flat rate of $3.50 per thousand requests. |
datadome | 50 | Use to bypass DataDome protected sites. On large plans the credit multiple will be increased to maintain a flat rate of $6.50 per thousand requests. |
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) |
| 10 | Google.com (and other Google sub domains, google.co.uk, etc.). If render_js=true then the cost is 25 credits. |
| 25 | Google.com (and other Google sub domains, google.co.uk, etc.) when used with Auto-Extract functionality. Shopee Domains. Mouser Domains |
| 35 | G2.com, Leboncoin.fr - On large plans the credit multiple will be increased to maintain a flat rate of $4.50 per thousand requests. |
| 70 | LinkedIn - On large plans the credit multiple will be increased to maintain a flat rate of $7 per thousand requests. |