Scraping API Prices
MenuClose

Search the site

82 providers, their alternatives and head-to-heads, targets, guides and answers

Home / Web scraping APIs / ScraperAPI

ScraperAPI pricing

100,000 JavaScript-rendered pages a month cost $149.00 on ScraperAPI's Startup plan.

Checked Oct 12, 2026 on ScraperAPI's own pricing page

100,000
  1. Hobby
  2. Startup
  3. Business
  4. Scaling
  5. Professional
Your workloadType an exact volume, change the success rate or copy a link to this jobEdit

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.

The ScraperAPI plans from 10K to 1M

5 of 6 published plans, with the volumes on the scale each one covers; the plan this job selects is marked
PlanCoversBilled monthlyBilled yearly, per month IncludedConcurrent
Hobby 10K pages $49.00 $44.10saves 10% 100,000 credits 20
Startup fits your volume 25K to 100K pages $149.00 $134.10saves 10% 1,000,000 credits 50
Business 250K pages $299.00 $269.10saves 10% 3,000,000 credits 100
Scaling 500K pages $475.00 $427.50saves 10% 5,000,000 credits 200
Professional 1M pages $975.00 $877.50saves 10% 10,500,000 credits 300

All 6 ScraperAPI plans, with what each charges past its allowance, are further down.

Your job

Workload100,000 pages per month
JavaScript renderingrequired
Bills failed fetchesno
per 1,000 pages kept$1.49

What ScraperAPI bills you for

1pages: 1 credit per request
2JavaScript rendering: 10 credits per request
=You consume 1,000,000 credits

What you pay

$149.00 Published bill Every figure is published; the arithmetic below is checkable. Startup, monthly list price Check ScraperAPI's official pricing

Every ScraperAPI plan

Published plans; the plan this job selects is marked
PlanBilled monthlyBilled yearly, per month IncludedPast the allowanceConcurrent requests
Hobby $49.00 $44.10saves 10% 100,000 credits move to a bigger plan 20
Startup fits your volume $149.00 $134.10saves 10% 1,000,000 credits move to a bigger plan 50
Business $299.00 $269.10saves 10% 3,000,000 credits move to a bigger plan 100
Scaling $475.00 $427.50saves 10% 5,000,000 credits move to a bigger plan 200
Professional $975.00 $877.50saves 10% 10,500,000 credits move to a bigger plan 300
Advanced $1,975.00 $1,777.50saves 10% 21,500,000 credits move to a bigger plan 500

ScraperAPI is also sold as one of the SERP APIs (100,000 standard searches a month: $299.00 on Business).

About this price and its sources

How ScraperAPI turns targets and retrieval modes into credit costs, how success is defined, and what buyers still need to ask.

Published bill Price checked Oct 12, 2026 Checked Oct 12, 2026 2 vendor sources See the calculation

Cite this price

100,000 JavaScript-rendered pages a month cost $149.00 on ScraperAPI's Startup plan. Price read from https://www.scraperapi.com/pricing/ on Oct 12, 2026. Scraping API Prices, https://scrapingapiprices.com/scraperapi-pricing

How the bill builds up

  1. Base rate1 creditper request
  2. → JavaScript rendering10 creditsper request; replaces the base rate
  3. × Premium proxyNot requiredNot part of this workload
  4. ÷ Success rate1Failed requests are not billed
  5. = Billed units per page you keep10 creditsFrom this bill’s calculation
  6. = per 1,000 pages kept$1.49Startup, billed monthly
Credits and multipliersJavaScript renderingBilled failuresSuccess rateConcurrencyFree tierRenews monthly

The bill at your volume

100,000 pages per month · $149.00

Monthly bill or prepaid purchase$475.00
25,000Pages per month500,000
Solid steps show published plan prices. Dashed segments include metered usage or overage. Gaps mean no complete published bill. These are the same dated prices as the calculation above.
Read the chart as a table
ScraperAPI bills at the available volumes
VolumeBillOffer
10,000$49.00Hobby
25,000$149.00Startup
50,000$149.00Startup
100,000$149.00Startup
250,000$299.00Business
500,000$475.00Scaling
1,000,000$975.00Professional
Follow each billed unit
  1. Successes you want

    100,000 pages

    Your stated workload. Every vendor on this site is priced against this same number.

  2. × 1

    Attempts you are billed for

    100,000 requests

    ScraperAPI does not bill failed fetches, so failures cost nothing here.

  3. × 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.

  4. =

    Cash per month

    $149.00 /mo

    Startup: the cheapest way to buy this volume, not just the first plan big enough.

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 credits → Startup $149.00/mo = $1.49 per 1,000 pages kept

The arithmetic, line by line
  1. pages: 1 credit per request source
  2. JavaScript rendering: 10 credits per request source
  3. consumes 1,000,000 credits per month
  4. cheapest way to buy that: Startup, 1,000,000 included = $149.00 per month source

What makes it cost more

One page is not always one billed unit. These are ScraperAPI's published charges for each kind of work; failed requests are not billed.

Every published way ScraperAPI charges
WorkCostsPerSource
A standard page 1 credit request source
Amazon pages 5 credits request source
Google pages 25 credits request source
Bing pages 25 credits request source
Linkedin pages 30 credits request source
Premium proxies 10 credits request source
JavaScript rendering 10 credits request source
A screenshot 10 credits request source
Stealth mode for the hardest sites 30 credits request source
Protected sites 10 credits request source
JavaScript rendering with premium proxies 25 credits request source
JavaScript rendering with stealth mode for the hardest sites 75 credits request source

Limits and terms

What ScraperAPI publishes beyond the price: the limits a job runs into and the terms that change what a plan is worth. Each line links the page it comes from and the day it was read.

Speed, concurrency and sessions

  • Requests above the concurrency limit receive HTTP 429 and are not queued. source, read Jul 26, 2026

Credits, renewal and billing

  • Unused credits reset each billing period and do not roll over. source, read Jul 26, 2026
  • Hobby, Startup, and Business stop at the plan credit limit unless upgraded; pay-as-you-go is limited to Scaling and above. source, read Jul 26, 2026

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. APIs without a full public price aren't ranked. Showing 6 of 14; see the rest.

What ScraperAPI does not publish

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, checked Jul 26, 2026.

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, ScraperAPI credit guide, checked Jul 26, 2026; Oxylabs pricing, checked Oct 9, 2026.

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, checked Jul 26, 2026.

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, checked Jul 26, 2026.