Home / Web scraping APIs / Nimble
Nimble pricing
100,000 JavaScript-rendered pages a month cost $100.00, pay as you go, on Nimble.
Checked Oct 12, 2026 on Nimble's own pricing page
- Pay as you go
Your workloadType an exact volume, change the success rate or copy a link to this jobEdit
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.
The Nimble plans from 10K to 1M
| Plan | Covers | Billed monthly | Billed yearly, per month | Included | Concurrent |
|---|---|---|---|---|---|
| Pay as you go fits your volume | 10K to 1M pages | not published | not offered | pay per use | not published |
All 4 Nimble plans, with what each charges past its allowance, are further down.
Your job
What Nimble bills you for
What you pay
Every Nimble plan
| Plan | Billed monthly | Billed yearly, per month | Included | Past the allowance | Concurrent requests |
|---|---|---|---|---|---|
| Pay as you go fits your volume | not published | not offered | pay per use | not published | not published |
| Data Services Startup | yearly only | $2,500.00 | 350,000 pages | move to a bigger plan | not published |
| Data Services Scale | yearly only | $7,000.00 | 1,200,000 pages | move to a bigger plan | not published |
| Data Services Professional | yearly only | $15,000.00 | 3,000,000 pages | move to a bigger plan | not published |
Nimble is also sold as one of the web search APIs (100,000 standard searches a month: $110.00, pay as you go on Pay as you go) and one of the AI extraction APIs (100,000 AI extraction operations a month: no public price).
About this price and its sources
How Nimble selects extraction drivers and bills successful URLs, what remains workload-dependent, and which teams fit.
Cite this price
100,000 JavaScript-rendered pages a month cost $100.00, pay as you go, on Nimble. Price read from https://docs.nimbleway.com/nimble-sdk/admin/pricing on Oct 12, 2026. Scraping API Prices, https://scrapingapiprices.com/nimble-pricing
How the bill builds up
- Base rate$0.001per page
- × JavaScript renderingNot publishedSee the stated assumption in the calculation
- × Premium proxyNot requiredNot part of this workload
- ÷ Success rate1Failed requests are not billed
- = Billed units per page you keep1 pageFrom this bill’s calculation
- = per 1,000 pages kept$1.00Pay as you go, billed monthly
Credits and multipliers
JavaScript rendering
Billed failures
Success rate
Concurrency
Free tier
Renews monthly The bill at your volume
100,000 pages per month · $100.00
Read the chart as a table
| Volume | Bill | Offer |
|---|---|---|
| 10,000 | $10.00 | Pay as you go |
| 25,000 | $25.00 | Pay as you go |
| 50,000 | $50.00 | Pay as you go |
| 100,000 | $100.00 | Pay as you go |
| 250,000 | $250.00 | Pay as you go |
| 500,000 | $500.00 | Pay as you go |
| 1,000,000 | $1,000.00 | Pay as you go |
Follow each billed unit
-
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 pages
One attempt is one billed unit for this workload.
- =
Metered cash this month
$100.00 /mo
Pay as you go: the cheapest way to buy this volume, not just the first plan big enough.
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 pages → Pay as you go $100.00/mo = $1.00 per 1,000 pages kept
What makes it cost more
One page is not always one billed unit. These are Nimble's published charges for each kind of work; failed requests are not billed.
| Work | Costs | Per | Source |
|---|---|---|---|
| A standard page | $0.001 | page | source |
| A search | $0.0011 | search | source |
| A deep search | $0.005 | search | source |
| Residential proxy traffic | $5.3 | GB | source |
Limits and terms
What Nimble publishes beyond the price: the limits a job runs into and the terms that change what a plan is worth. Each line links the page it comes from and the day it was read.
Speed, concurrency and sessions
- Managed plan limits are 5 agents on Startup, 10 on Scale, and 20 on Professional; these are not stated as request-concurrency limits. source, read Jul 26, 2026
What you may do with the results, and how long they are kept
- Data retention is 7 days on Startup, 30 days on Scale, and 90 days on Professional. source, read Jul 26, 2026
Credits, renewal and billing
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. APIs without a full public price aren't ranked. Showing 6 of 11; see the rest.
What Nimble does not publish
- No public request-concurrency limits were published.
- Nimble's page no longer lists its VX6, VX8 and VX10 difficulty levels, so there is no longer a separate rate for a JavaScript-rendered or stealth extraction.
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, checked Jul 26, 2026.
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, checked Jul 26, 2026.
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 (Nimble pricing documentation, Jul 26, 2026).
- A fixed total rate for deep search, because underlying Extract or Agent usage depends on configuration (Nimble pricing documentation, Jul 26, 2026).
- A domain-by-domain forecast of which automatic extraction driver will be selected before execution (Nimble pricing documentation, Jul 26, 2026).
- A monthly purchase option for managed Data Services plans, which the public documentation says are billed annually (Nimble pricing documentation, Jul 26, 2026).
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, checked Jul 26, 2026.
Nimble head to head
Both bills for the same job, and the volume where the cheaper one changes.