Scraping API PricesAll products / ScraperAPI
ScraperAPI pricing
How ScraperAPI turns targets and retrieval modes into credit costs, how success is defined, and what buyers still need to ask.
Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.
Your job
What ScraperAPI counts
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- × 1
Attempts you are billed for
100,000 requests
ScraperAPI does not bill failed fetches, so failures cost nothing here.
- × 10
What the meter counts
1,000,000 credits
One attempt is not one billed unit here: this workload multiplies by 10 before any money is involved.
- =
Cash per month
$149.00 /mo
Startup. Cheapest of every eligible purchase option, not the first plan that fits.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
100,000 pages divided by 95% success → 1,000,000 credit → Startup $149.00/mo = $1.49 per 1,000 pages kept
Cheaper for this job
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. Unknown totals never enter the numeric order.
Every ScraperAPI plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Hobby | $49.00 | $44.10 | n/a | 100,000 credit | 20 |
| Startup your job | $149.00 | $134.10 | n/a | 1,000,000 credit | 50 |
| Business | $299.00 | $269.10 | n/a | 3,000,000 credit | 100 |
| Scaling | $475.00 | $427.50 | n/a | 5,000,000 credit | 200 |
| Professional | $975.00 | $877.50 | n/a | 10,500,000 credit | 300 |
| Advanced | $1,975.00 | $1,777.50 | n/a | 21,500,000 credit | 500 |
What consumes a unit
This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.
| Operation | Costs | Per | Source |
|---|---|---|---|
| request.basic | 1 credit | request | source |
| target.amazon | 5 credit | request | source |
| target.google | 25 credit | request | source |
| target.bing | 25 credit | request | source |
| target.linkedin | 30 credit | request | source |
| request.premium_proxy | 10 credit | request | source |
| request.js_render | 10 credit | request | source |
| request.screenshot | 10 credit | request | source |
| request.stealth | 30 credit | request | source |
| target.protected_generic | 10 credit | request | source |
What ScraperAPI does not publish
- No public pay-as-you-go unit rate was obtainable.
- The docs do not define how target, bypass, and parameter credit costs combine.
What ScraperAPI is
ScraperAPI is a managed web scraping API that accepts a target URL and handles proxy rotation, retries, browsers, and blocking countermeasures. It also exposes specialized handling for search engines, ecommerce sites, protected targets, screenshots, and structured output options. It is for developers who want to keep their own extraction logic while outsourcing page access and retry infrastructure. Sources: ScraperAPI and ScraperAPI pricing, retrieved 2026-07-26.
ScrapingBee, ZenRows, and Oxylabs Web Scraper API are the nearest named competitors. ScrapingBee combines its HTML API with AI queries and dedicated data endpoints, ZenRows separates Universal Scraper request credits from a browser-time and bandwidth path, and Oxylabs publishes target-dependent successful-result rates. ScraperAPI’s distinguishing commercial layer is its monthly credit pool with documented costs for target families and retrieval modes. Sources: ScrapingBee pricing, ZenRows pricing, Oxylabs pricing, and ScraperAPI credit guide, retrieved 2026-07-26.
How billing works
One unit is one credit. A basic request consumes the base amount, while Amazon, Google, Bing, LinkedIn, premium proxy, JavaScript rendering, screenshots, stealth, protected-site handling, and combinations can consume more. Some published modes replace the base rate, while the documentation does not define a universal rule for combining every target, bypass, and parameter. Only HTTP 200 and 404 responses are normally charged. A client-cancelled call can still be charged when it is cancelled before ScraperAPI has had its documented completion window. The common buying mistake is to multiply the plan allowance by one basic request and treat that as capacity for every target. Actual consumption follows the target and enabled mode, and some combinations need direct confirmation. Source: ScraperAPI credit and request-cost guide, retrieved 2026-07-26.
What ScraperAPI does not publish
- One rule explaining how every target, blocking-bypass, screenshot, and rendering cost combines. Source reviewed: credit guide, retrieved 2026-07-26.
- A public unit rate for pay-as-you-go use on the plans that support it. Source reviewed: ScraperAPI pricing, retrieved 2026-07-26.
- Queueing above concurrency. The page instead states that excess concurrent requests receive HTTP 429. Sources: ScraperAPI pricing and concurrency guide, retrieved 2026-07-26.
Unused credits reset at the end of the billing period, and lower self-serve plans stop at their limit rather than automatically using overage. Source: ScraperAPI pricing, retrieved 2026-07-26.
Who it suits
ScraperAPI suits teams with a known mix of basic, rendered, premium, and named-target requests that can monitor credits by mode. It is less suitable for procurement that requires one public combination formula or a published overage rate before choosing a plan. The reason is that basic metering and success treatment are clear, but the full cross-product of options is not. Sources: ScraperAPI pricing and credit guide, retrieved 2026-07-26.
Answer
ScraperAPI's dated 2026-07-26 price snapshot gives $149.00 for 100,000 JavaScript-rendered pages on its Startup offer. This older figure is excluded from rankings; check the vendor before buying.
Recorded 2026-07-26 from the vendor's own pricing page.A vendor page moved or could not be matched closely enough. Treat this as an older snapshot and check the vendor before buying.