Home / Web scraping APIs / Context.dev
Context.dev pricing
100,000 JavaScript-rendered pages a month cost $99.00 on Context.dev's Pro plan, with room to grow to 125,000 pages on the same plan.
Checked Oct 12, 2026 on Context.dev's own pricing page
- Developer
- Pro
- Growth
- Scale
Your workloadPick a volume on the scale, 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.
Every Context.dev plan
| Plan | Covers | Billed monthly | Billed yearly, per month | Included | Past the allowance | Concurrent |
|---|---|---|---|---|---|---|
| Developer | 10K to 25K pages | $19.00 | $15.83saves 17% | 7,500 credits | $2.20 per 1,000 more | 10 |
| Pro fits your volume | 50K to 100K pages | $99.00 | $82.50saves 17% | 125,000 credits | $1.80 per 1,000 more | 100 |
| Growth | 250K to 500K pages | $299.00 | $249.17saves 17% | 500,000 credits | $1.40 per 1,000 more | 250 |
| Scale | 1M pages | $499.00 | $415.83saves 17% | 1,000,000 credits | $1.00 per 1,000 more | 500 |
Your job
What Context.dev bills you for
What you pay
Context.dev is also sold as one of the AI extraction APIs (100,000 AI extraction operations a month: $299.00 on Growth) and one of the web search APIs (100,000 standard searches a month: $99.00 on Pro).
About this price and its sources
Context.dev bills scraping, crawling and search from one credit balance: 1 credit a page with JavaScript rendering, anti-bot bypass and proxies included, from $19 a month.
Cite this price
100,000 JavaScript-rendered pages a month cost $99.00 on Context.dev's Pro plan, with room to grow to 125,000 pages on the same plan. Price read from https://www.context.dev/pricing on Oct 12, 2026. Scraping API Prices, https://scrapingapiprices.com/context-dev-pricing
How the bill builds up
- Base rate1 creditper page
- → JavaScript rendering1 creditper page; replaces the base rate
- × Premium proxyNot requiredNot part of this workload
- ÷ Success rate1Failed requests are not billed
- = Billed units per page you keep1 creditFrom this bill’s calculation
- = per 1,000 pages kept$0.99Pro, 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 · $99.00
Read the chart as a table
| Volume | Bill | Offer |
|---|---|---|
| 10,000 | $25.60 | Developer |
| 25,000 | $58.60 | Developer |
| 50,000 | $99.00 | Pro |
| 100,000 | $99.00 | Pro |
| 250,000 | $299.00 | Growth |
| 500,000 | $299.00 | Growth |
| 1,000,000 | $499.00 | Scale |
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
Context.dev does not bill failed fetches, so failures cost nothing here.
- × 1
What the meter counts
100,000 credits
One attempt is one billed unit for this workload.
- =
Cash per month
$99.00 /mo
Pro: 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 credits → Pro $99.00/mo = $0.99 per 1,000 pages kept
What makes it cost more
One page is not always one billed unit. These are Context.dev's published charges for each kind of work; failed requests are not billed.
| Work | Costs | Per | Source |
|---|---|---|---|
| A standard page | 1 credit | page | source |
| JavaScript rendering | 1 credit | page | source |
| Premium proxies | 1 credit | page | source |
| JavaScript rendering with premium proxies | 1 credit | page | source |
| A crawled page | 1 credit | page | source |
| AI extraction | 4 credits | page | source |
| A search | 1 credit | 10 results10 results a search by default | source |
Limits and terms
What Context.dev 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
- Concurrent requests per organization: Free 1, Developer 10, Pro 100, Growth 250, Scale 500. source
Credits, renewal and billing
- With insufficient credits and no available top-up, any plan returns 401 USAGE_EXCEEDED. source
- Upgrades apply immediately; downgrades apply at renewal. source
Other terms
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.
What Context.dev does not publish
- Whether unused monthly credits roll over.
- The top-up price for subscriptions started before the current rates: the page says existing subscriptions keep their rates.
What Context.dev is
Context.dev is a web data API for apps and AI agents: scrape, crawl, map and search endpoints that return Markdown or structured JSON, plus brand, style guide and people lookups, all drawn from one credit balance. Context Dev Inc. is a Delaware corporation (terms of service, checked Oct 12, 2026).
How billing works
A standard scrape costs 1 credit, and JavaScript rendering, anti-bot bypass and proxies are included in that price; browser actions raise it to 2 credits, and a successful JSON extraction adds 4, so a structured page costs 5. A crawl costs 1 credit a page, and web search 1 credit per 10 results. Plans run from Developer at $19 a month for 7,500 credits to Scale at $499 for 1,000,000, and paid plans can top up in 1,000-credit blocks at $2.20 on Developer down to $1.00 on Scale. Paying a year ahead saves two months. Most failed requests are not billed, but a 404 is billed at the request’s base price (Context.dev pricing, checked Oct 12, 2026).
Before you buy
Because rendering and proxies cost nothing extra, Context.dev’s price per page is the same for a plain page and a protected one, which is unusual: on Scrape.do and ScrapingDog a protected page costs 10 to 25 times a plain one. The page does not say whether unused credits roll over, and there is no one-off purchase: every route is a monthly or yearly plan. With no credits left and no top-up, requests return an error rather than an overage bill. The free plan gives 1,000 credits a month with one concurrent request and no card.
Who it suits
Context.dev suits teams whose targets mix plain and protected pages, since every page costs the same credit, and AI products that want Markdown, JSON and search from one key. A team scraping only plain pages at volume can pay less elsewhere; the calculator sets its bill for your job against every other scraping API.