Scraping API PricesDecodo vs Oxylabs
The current volume and workload boundaries between Decodo and Oxylabs Web Scraper API.
Decodo Web Scraping API
Oxylabs Web Scraper API
The difference
Both paths, one ruler
Decodo Web Scraping API
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
Decodo Web Scraping API does not bill failed fetches, so failures cost nothing here.
- × 1
What the meter counts
100,000 results
One attempt is one billed unit for this workload.
- =
Cash per month
$49.00 /mo
$49 plan. 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.
Oxylabs Web Scraper API
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.
Both ladders share one linear scale, topping out at 105,263 counted units, so a longer bar means more billed work rather than a different drawing.
These figures are for one stated workload: 100,000 JavaScript-rendered pages a month at a 95% success rate. The comparison below names where the answer changes.
Decision boundary: for standard successful results, Decodo covers the first 2,000 with its no-charge allowance and has the lower computed bill through 38,000. The bills tie from 38,001 through 98,000, Decodo is lower from 98,001 through 163,000, the bills tie from 163,001 through 220,000, and Decodo is lower through its last published allowance of 707,000. From 707,001 through 3,330,000, Oxylabs is the only one of the pair with a published self-serve allowance large enough for the workload. (Decodo pricing, Oxylabs Web Scraper API pricing, retrieved July 26, 2026)
That capacity boundary moves earlier for JavaScript and premium routing. Decodo publishes distinct per-result rates for standard, JavaScript, premium, and premium-plus-JavaScript bundles, so the same monthly commitment buys fewer results as the request type changes. Oxylabs likewise publishes separate Amazon, Google, other-site, JavaScript, and media rates. Compare results by target and mode, not the headline standard allowance. (Decodo pricing, Oxylabs Web Scraper API pricing, retrieved July 26, 2026)
Billing models side by side
Decodo sells monthly plans whose four successful-result rates depend on standard or premium proxy access and whether JavaScript is enabled. The four types are mutually selected bundles, not additive charges. It retries internally and says it charges only successfully retrieved results, although the reviewed pages do not provide a complete billable status-code list. Plan limits are published as requests per second rather than concurrent requests. (Decodo pricing, Decodo Web Scraping API introduction, retrieved July 26, 2026)
Oxylabs also uses monthly commitments and target-dependent successful-result rates. Amazon, Google, other sites, JavaScript rendering, and media bandwidth have different unit rates, and the rate falls at larger commitments. HTTP 2xx and 4xx target responses are charged, while Oxylabs system errors with 5xx or 6xx codes are not. Published throughput figures are requests-per-second limits. (Oxylabs Web Scraper API pricing, retrieved July 26, 2026)
The billing definitions create a practical workload flip. Decodo’s “successfully retrieved” wording lacks a status table, while Oxylabs explicitly includes target 4xx responses in billable results. A crawl with many missing or forbidden target pages can consume Oxylabs results differently from the way a buyer might interpret Decodo’s shorter wording. This is a contract difference, not a measured comparison. (Decodo Web Scraping API introduction, Oxylabs Web Scraper API pricing, retrieved July 26, 2026)
What each provides that the other does not
Decodo is the only one of this pair with a published no-charge allowance and a low-volume plan ladder reaching the 707,000 standard-result point without jumping to a large business commitment. It also exposes premium and premium-plus-JavaScript bundles directly in each plan’s result-rate table. (Decodo pricing, retrieved July 26, 2026)
Oxylabs is the only one of this pair whose reviewed table publishes separate Amazon, Google, generic-site, JavaScript, and media-bandwidth rates, plus a self-serve allowance beyond 3,000,000 results. It also defines billable 2xx and 4xx target responses explicitly. (Oxylabs Web Scraper API pricing, retrieved July 26, 2026)
Who should pick which
Pick Decodo for standard-result workloads within 707,000 when its lower bands or tie bands fit, and when the four proxy-and-render bundles match the request shapes. Pick Oxylabs when forecast volume exceeds Decodo’s last public allowance, when target-specific Amazon or Google rates dominate, or when explicit media-bandwidth accounting is required. In the tie bands, use target mix and billable-status treatment as the decision boundary. (Decodo pricing, Oxylabs Web Scraper API pricing, retrieved July 26, 2026)
The unverified items are Decodo’s exact billable status codes and concurrent-request limits, and Oxylabs’ custom-plan minimum commitment. Neither reviewed table publishes annual pricing. Do not extrapolate a plan beyond its stated allowance or invent an overage rate to close those gaps. (Decodo pricing, Decodo Web Scraping API introduction, Oxylabs Web Scraper API pricing, retrieved July 26, 2026)