ScraperAPI review 2026: pricing, credits and who it's for

ScraperAPI at a glance

Everything in this table comes from ScraperAPI's pricing page and docs, read on November 4, 2026.

What ScraperAPI does, in plain words

Scraping a site yourself sounds easy until the site blocks you. Your IP gets banned, a CAPTCHA appears, or the page loads its content with JavaScript, so your script gets an empty shell. ScraperAPI sits in the middle. You call its endpoint with the page you want, it picks a proxy, retries when it gets blocked, renders the page if you ask, and returns the HTML. For some popular sites, Google and Amazon among them, it can return clean JSON instead.

You don't manage proxy lists or headless browsers. You pay in credits, and you're only charged for successful requests.

There are three ways to use it:

• The API. One HTTP request per page. Works from Python, Node, PHP or anything else that can make a request.
• Structured data endpoints. Ready-made parsers for Google search, Amazon and a few other sites. You get fields, not HTML.
• DataPipeline and the crawler. Schedule jobs from the dashboard without hosting a script. Handy for weekly runs.

ScraperAPI pricing in 2026

Monthly prices below; annual billing takes 10% off the first three plans.

From Scaling up you can switch on pay-as-you-go for overage. Hobby to Professional can auto-upgrade when you run out. If you send more parallel requests than your thread limit, the extra ones get a 429 error, so the thread count matters as much as the credits.

What a credit really buys

This is where most ScraperAPI reviews go quiet. Credits aren't requests. The cost depends on the site:

Sites with heavy anti-bot protection can cost 10 more credits per request. JavaScript rendering and premium proxies also cost extra, so check the credit cost in the dashboard before a big run.

Google in dollars. On Hobby, 4,000 Google searches for $49 works out to about $12.25 per 1,000. On Startup it's about $3.73, on Business about $2.49. A dedicated SERP API like DataForSEO charges $0.60 to $2.00 per 1,000 Google SERPs, and Serper about $1.00 or less. So ScraperAPI isn't the cheap way to buy Google data. It's the convenient way if you already pay for it for other sites. Our cheapest SERP API comparison has the full price table.

Start the 7-day trial with 5,000 free credits

Free trial, free plan and coupons

Free trial. New accounts get 7 days and 5,000 credits, with no card. That's 5,000 normal pages or 200 Google searches. Enough to point it at the sites you care about and see if it gets through.

Free plan. After the trial you drop to 1,000 credits a month with 5 threads. That covers small checks and a hobby script, not production work.

Coupon codes. We searched in November 2026 and didn't find a working public ScraperAPI coupon. The discounts that exist: 10% off for annual billing on Hobby, Startup and Business, and the free trial itself.

Refunds. ScraperAPI offers a refund within 7 days of buying, and you can cancel any time. Credits don't roll over, so don't buy Business "just in case".

Pros and cons

Pros - One API for proxies, CAPTCHAs and JavaScript, no proxy lists to manage - Ready-made JSON for Google and Amazon - Charged only for successful requests (200 and 404 responses) - No-code scheduling with DataPipeline - Free trial with 5,000 credits and no card - 7-day refund

Cons - Google costs 25 credits, so SERP data is expensive on small plans - Credits don't roll over - Geotargeting outside the US and EU starts on the $299 Business plan - Annual discount only on the first three plans - Credit cost changes with the site and options, so budgets need a test run

ScraperAPI vs the alternatives

Prices are list prices from each vendor's site on November 4, 2026.

The table makes one thing obvious. If Google is most of your volume, use a SERP API. If you scrape stores, listings, news sites and the odd SERP, a general scraper like ScraperAPI or ScrapingBee does more for the money. Between those two, ScrapingBee is cheaper per credit on paper: 1 million credits cost $99 there and $149 at ScraperAPI, 3 million cost $249 against $299. ScraperAPI's case is the bigger trial, the no-code DataPipeline and the ready-made Google and Amazon parsers. Credit rules for rendering and premium proxies differ between the two, so run the same target sites through both trials before you decide.

If you only need rankings: the SE Ranking option

A lot of people look at ScraperAPI because they want to track where their pages rank. You can build that: send a Google search per keyword per day, parse the results, store the positions. But on Hobby that's 4,000 searches a month, which is about 130 keywords checked daily. And you still have to write the parser, the database and the charts.

SE Ranking does the whole job without code. Core checks 2,000 keywords a day across 10 projects for $129/mo ($103.20 billed annually), and it adds keyword research, site audits and backlink data. If you need the raw numbers in your own tools later, SE Ranking also sells API access. Our SE Ranking review has the plan details, and the build or buy guide to rank tracking APIs does the cost maths both ways.

Try SE Ranking free for 14 days

Who should use ScraperAPI

• Developers who scrape many different sites and don't want to run proxies
• Teams collecting product, price or listing data on a schedule
• SEO and data folks who need some Google results alongside other pages
• Anyone who wants to test a scraping idea for free before committing

Look elsewhere if Google SERPs are your main volume (try a dedicated SERP API), or if you only need rank tracking and would rather not code (see our best rank tracker guide).

How we reviewed ScraperAPI

On November 4, 2026 we read ScraperAPI's pricing page, its documentation on credit costs and concurrency, and its refund terms. All plan figures and credit costs above are quoted from those pages. Competitor prices come from each vendor's own pricing page on the same day. The per-1,000 figures are our arithmetic from those list prices.

We haven't run a controlled success-rate test on ScraperAPI, so we don't publish one. John F., the ToolVerdict team member who works with SEO APIs and AI tools day to day, hasn't used ScraperAPI on a project, so there's no hands-on quote here. When we do test it, we'll add the results with dates.

We earn a commission from ScraperAPI and SE Ranking links. Links to ScrapingBee, SerpApi, Serper and DataForSEO are plain links. See our affiliate disclosure.