ScraperAPI review: the short version
ScraperAPI is a unlocker / scraping api from ScraperAPI, and in our 2026 assessment it scores 8.2/10 overall. It is at its best for small and mid-size teams that want one endpoint and no infrastructure, it starts at $49 / mo (100k credits), and it expects none — the unlocker is the proxy network behind it. Credit-based: a plain request costs 1 credit, rendering 10, premium residential 10–25 or more.
The rest of this review covers how it actually works, what it costs at realistic volumes, which proxy type to pair it with, how it behaves against anti-bot systems, where it breaks, and which alternatives make more sense for adjacent workloads. Every figure below reflects list pricing and hands-on testing rather than vendor marketing copy.
- +Proxy-port mode — no code change needed
- +Structured endpoints for Amazon, Google, Walmart
- +Async batch job endpoint
- +Geotargeting on paid plans
What ScraperAPI is and how it works
## ScraperAPI review: the short version
ScraperAPI is a unlocker / scraping api from ScraperAPI, and in our 2026 assessment it scores 8.2/10 overall. It is at its best for small and mid-size teams that want one endpoint and no infrastructure, it starts at $49 / mo (100k credits), and it expects none — the unlocker is the proxy network behind it. Credit-based: a plain request costs 1 credit, rendering 10, premium residential 10–25 or more.
The rest of this review covers how it actually works, what it costs at realistic volumes, which proxy type to pair it with, how it behaves against anti-bot systems, where it breaks, and which alternatives make more sense for adjacent workloads. Every figure below reflects list pricing and hands-on testing rather than vendor marketing copy.
- Proxy-port mode — no code change needed
- Structured endpoints for Amazon, Google, Walmart
- Async batch job endpoint
- Geotargeting on paid plans
## What ScraperAPI is and how it works
ScraperAPI occupies the pragmatic middle of the market: more managed than a raw proxy gateway, cheaper and simpler than an enterprise unlocker. You either call the REST endpoint with your URL, or point an existing scraper at their proxy port and change nothing else — the second option is why migrations take an afternoon rather than a sprint.
The credit model is its clearest feature. One credit per standard request, ten for JavaScript rendering, and a higher multiplier for premium residential exits or difficult domains. At $49 for 100,000 credits, a static-HTML crawl runs around $0.49 per thousand pages; the same crawl with rendering everywhere costs ten times that, which is exactly the discipline you want the pricing to enforce.
The structured endpoints are underrated. Amazon product, Google search and Walmart endpoints return parsed JSON with a schema the vendor maintains, so a price-monitoring pipeline never touches a selector. For teams whose data needs are commodity, that eliminates the most fragile code in the stack.
## ScraperAPI scorecard and measured performance
Scores below are relative to the other tools in this directory, not to software in general — a 6 for scale still means a tool that handles more traffic than most projects will ever generate. The performance figures come from crawling a mixed basket of static HTML, JavaScript-rendered commerce and lightly protected listing pages from three regions.
Read them alongside your own target list. The tool almost never determines success rate on its own; the combination of exit IP quality, request fingerprint and request pacing does, which is why two teams running the same framework routinely report success rates thirty points apart.
## Throughput, rendering and resource profile
Throughput numbers only mean something with the cost attached. ScraperAPI delivers 20 – 100 concurrent threads by plan, and can render JavaScript, which is convenient and roughly five to twenty times more expensive per page than a plain fetch.
Use these figures to size infrastructure before committing to a plan or a proxy contract. Work backwards from records per day, apply a realistic success rate, add a retry factor of 1.2–1.6, and only then choose concurrency.
## ScraperAPI pricing and real cost per thousand pages
Credit-based: a plain request costs 1 credit, rendering 10, premium residential 10–25 or more.
Per-success pricing is the reason unlockers exist. On raw proxies a 55% success rate means you pay bandwidth on every failure and maintain the retry ladder yourself; with success-based billing your cost per usable record is knowable before you write code. Model it honestly: at roughly $1 to $3 per thousand successes, a million-record monthly feed is $1,000–$3,000, which is cheap against engineer-months and expensive against a static site you could have crawled for $40.
A useful discipline: express every option as cost per thousand usable records, not cost per month. A plan that looks cheap and delivers a 60% success rate is more expensive than a premium option at 95%, because the failures consume bandwidth, retries, engineering attention and calendar time.
## Best proxies for scraping with ScraperAPI
An unlocker replaces your proxy layer entirely: the vendor chooses the exit IP class, negotiates the TLS fingerprint, sets coherent headers, solves interstitials and retries until the response looks legitimate. That is why you should route only the hard tail through it. Keep cheap datacenter or residential proxies on the majority of URLs and escalate a domain to the unlocker when its measured success rate falls below your threshold — a two-tier router is a fifty-line component that routinely halves the bill.
With ScraperAPI specifically, identity attaches through 40m+ ip pool with automatic rotation; premium residential behind a credit multiplier. Get that wiring right before tuning anything else — a rotation bug that reuses one exit across a thousand requests will look exactly like a bad proxy provider.
## How ScraperAPI handles anti-bot systems
Unlockers exist because challenge solving became a full-time speciality. Behind the endpoint sit maintained browser fingerprints, header profiles, CAPTCHA pipelines and enormous residential pools, all updated as detection vendors ship changes. You trade visibility for success rate: you cannot debug an unlock, so log request IDs, sample responses for content validity — an unlocked page that returns a consent wall is still a failure — and alert on schema drift rather than HTTP status alone.
Practically, treat detection as a budget rather than a binary. Measure success rate per domain daily, escalate a domain one tier at a time — better headers, then better IPs, then a browser, then an unlocker — and stop at the first tier that clears your threshold. Escalating everything to the most expensive tier is the most common and most costly mistake in scraping operations.
## Scaling ScraperAPI in production
Scaling is mostly commercial. Negotiate committed volume for a lower per-request rate, cap concurrency to the plan's limit to avoid throttling, and deduplicate ruthlessly since every duplicate URL is a billed success. Keep a per-domain success ledger so you can demote a target back to plain proxies once it stops fighting you.
- Track success rate, cost per thousand records and bytes per page as your three primary metrics
- Retire proxy sessions automatically on repeated failures instead of retrying blindly
- Deduplicate URLs before dispatch — duplicates cost bandwidth, credits and rate-limit headroom
- Validate content, not just HTTP status: a 200 that returns a consent wall is a failed fetch
- Keep a second fetching path warm so a vendor incident degrades throughput instead of stopping it
## ScraperAPI pros and cons
No scraping tool is universally correct; each one trades cost, control and maintenance in a different ratio. ScraperAPI makes the following trade explicitly.
## Who should use ScraperAPI — and who should not
Choose ScraperAPI when your workload looks like small and mid-size teams that want one endpoint and no infrastructure and your team is comfortable with HTTP API · proxy port · SDKs. It fits organisations that have already decided whether they are buying outcomes or building capability, because it sits clearly on one side of that line: you buy an outcome and trade unit cost for removed maintenance.
Look elsewhere if your targets are unprotected static pages — a self-hosted crawler on datacenter proxies will do the same job for a fraction of the price.
## Compliance and responsible collection
Collecting publicly accessible data is broadly lawful in most jurisdictions, but the surrounding obligations are real: respect robots.txt where it expresses the publisher's intent, avoid authentication walls you have not been granted access to, never collect personal data without a lawful basis under GDPR or equivalent, and keep request rates low enough that you never degrade the target's service.
Reputable proxy providers enforce KYC precisely because misuse of their networks is their liability as well as yours. Document what you collect, why, how long you retain it and who can access it. For AI training corpora, record licensing and provenance per source — that record is increasingly the first thing an auditor or enterprise customer asks to see.
ScraperAPI scorecard and measured performance
Scores below are relative to the other tools in this directory, not to software in general — a 6 for scale still means a tool that handles more traffic than most projects will ever generate. The performance figures come from crawling a mixed basket of static HTML, JavaScript-rendered commerce and lightly protected listing pages from three regions.
Read them alongside your own target list. The tool almost never determines success rate on its own; the combination of exit IP quality, request fingerprint and request pacing does, which is why two teams running the same framework routinely report success rates thirty points apart.
| Criterion | Score | Assessment |
|---|---|---|
| Ease of adoption | 10/10 | Productive on day one |
| Scale ceiling | 8/10 | Fine into the low millions |
| Anti-bot resilience | 8/10 | Good with the right proxies |
| Documentation | 9/10 | Excellent, with runnable examples |
| Value for money | 8/10 | Fair for what it removes from your backlog |
Throughput, rendering and resource profile
Throughput numbers only mean something with the cost attached. ScraperAPI delivers 20 – 100 concurrent threads by plan, and can render JavaScript, which is convenient and roughly five to twenty times more expensive per page than a plain fetch.
Use these figures to size infrastructure before committing to a plan or a proxy contract. Work backwards from records per day, apply a realistic success rate, add a retry factor of 1.2–1.6, and only then choose concurrency.
| Metric | Observed | Notes |
|---|---|---|
| Throughput | 20 – 100 concurrent threads by plan | Per worker or per plan tier, on a stable target |
| JavaScript rendering | Yes (render=true, 10 credits) | Rendering multiplies cost 5–20× versus plain HTTP |
| Memory footprint | None (remote) | Sizing input for container limits |
| Success profile | Good on mainstream commerce and SERP targets | Depends far more on proxy quality than on the tool |
| Proxy support | 40M+ IP pool with automatic rotation; premium residential behind a credit multiplier | How identity is attached to a request |
ScraperAPI pricing and real cost per thousand pages
Credit-based: a plain request costs 1 credit, rendering 10, premium residential 10–25 or more.
Per-success pricing is the reason unlockers exist. On raw proxies a 55% success rate means you pay bandwidth on every failure and maintain the retry ladder yourself; with success-based billing your cost per usable record is knowable before you write code. Model it honestly: at roughly $1 to $3 per thousand successes, a million-record monthly feed is $1,000–$3,000, which is cheap against engineer-months and expensive against a static site you could have crawled for $40.
A useful discipline: express every option as cost per thousand usable records, not cost per month. A plan that looks cheap and delivers a 60% success rate is more expensive than a premium option at 95%, because the failures consume bandwidth, retries, engineering attention and calendar time.
| Plan | Price | What you get |
|---|---|---|
| Free trial | $0 | 1,000 credits, 7 days |
| Hobby | $49 / mo | 100k credits, 20 concurrent threads |
| Startup | $149 / mo | 1M credits, 50 threads, geotargeting |
| Business | $299 / mo | 3M credits, 100 threads, all geos |
Best proxies for scraping with ScraperAPI
An unlocker replaces your proxy layer entirely: the vendor chooses the exit IP class, negotiates the TLS fingerprint, sets coherent headers, solves interstitials and retries until the response looks legitimate. That is why you should route only the hard tail through it. Keep cheap datacenter or residential proxies on the majority of URLs and escalate a domain to the unlocker when its measured success rate falls below your threshold — a two-tier router is a fifty-line component that routinely halves the bill.
With ScraperAPI specifically, identity attaches through 40m+ ip pool with automatic rotation; premium residential behind a credit multiplier. Get that wiring right before tuning anything else — a rotation bug that reuses one exit across a thousand requests will look exactly like a bad proxy provider.
| Target profile | Proxy type | Typical price | Why |
|---|---|---|---|
| Internal APIs, open data, docs sites | Datacenter | $0.30 – $2.00 / IP / mo | No consumer-IP requirement; cheapest possible bandwidth |
| Mid-tier commerce, listings, forums | Rotating residential | $1.00 – $8.00 / GB | Real ISP-assigned IPs clear reputation checks |
| Logged-in accounts, dashboards | ISP / static residential | $1.50 – $6.00 / IP / mo | One stable identity per account, held for months |
| App-only endpoints, hardest anti-bot | Mobile (4G/5G) | $4.00 – $20.00 / GB | Carrier CGNAT makes per-IP blocking costly for the target |
| Everything already blocked | Unlocker API | $0.50 – $3.00 / 1k requests | Challenge solving handled provider-side, billed per success |
Proxy-port mode and structured endpoint
# 1) Proxy mode — zero code change in an existing crawler
import requests
proxies = {"http": "http://scraperapi.country_code=us:APIKEY@proxy-server.scraperapi.com:8001"}
r = requests.get("https://example.com", proxies=proxies, verify=False)
# 2) Structured endpoint — parsed JSON, no selectors
r = requests.get(
"https://api.scraperapi.com/structured/amazon/product",
params={"api_key": "APIKEY", "asin": "B0CX23V2ZK", "country": "us"},
timeout=70,
)
print(r.json()["pricing"])How ScraperAPI handles anti-bot systems
Unlockers exist because challenge solving became a full-time speciality. Behind the endpoint sit maintained browser fingerprints, header profiles, CAPTCHA pipelines and enormous residential pools, all updated as detection vendors ship changes. You trade visibility for success rate: you cannot debug an unlock, so log request IDs, sample responses for content validity — an unlocked page that returns a consent wall is still a failure — and alert on schema drift rather than HTTP status alone.
Practically, treat detection as a budget rather than a binary. Measure success rate per domain daily, escalate a domain one tier at a time — better headers, then better IPs, then a browser, then an unlocker — and stop at the first tier that clears your threshold. Escalating everything to the most expensive tier is the most common and most costly mistake in scraping operations.
Scaling ScraperAPI in production
Scaling is mostly commercial. Negotiate committed volume for a lower per-request rate, cap concurrency to the plan's limit to avoid throttling, and deduplicate ruthlessly since every duplicate URL is a billed success. Keep a per-domain success ledger so you can demote a target back to plain proxies once it stops fighting you.
- +Track success rate, cost per thousand records and bytes per page as your three primary metrics
- +Retire proxy sessions automatically on repeated failures instead of retrying blindly
- +Deduplicate URLs before dispatch — duplicates cost bandwidth, credits and rate-limit headroom
- +Validate content, not just HTTP status: a 200 that returns a consent wall is a failed fetch
- +Keep a second fetching path warm so a vendor incident degrades throughput instead of stopping it
ScraperAPI pros and cons
No scraping tool is universally correct; each one trades cost, control and maintenance in a different ratio. ScraperAPI makes the following trade explicitly.
| Strengths | Weaknesses |
|---|---|
| Easiest onboarding in the category | Credit multipliers make heavy rendering expensive |
| Credit model is easy to reason about | Concurrency capped by plan tier |
| Structured SERP and product endpoints return clean JSON | Less control than raw proxies |
| Failed requests are not charged | Weaker than top-tier unlockers on the hardest targets |
Who should use ScraperAPI — and who should not
Choose ScraperAPI when your workload looks like small and mid-size teams that want one endpoint and no infrastructure and your team is comfortable with HTTP API · proxy port · SDKs. It fits organisations that have already decided whether they are buying outcomes or building capability, because it sits clearly on one side of that line: you buy an outcome and trade unit cost for removed maintenance.
Look elsewhere if your targets are unprotected static pages — a self-hosted crawler on datacenter proxies will do the same job for a fraction of the price.
Compliance and responsible collection
Collecting publicly accessible data is broadly lawful in most jurisdictions, but the surrounding obligations are real: respect robots.txt where it expresses the publisher's intent, avoid authentication walls you have not been granted access to, never collect personal data without a lawful basis under GDPR or equivalent, and keep request rates low enough that you never degrade the target's service.
Reputable proxy providers enforce KYC precisely because misuse of their networks is their liability as well as yours. Document what you collect, why, how long you retain it and who can access it. For AI training corpora, record licensing and provenance per source — that record is increasingly the first thing an auditor or enterprise customer asks to see.
ScraperAPI FAQs
How many credits does a rendered page cost?+
Ten credits for JavaScript rendering, versus one for a plain fetch; premium residential adds a further multiplier.
Can I use ScraperAPI with Scrapy?+
Yes — set the proxy port in your downloader middleware, or call the REST endpoint from start_requests.
Does ScraperAPI charge for failures?+
No. Only successful responses consume credits.
Keywords covered
scraping proxy providers · best proxies for scraping · proxies for web scraping · scraping proxies comparison
