Scraping API PricesAll products / Oxylabs Web Scraper API
Oxylabs Web Scraper API pricing
How Oxylabs bills target-dependent successful results and media traffic, what remains unpublished, and which buyers 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 Oxylabs Web Scraper API counts
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 0.95
Attempts you are billed for
105,263 requests
Oxylabs Web Scraper API bills failed fetches, so a 5% failure rate is billed work.
- × 1
What the meter counts
105,263 requests
One attempt is one billed unit for this workload.
- =
Cash per month
$136.84 /mo
Starter. 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 → 105,263 request → Starter $136.84/mo = $1.37 per 1,000 pages kept
The arithmetic, line by line
- pages: 0.0011 usd per result on Startersource
- request.js_render: 0.0013 usd per result on Startersource
- billed on 105,263 attempts, not 100,000 successes, because this vendor charges for failed requestssource
- consumes 105,263.16 request per month
- cheapest way to buy that: Starter, $136.84 of metered usage = $136.84 per monthsource
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. Unknown totals never enter the numeric order.
Every Oxylabs Web Scraper API plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Micro | $49.00 | n/a | n/a | 98,000 result | n/a |
| Starter your job | $99.00 | n/a | n/a | 220,000 result | n/a |
| Business | $999.00 | n/a | n/a | 3,330,000 result | n/a |
| Custom+ | Not published | n/a | n/a | n/a | n/a |
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 |
|---|---|---|---|
| target.amazon | 0.0005 usd | result | source |
| target.google | 0.001 usd | result | source |
| request.basic | 0.00115 usd | result | source |
| request.js_render | 0.00135 usd | result | source |
What Oxylabs Web Scraper API does not publish
- Annual pricing was not published.
- The Custom+ monthly minimum commitment was not published.
- Concurrent-request limits were not published; the page gives requests-per-second rate limits instead.
What Oxylabs Web Scraper API is
Oxylabs Web Scraper API retrieves public web pages and can return raw HTML or parsed data from a library of preconfigured targets. The same product covers general websites, search targets, ecommerce targets, and JavaScript-rendered pages while handling proxy rotation behind the API. It is for engineering and data teams that want a managed retrieval layer rather than a proxy connection they must operate themselves. Sources: Oxylabs Web Scraper API and Oxylabs pricing, retrieved 2026-07-26.
Bright Data Web Unlocker, Zyte API, and ScraperAPI are the nearest named comparisons. Bright Data Web Unlocker foregrounds one successful-request unit, Zyte selects among target-difficulty tiers and optional add-ons, and ScraperAPI uses request credits with mode and target costs. Oxylabs instead publishes different successful-result rates for Amazon, Google, other sites, and JavaScript work, with media traffic treated separately. Sources: Bright Data Web Unlocker pricing, Zyte pricing, ScraperAPI pricing, and Oxylabs pricing, retrieved 2026-07-26.
How billing works
One unit is one successful result. The target category or JavaScript mode selects the result rate rather than adding several public request multipliers together. Media transferred through the service has a separate bandwidth meter. Oxylabs counts target responses in the HTTP 2xx and 4xx classes as successful and billable, while provider-side 5xx and 6xx errors are not billed. The common buying mistake is to treat the plan’s maximum result allowance as a fixed allowance for every workload. That maximum assumes the least costly target category, so a mix containing other targets, JavaScript rendering, or media can produce fewer results from the same commitment. Source: Oxylabs pricing, retrieved 2026-07-26.
What Oxylabs does not publish
- An annual self-serve price or annual discount for this product. Source reviewed: Oxylabs pricing, retrieved 2026-07-26.
- The minimum monthly commitment for the Custom+ path. Source reviewed: Oxylabs pricing, retrieved 2026-07-26.
- A concurrent-request limit. The public figures describe requests per second, which is a different capacity control. Source reviewed: Oxylabs pricing, retrieved 2026-07-26.
Who it suits
Oxylabs suits teams that can classify demand by target family and want raw or parsed delivery through one managed API. It is less suitable when procurement requires one identical unit rate across every site, a public annual term, or a published concurrent-request ceiling before a call. The reason is that the result definition is clear, but workload mix and media traffic still determine effective consumption. Sources: Oxylabs Web Scraper API and Oxylabs pricing, retrieved 2026-07-26.
Answer
Oxylabs Web Scraper API's dated 2026-07-26 price snapshot gives $136.84 for 100,000 JavaScript-rendered pages on its Starter 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.