Scraping API PricesAll products / Nimble
Nimble pricing
How Nimble selects extraction drivers and bills successful URLs, what remains workload-dependent, and which teams 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 Nimble 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
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.
100,000 pages divided by 95% success → 100,000 request → Pay as you go $130.00/mo = $1.30 per 1,000 pages kept
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 Nimble plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Pay as you go your job | Not published | n/a | n/a | n/a | n/a |
| Data Services Startup | Not published | $2,500.00 | n/a | 350,000 page | n/a |
| Data Services Scale | Not published | $7,000.00 | n/a | 1,200,000 page | n/a |
| Data Services Professional | Not published | $15,000.00 | n/a | 3,000,000 page | 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 |
|---|---|---|---|
| request.basic | 0.0009 usd | page | source |
| request.js_render | 0.0013 usd | page | source |
| request.stealth | 0.00145 usd | page | source |
| search.query | 0.001 usd | search | source |
| search.deep | 0.004 usd | search | source |
What Nimble does not publish
- No public request-concurrency limits were published.
- No public affiliate terms were obtainable.
What Nimble is
Nimble offers direct APIs for web extraction, crawling, mapping, search, agents, media download, and proxies, plus managed Data Services plans for production pipelines. It is for teams that want Nimble to select an extraction driver based on whether a target needs standard retrieval, JavaScript execution, or stealth handling. Bright Data Web Unlocker, Firecrawl, and Oxylabs Web Scraper API are the nearest named comparisons. Nimble’s distinctive pricing behavior is automatic driver escalation paired with successful-URL billing for its direct extraction APIs. Sources: Nimble pricing documentation, Nimble, Bright Data Web Unlocker pricing, Firecrawl pricing, and Oxylabs Web Scraper API, retrieved 2026-07-26.
How billing works
For Extract, Crawl, and Map, one unit is a successfully processed URL. The selected driver sets the rate: standard retrieval, JavaScript rendering, and stealth rendering have different rates, and Nimble can escalate automatically. These are replacement driver rates rather than three charges added together. Crawl usage is the sum of its Extract requests. Search and AI-generated answers use separate per-input meters, while deep search can also add underlying Extract or Agent costs. The common buying mistake is to budget every URL at the standard driver rate even when the target mix requires JavaScript or stealth. Source: Nimble pricing documentation, retrieved 2026-07-26.
What Nimble does not publish as one answer
- Public request-concurrency limits for the direct APIs. The managed-plan table publishes concurrent agents, which is a different limit. Source reviewed: Nimble pricing documentation, retrieved 2026-07-26.
- A fixed total rate for deep search, because underlying Extract or Agent usage depends on configuration. Source reviewed: Nimble pricing documentation, retrieved 2026-07-26.
- A domain-by-domain forecast of which automatic extraction driver will be selected before execution. Source reviewed: Nimble pricing documentation, retrieved 2026-07-26.
- A monthly purchase option for managed Data Services plans, which the public documentation says are billed annually. Source reviewed: Nimble pricing documentation, retrieved 2026-07-26.
Who it suits
Nimble suits teams that want successful-request billing and automatic escalation across static, JavaScript, and protected targets. It also suits buyers choosing between direct APIs and a managed pipeline. It is less suitable when procurement needs one fixed rate before the target mix is known, or when public concurrency limits are required for capacity planning. The reason is that success treatment is clear, but driver choice and deep-search composition still determine the effective unit cost. Sources: Nimble pricing documentation and Nimble, retrieved 2026-07-26.
Answer
Nimble's dated 2026-07-26 price snapshot gives $130.00 for 100,000 JavaScript-rendered pages on its Pay as you go 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.