Cheapest Scraping API: How to Compare the Real Cost

This page is published by Thordata, one of the products compared.

The cheapest scraping API depends on how many usable results your target pages return and what the service charges for each attempt. As of October 2026, Thordata’s Web Scraper API offers a 7-day trial with 5,000 credits, while Bright Data’s SERP API has a free tier with 5,000 requests per month; credits and requests are different billing units. This guide is for buyers comparing scraping APIs with proxy services rather than treating their advertised rates as interchangeable. It shows how to turn each billing unit into a cost per successful result, starting with Thordata’s Web Scraper API pricing.

The cheapest option depends on the pages you scrape

The lowest advertised scraping API price is not necessarily the lowest cost per usable result. A simple page may need only a request and a parser. A JavaScript-heavy page may need rendering, while a protected target may require retries or CAPTCHA handling. Those extra steps can change both the bill and the share of requests that return usable data.

A scraping API is a better fit when it handles those steps and returns the fields you need; buying proxies separately leaves you responsible for extraction and retry logic. For straightforward pages with a working scraper, proxy traffic may be the smaller expense. Thordata’s Web Scraper API pricing is a relevant reference when comparing API charges with that separate-proxy approach.

Last updated: October 2026.

Compare scraping APIs and proxy services separately

A scraping API charges for requests, responses or credits and handles parts of the retrieval workflow; a proxy charges for traffic and leaves collection code to you. Compare API prices with API prices first. A $2 proxy package cannot be ranked against a $30 scraper package without accounting for the scraper, retries and results.

Trial terms are current as of October 2026. Keep proxy-only rates out of scraping API price rankings.

Calculate cost per successful result

A scraping API’s lowest listed rate is not necessarily its lowest cost per usable result. Count the requests or credits charged for successful responses, failed attempts and retries, then divide the bill by usable results. Thordata’s Web Scraper API lists credit packages; its Google Videos SERP API charges only for valid data retrievals, so invalid responses do not increase its response count.

The Web Scraper API pricing also lists a 7-day trial with 5,000 credits. Neither package price alone establishes what a rendered page or premium target will consume in credits.

For a workload estimate, calculate package cost ÷ expected usable results. If a target needs retries, include their billed units in the package quantity before choosing a tier.

Check what each option handles for you

Thordata Web Unlocker handles JavaScript rendering, CAPTCHA resolution, IP rotation and request retries for website extraction. Bright Data SERP API handles rendering, CAPTCHA solving and retries for search results, while ScraperAPI handles Google blocking, CAPTCHAs and parsing. The cheapest scraping API for a workload therefore depends partly on which of those tasks would otherwise require your own code.

For credit-based extraction instead, Thordata lists Web Scraper API packages; compare their output requirements with the managed-page and SERP options before choosing.

Test prices against your own target pages

The cheapest scraping API is the one with the lowest cost per successful result on your target pages, not necessarily the lowest listed price per credit. Run the same representative URLs through each candidate, including straightforward pages and pages that require JavaScript rendering or trigger access challenges. Keep the requested fields, location, and retry limit identical.

1. Build a fixed URL set for each page type. Repeat each run at the times your production job would operate.

2. Record valid results, failed requests, elapsed response time, credits or responses charged, and total spend. Divide spend by valid results; report success rate and median response time separately.

3. Compare results by page type. A lower-priced API loses on cost if failed or incomplete responses consume enough paid capacity to raise its cost per valid result.

Last updated: October 27, 2026. Prices and features were checked in October 2026; use the current Thordata Web Scraper API pricing when setting the test budget.

What should you check before signing up?

The lowest advertised scraping API price may not be the lowest bill for your workload. Before signing up, verify the current plan inclusions, what happens when you exceed them, and whether failed requests consume credits. A low package price matters less if your target pages produce few usable results or require more credits than expected.

Thordata advertises a free trial. Its Web Scraper API pricing is the place to compare the package you intend to use with the trial offer; do not assume the trial covers the same workload.

Before committing, check the terms that apply to the trial and any refund request. In particular, establish when paid usage begins and what happens to unused credits if you stop. Last updated: October 2026.

How to choose

Choose Thordata’s Web Scraper API when you need structured results without managing proxies: its credit packages charge for successful results. The Web Scraper API pricing suits a buyer who can estimate credit use from a defined set of target pages. A proxy is the better fit when you already run the scraper and need control over its requests.

FAQ

Which web scraping API has the cheapest official pricing in 2026?

There is no single cheapest API for every workload: the lowest stated paid Thordata Web Scraper API pack is 30,000 credits for $30.00, while ScraperAPI lists 100,000 SERP API credits for $49 per month, as of October 2026. Those credits cover different products, so neither price establishes the cheaper cost per successful webpage result. ScrapingBee and ZenRows cannot be ranked from the prices used in this comparison.

What does Bright Data charge per 1,000 Web Unlocker requests in 2026?

Bright Data’s Web Unlocker rate per 1,000 requests cannot be determined from the pricing figures used here. Bright Data’s separately priced SERP API lists pay-as-you-go usage at $1.5 per 1,000 requests and a $499-per-month plan with 380K requests, as of October 2026; those are not Web Unlocker rates.

What is Scrape.do’s official API price?

Scrape.do’s API price cannot be established from the pricing figures used here. A price comparison with Scrape.do therefore needs its rate for the intended request type and the number of billable requests required to return a successful result.

What is ScraperAPI’s official web scraping API price?

ScraperAPI lists 100,000 SERP API credits for $49 per month and a 7-day trial with 5,000 API credits, as of October 2026. That is a search-results product price, not a general web scraping API rate; do not use it to estimate the cost of collecting arbitrary webpages.

What is ScrapingBee’s official API price?

ScrapingBee’s API price cannot be established from the pricing figures used here. Without its billing rate for the pages and settings in question, a per-1,000-request comparison against another API would imply a cost that has not been established.

Is a free plan or pay-as-you-go API cheaper than a package?

A free plan costs less only while the workload fits its allowance; pay-as-you-go costs less than a package when the charge for expected billable usage stays below the package price. As of October 2026, Bright Data’s SERP API includes 5K requests and 5K records per month in its free tier, while Thordata’s Web Scraper API offers a 7-day trial with 5,000 credits. Scrape.do, Crawlbase and ScrapingAnt need their own billing rates before they can be placed in that calculation.

Can ScraperAPI, ScrapingBee and ZenRows be compared by price per 1,000 requests?

A price per 1,000 requests is comparable only when each provider counts the same kind of request and charges for the same outcome. ScraperAPI’s stated $49-per-month plan supplies 100,000 SERP API credits, as of October 2026, rather than a quoted price for 100,000 successful webpage results. ScrapingBee and ZenRows cannot be given equivalent rates from the figures used here.

Does a failed scrape still use up credits?

Failed scrapes do not always have the same billing treatment across products. Thordata’s YouTube Shorts and Comments scrapers say they charge only for successful results; its Web Scraper API pricing uses credit packages, so the charge for a target-page workload should be calculated under that product’s credit rules rather than borrowed from another Thordata scraper.

Should I compare proxies with scraping APIs on price per request?

No: compare them on cost per successful result from the same target pages. Thordata’s residential proxies start at 1 GB for $2.00, while its Web Scraper API’s smallest stated paid pack is 30,000 credits for $30.00, as of October 2026. Proxy traffic pays for bytes transferred and leaves scraping logic with you; an API credit price cannot be converted to a per-page cost without the workload’s usage and success rate.