All products / Decodo Web Scraping API

Decodo Web Scraping API pricing

How Decodo counts successful results across request types, what its public pricing omits, and which scraping teams fit.

ExactPrice recorded on 2026-07-26Older price from 2026-07-26; excluded from rankings2 vendor sourcesSee the calculation
Available volumes

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

Workload100,000 pages per month
JavaScript renderingrequired
Bills failed fetchesno
per 1,000 pages kept$0.49

What Decodo Web Scraping API counts

1pages: 1 result per request
2request.js_render: 1 result per request
363,000 of the included allowance goes unused, 39% of what you buy
=You consume100,000 result

What you pay

$49.00ExactEvery figure is published; the arithmetic below is checkable.$49 plan, monthly list price63,000 of the included allowance goes unused.
  1. Successes you want

    100,000 pages

    Your stated workload. Every vendor on this site is priced against this same number.

  2. × 1

    Attempts you are billed for

    100,000 requests

    Decodo Web Scraping API does not bill failed fetches, so failures cost nothing here.

  3. × 1

    What the meter counts

    100,000 results

    One attempt is one billed unit for this workload.

  4. =

    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.

100,000 pages divided by 95% success 100,000 result $49 plan $49.00/mo = $0.49 per 1,000 pages kept

The arithmetic, line by line
  1. pages: 1 result per requestsource
  2. request.js_render: 1 result per requestsource
  3. consumes 100,000 result per month
  4. cheapest way to buy that: $49 plan, 163,000 included = $49.00 per monthsource
  5. 63,000 of the included allowance goes unused, 39% of what you buy

Every Decodo Web Scraping API plan

Published plans, with the offer this workload actually selects marked
PlanMonthlyIf billed yearlyPrepaid packIncludedSimultaneous sessions
Free$0.00n/an/a2,000 resultn/a
$19 plan$19.00n/an/a38,000 resultn/a
$49 plan your job$49.00n/an/a163,000 resultn/a
$99 plan$99.00n/an/a707,000 resultn/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.

Every published way Decodo Web Scraping API charges
OperationCostsPerSource
request.basic1 resultrequestsource
request.js_render1 resultrequestsource
request.premium_proxy1 resultrequestsource

What Decodo Web Scraping API does not publish

What Decodo Web Scraping API is

Decodo Web Scraping API is a managed page-retrieval service that handles proxy routing and internal retries and can add JavaScript rendering or premium proxy access. It also covers search-engine retrieval use cases. ScraperAPI, ZenRows, and Bright Data Web Unlocker are the nearest named competitors because each offers an API that returns web content while handling blocking infrastructure. Decodo’s pricing distinction is a successful-result model with separate request classes for standard access, JavaScript rendering, premium access, and the combination of premium access with rendering. Sources: Decodo Web Scraping API pricing, Decodo API introduction, ScraperAPI pricing, ZenRows pricing, and Bright Data Web Unlocker pricing, retrieved 2026-07-26.

How billing works

One unit is one successfully retrieved result. The chosen request class determines how quickly a plan’s result allowance is used: standard requests consume the balance at the lowest rate, while JavaScript, premium proxy access, or both use a higher rate. The four classes are alternative bundles rather than charges that a buyer should add by hand. Internal retries are included, and Decodo says only successful retrievals are charged. The common buying mistake is to read the standard-result allowance as the number available for every workload. A premium JavaScript workload yields fewer results from the same plan balance. Sources: Decodo Web Scraping API pricing and Decodo API introduction, retrieved 2026-07-26.

What Decodo does not publish

  • An annual self-serve rate for Web Scraping API. Source reviewed: Decodo pricing, retrieved 2026-07-26.
  • A complete list of HTTP statuses that count as a successful, billable result. Source reviewed: Decodo API introduction, retrieved 2026-07-26.
  • Numeric concurrent-request allowances; the public page publishes requests-per-second limits instead. Source reviewed: Decodo pricing, retrieved 2026-07-26.
  • A self-serve overage rule independent of the published plan result allowances. Source reviewed: Decodo pricing, retrieved 2026-07-26.

Who it suits

Decodo suits teams that want success-only page retrieval and can classify traffic in advance as standard, rendered, premium, or premium rendered. It is less suitable for interactive browser automation or for a buyer that cannot predict the mix of request classes. The reason is that the endpoint model is simple after classification, but the effective result volume changes materially with rendering and proxy requirements. Buyers should test representative domains before treating the headline standard allowance as capacity. Sources: Decodo pricing and Decodo API introduction, retrieved 2026-07-26.

Answer

Decodo Web Scraping API's dated 2026-07-26 price snapshot gives $49.00 for 100,000 JavaScript-rendered pages on its $49 plan 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.