Every web scraper,on the record
The database of web scraping APIs and tools, 14 of them so far. Every price, limit and capability here is the vendor's own published number, quoted with the date we read it.
Three numbers decidea scraping API
Everything else on a vendor's homepage is decoration.
Price per 1,000 requests
Every vendor sells credits, requests or pages on plans with different sizes. We convert each plan to a price per 1,000 successful requests before comparing.
What a credit buys
JavaScript rendering, premium proxies and geotargeting multiply the credit cost of a request, by 5, 10 or 75 on some lists. We print the multipliers, not the headline.
What it actually gets through
Success rates are the vendor's own claims. We list what each one publishes, per target where it does, and nothing it doesn't.
A score you can
recompute yourself
Six criteria, public weights, one line of reasoning per rating. The number is arithmetic on the ratings, not an opinion.
14 scrapers,one rubric
Scored on the same six criteria, from each vendor’s own published pages. Highest score first.
The most legible pricing in this database: the plan card prints the price per 1,000 credits, the documentation prints what each request type and each named domain costs, and only successful requests count. A 99.98% success figure on the homepage is a claim, not a method.
The pricing table answers the question every other vendor makes you compute: standard proxies, standard with JavaScript, premium proxies, premium with JavaScript, each priced per 1,000 requests on each plan, with the rate limit beside it. A free starter plan and a 14-day money-back line finish it.
The credit table is the review: a plain request is one credit, the default headless-browser request five, premium proxies ten, both together twenty-five, stealth proxies seventy-five. Cheap for plain fetches, ordinary once JavaScript and premium proxies are on.
Feature access never gates, the page says, and the plans bear it out: every tier has all five APIs, rendering, the unblocker, residential proxies in 190+ countries and the SDKs; only volume, concurrency, log retention and support change. The credit table is four lines and failures are free.
A clear ladder: five paid tiers from $16 to $456, concurrency printed on each, rollover on paid plans, and the credit rule stated in one sentence. What is missing is any success or latency figure; the word on the page is reliable, not a number.
The price of a page depends on which Actor fetches it and how much compute it burns, so no per-1,000 figure fits. What is public is the platform ladder: a free $5 of monthly usage, three paid tiers whose fee is also their usage credit, compute from $0.20 down to $0.13 a unit, and the add-ons.
Seven plans with threads and geotargeting scope printed on each, a credit-cost page that names the parameters and the domains that cost more, and a written 7-day no-questions refund. Rendering at ten credits makes it dearer than most for JavaScript pages.
The largest free monthly allowance in this database and the only vendor promising unlimited parallel requests on every tier. What it does not print on the pages we read is the credit cost of rendering or residential proxies, so the per-1,000 figure holds for plain requests only.
A long, plain ladder: credits and concurrency printed on every tier, JavaScript rendering at five credits and premium proxies at ten in the documentation, and every dedicated API included on every plan. The free tier is a test drive of 200 credits, not a working allowance.
Pricing written like a tax table: pay as you go on a ladder of brackets, or a monthly block at a lower effective rate with the ladder continuing past it. A failed or blocked request is never billed and a rendered one costs two credits, which is the simplest multiplier in this database.
The unit is a page turned into clean text, one credit each, with search at two credits per ten results and browser time at two a minute. Cheap plans are small: 5,000 pages for $16 is the dearest entry price per 1,000 in this database, and the printed prices assume annual billing.
The Web Scraper API sells finished rows from 800+ site scrapers, a record being one extracted item such as one LinkedIn profile, and bills only what is delivered. The unit makes it the dearest line in this table and the least comparable; the plans behind the slider, $499, $999 and $1,999, are public once you read the page's own data.
No plan sizes at all: a $5 trial credit, thirty days, then a rate per 1,000 successful responses that depends on which tier Zyte puts the target site in and whether you render it. Cheap on easy sites, the dearest browser rate in this database on hard ones.
Two from-prices and a long list of scraping sources are what the public pages give: $49 a month, $0.25 per 1,000 results, a free trial, ISO 27001. The plan table and the scraper API documentation answered our reader with 404, so the ladder, the rendering price and the SDKs are not scored.
Run a scraping API?Get it on the record.
Send us the pages that state your prices, credit costs and limits. We read them, score them on the public rubric, and publish the review with the date.