Decodo vs Nimble
The rendered-page boundaries between monthly successful-result bundles and per-successful-URL billing.
Decodo Web Scraping API
Nimble
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.
Nimble
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
Nimble does not bill failed fetches, so failures cost nothing here.
- × 1
What the meter counts
100,000 requests
One attempt is one billed unit for this workload.
- =
Metered cash this month
$130.00 /mo
Pay as you go. 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 100,000 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.
The boundary
For recurring browser-rendered successful URLs after one-time signup credit is excluded, Decodo is cheaper through its recurring allowance of 1,000 rendered results a month. Nimble becomes cheaper at 1,001 and remains lower through 14,611 URLs. The cents-rounded bills tie at $19 from 14,612 through 14,619, and Decodo becomes strictly cheaper at 14,620 because its $19 plan includes up to 25,000 JavaScript results while Nimble continues at $0.0013 per successful rendered URL. The unrounded crossing is about 14,615 URLs. (Decodo Web Scraping API pricing, Nimble pricing documentation, retrieved 2026-07-26)
That verdict flips again at Decodo’s plan steps. At 25,001 rendered URLs, Decodo moves to its $49 plan while Nimble’s cents-rounded bill is $32.50, so Nimble is lower until roughly 37,690. Decodo then becomes lower and remains so through the $49 plan’s 75,000 rendered-result allowance. At 75,001, Decodo moves to $99 and Nimble’s cents-rounded bill is $97.50, so Nimble is briefly lower until roughly 76,150; Decodo is lower after that through the final published self-serve allowance of 165,000 rendered results. These figures compare the published JavaScript class, not standard or stealth retrieval. (Decodo Web Scraping API pricing, Nimble pricing documentation, retrieved 2026-07-26)
Billing models side by side
Decodo sells monthly bundles of successful results. Each plan publishes different capacities for standard access, JavaScript, premium proxy, and premium plus JavaScript. Those four figures are alternative request classes, not additive charges. Internal retries are included and Decodo says only successfully retrieved results are charged. The recurring free plan itself has different class capacities, including 1,000 JavaScript results rather than the larger standard-result headline. (Decodo Web Scraping API pricing, Decodo API introduction, retrieved 2026-07-26)
Nimble’s self-serve Extract, Crawl, and Map APIs charge per successfully processed URL. The published direct rates are selected by the extraction driver: standard, JavaScript, or stealth. Nimble can escalate the driver automatically, so a target that requires stealth does not remain at the JavaScript rate used by this page. Its 5,000-page free credit is a one-time trial and is excluded from the recurring boundary. Nimble also sells managed Data Services through annual commitments, but those plans are a different purchase path. (Nimble pricing documentation, retrieved 2026-07-26)
What each does that the other does not
Decodo is the only member of this pair whose reviewed self-serve table gives four explicit plan capacities for the combinations of standard or premium access and rendering on or off. Nimble is the only member whose reviewed pricing exposes automatic driver escalation, Map and Crawl under the same successful-URL schedule, separate deep-search rates, and a managed Data Services path with annual commitments and data-retention allowances. The choice is therefore partly about whether the buyer wants to classify the request before sending it or let the service select an extraction driver. (Decodo Web Scraping API pricing, Nimble pricing documentation, retrieved 2026-07-26)
Who should pick which
Pick Decodo inside the low recurring free allowance and inside the upper portions of each paid JavaScript bundle, where the fixed plan has been sufficiently used. Pick Nimble immediately after a Decodo plan step, while the next bundle contains too much unused capacity, or when a per-successful-URL bill is preferable to a monthly block. If the target mix includes standard or stealth pages, compute those rows separately because Decodo changes the plan capacity by class and Nimble changes the unit rate by driver. (Decodo Web Scraping API pricing, Nimble pricing documentation, retrieved 2026-07-26)
Neither reviewed source publishes a numeric direct-API concurrency limit that can be compared cleanly. Decodo publishes requests-per-second limits instead, while Nimble’s managed plans publish concurrent agents, which is a different control. Neither omission is converted into a throughput or reliability claim here. (Decodo Web Scraping API pricing, Nimble pricing documentation, retrieved 2026-07-26)