Scraping API PricesAll products / ScrapeOps
ScrapeOps pricing
How the ScrapeOps Proxy API Aggregator routes requests and charges feature-dependent credits, with the remaining gaps and fit.
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 ScrapeOps 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
ScrapeOps 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
$99.00 /mo
1M. 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 → 1M $99.00/mo = $0.99 per 1,000 pages kept
Every ScrapeOps plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| 25K | $9.00 | n/a | n/a | 25,000 credit | 1 |
| 50K | $15.00 | n/a | n/a | 50,000 credit | 1 |
| 100K | $19.00 | n/a | n/a | 100,000 credit | 1 |
| 250K | $29.00 | n/a | n/a | 250,000 credit | 5 |
| 500K | $54.00 | n/a | n/a | 500,000 credit | 25 |
| 1M your job | $99.00 | n/a | n/a | 1,000,000 credit | 50 |
| 2M | $199.00 | n/a | n/a | 2,000,000 credit | 75 |
| 3M | $249.00 | n/a | n/a | 3,000,000 credit | 100 |
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 |
| request.js_render | 10 credit | request | source |
| request.residential_proxy | 10 credit | request | source |
| request.mobile_proxy | 25 credit | request | source |
| request.ai_extraction | 25 credit | request | source |
| request.captcha_solve | 10 credit | request | source |
| target.google | 10 credit | request | source |
| target.linkedin | 70 credit | request | source |
| target.protected_generic | 10 credit | request | source |
What ScrapeOps does not publish
- The single combine field cannot represent both replacement bundles and the additive 25-credit LLM charge.
- Annual pricing was not published.
What ScrapeOps is
This page covers the ScrapeOps Proxy API Aggregator, not its separately sold residential and mobile proxy aggregator. The API routes a scrape through a pool of smart proxy API providers from one endpoint, can switch providers for the target, and includes options for JavaScript, proxy classes, blocking countermeasures, and LLM extraction. It is for teams that want an aggregation layer instead of maintaining separate integrations and accounts with several scraping providers. Source: ScrapeOps Proxy Aggregator, retrieved 2026-07-26.
ScraperAPI, Zyte API, and ScrapingBee are the nearest named comparisons and are also among the kinds of direct providers the aggregator is designed to sit above. Buying one of those services means selecting and integrating a specific vendor. Buying the ScrapeOps API Aggregator means sending a request to a routing layer that chooses among providers and exposes its own credit formula. Sources: ScrapeOps Proxy Aggregator, ScraperAPI pricing, Zyte pricing, and ScrapingBee pricing, retrieved 2026-07-26.
How billing works
One unit is one credit, but a successful request can consume a replacement bundle or an additive combination. Basic retrieval, JavaScript modes, residential routing, mobile routing, protected-site levels, and named targets each have published credit treatments. LLM extraction adds credits to the selected retrieval path, and its documented totals change again when JavaScript or premium access is enabled. Only HTTP 200 and 404 responses consume credits. The common buying mistake is to treat every option as an independent multiplier or, at the other extreme, assume the highest selected option replaces everything. The published table contains both replacement bundles and an additive LLM charge, so each intended combination must be mapped directly. Source: ScrapeOps request-cost documentation, retrieved 2026-07-26.
What ScrapeOps does not publish
- One universal combination rule covering proxy class, rendering, protected targets, CAPTCHA treatment, named targets, and LLM extraction. Source reviewed: request-cost documentation, retrieved 2026-07-26.
- Annual plan pricing. Source reviewed: ScrapeOps Proxy Aggregator, retrieved 2026-07-26.
- A pay-as-you-go overage rate. The plans instead describe renewal, upgrade, or blocking behavior at exhaustion, and credits do not roll over. Sources: ScrapeOps Proxy Aggregator and request-cost documentation, retrieved 2026-07-26.
Who it suits
ScrapeOps suits teams that value one endpoint across multiple underlying providers and can model the exact feature combination they send. It is less suitable for buyers that require a direct contractual relationship with the delivery provider or one flat credit cost for every request. The reason is structural: the product is an aggregator with routing and several request classes, not merely another basic URL fetcher. Sources: ScrapeOps Proxy Aggregator and request costs, retrieved 2026-07-26.
Answer
ScrapeOps's dated 2026-07-26 price snapshot gives $99.00 for 100,000 JavaScript-rendered pages on its 1M offer. This older figure is excluded from rankings; check the vendor before buying.
Recorded 2026-07-26 from the vendor's own pricing page.We could not confirm this price in the latest check, so it remains visible for context but cannot lead a price ranking. Check the vendor's pricing page before buying.