Is there a free tier?

Yes. The page advertises a free tier with 500 credits and no credit card required.

How do API credits work?

The FAQ heading appears on the page, but the answer is not included in the supplied page text, so credit-to-call conversion and pricing per credit are not published.

Are there extra fees for JS rendering, anti-bot bypass, or premium proxies?

These are flagged as possible extras in the FAQ, but no per-request or flat fees are published on the page.

What are the rate limits, and how can I increase them?

Heading appears on the page; no published limits or upgrade path are included in the supplied text.

What's the difference between API credits and Logo Link?

Heading appears on the page; the supplied text shows Logo Link as a free, key-less CDN (logos.context.dev?domain=…) but does not contain the FAQ answer comparing it to API credits.

When should I talk to sales?

The page lists a 'Book a call' CTA for paid needs; the FAQ heading appears but the answer text is not in the supplied page copy.

Context.dev Pricing in 2026: Plans, Limits and Real Costs

Context.dev's pricing page only publishes a free tier with 500 credits and no credit card required. Paid plan names, prices, limits, and overage rates are not published on the page, and the FAQ refers buyers to sales for details.

Verified 2026-08-29 · official pricing page · Context.dev in the directory

Quick pricing verdict

Starting price: Not published on the pricing page. Only a free tier is shown.
Free plan: Yes. A free tier is advertised with 500 credits and no card required, with 10-minute integration.
Best plan for most people: Not published. The page does not name or price any paid tier.
Plan to avoid first: Not published. Only a free tier is visible on the page; the page directs paid buyers to book a call.
Biggest hidden cost: Not published. The FAQ flags possible extra fees for JS rendering, anti-bot bypass, and premium proxies, but lists no prices.
Pricing checked: 2026-08-29, against the official page

Context.dev's pricing page, as supplied, advertises a single visible offer: a free tier with 500 credits, no credit card required, and a stated 10-minute integration path for AI agents and developers. The page pitches one REST API covering scraping, crawling, sitemap discovery, brand extraction, screenshots, and transaction identification, and it lists integrations for Cursor, TypeScript, Python, Ruby, Go, PHP, and MCP.

Beyond the free tier, the page text does not publish plan names, prices, credit costs, rate limits, or overage behavior. Paid-buyer FAQs such as 'Which plan should I choose?', 'Do you offer annual billing?', 'Am I billed for failed requests?', and 'What happens when my API credits run out?' appear as headings with no answers shown, and the page routes buyers to 'Book a call' for anything that needs a number.

Plans compared

Plan	Price	Best for	Key limits
Free	$0	Trying the API and small pilots that fit within 500 credits, with no credit card needed.	500 credits advertised on the page; specific per-endpoint usage, rate limits, and what counts as one credit are not published.

Source: Context.dev pricing page, checked 2026-08-29.

What each plan includes

Free

Includes: Access to the same API covering web scraping (markdown, HTML, sitemap, full-site crawls), brand data extraction, Logo Link CDN, image and screenshot APIs, classification lookups, and structured extraction via Zod or JSON Schema, with SDKs for TypeScript, Python, Ruby, Go, PHP, and MCP, and integrations for Cursor and Zapier-style tools.
Missing: Any published numbers for paid tiers, credit cost per call, monthly or annual pricing, rate limits, the price of failed requests, and the behavior when credits run out. The page points these questions at a sales call.
Avoid if: You need a published price, a public rate limit, or a clear overage policy before you can build a forecast — none of those are on this page.
Verdict: The only tier a solo founder can price out without talking to sales. Useful for evaluation; unusable as a budgeting input for production.

Add-ons, overages, and surprise costs

Cost item	Trigger	Published amount	Billing behaviour
JS rendering	Scraping or crawling pages that require JavaScript execution, if this is treated as an add-on.	Not published	Flagged in the FAQ as a possible extra fee, with no price or threshold given on the page.
Anti-bot bypass	Requests that need to clear bot-detection or CAPTCHA on target sites.	Not published	Listed in the FAQ as a potential extra; the page gives no per-request or flat fee.
Premium proxies	Use of premium proxy infrastructure for hard-to-scrape targets.	Not published	Mentioned in the FAQ alongside JS rendering and anti-bot bypass; no pricing structure disclosed.
Credit replenishment above the free 500	Continued API use after the free credits are used, or any paid plan.	Not published	The FAQ asks 'What happens when my API credits run out?' but the page text does not publish the answer.

Source: Platform pricing docs, checked 2026-08-29.

Which plan should you choose?

Solo founder evaluating Context.dev before committing budget: Free — It is the only tier with published numbers on the page (500 credits, no card), and the page explicitly markets a 10-minute integration path.
Team that needs a published paid price, rate limit, or annual figure: Book a call — The page text does not publish paid-tier pricing, rate limits, annual billing terms, failed-request billing, or overage behavior, so a sales call is the only path to a budget number.
Founder who only needs company or brand logos: Free via Logo Link CDN — The page shows a free <img>-tag logo embed at logos.context.dev?domain=… with no API call, no SDK, and no backend, separate from the main API credit system.
Founder building agent-driven signup or onboarding enrichment: Free for the prototype, then sales — The page showcases the autofill, brand-kit, and enrichment use cases on the free tier, but production volume will exceed 500 credits and paid terms are not published.

Frequently asked questions

Is there a free tier?: Yes. The page advertises a free tier with 500 credits and no credit card required.
How do API credits work?: The FAQ heading appears on the page, but the answer is not included in the supplied page text, so credit-to-call conversion and pricing per credit are not published.
Which plan should I choose?: Heading appears on the page; the answer is not in the supplied text. Only the free tier is priced.
Are there extra fees for JS rendering, anti-bot bypass, or premium proxies?: These are flagged as possible extras in the FAQ, but no per-request or flat fees are published on the page.
What are the rate limits, and how can I increase them?: Heading appears on the page; no published limits or upgrade path are included in the supplied text.
Do you offer annual billing?: The page asks the question but does not publish whether annual billing is offered or any annual price in the supplied text.
Am I billed for failed requests?: The page asks the question but does not publish the policy in the supplied text.
What happens when my API credits run out?: The page asks the question but does not publish the behavior in the supplied text.
What's the difference between API credits and Logo Link?: Heading appears on the page; the supplied text shows Logo Link as a free, key-less <img> CDN (logos.context.dev?domain=…) but does not contain the FAQ answer comparing it to API credits.
When should I talk to sales?: The page lists a 'Book a call' CTA for paid needs; the FAQ heading appears but the answer text is not in the supplied page copy.

What we read

Every figure on this page was extracted from the vendor's own pricing page at the moment below. The text is reproduced so you can check our reading against what they publish today.

Source captured 2026-08-29 08:21 UTC

New: Monitors. Watch any website for changes → Context.dev Features Use Cases Customers Pricing Docs Web Scraping API markdown, HTML, sitemap, search, full-site crawls Extract structured data from any site via JSON schema Brand Data logos, colors, fonts, styleguide, description, socials, address Logo Link logo CDN Pull Images images, logos, and screenshots from any URL Classification NAICS, SIC, transaction identification AI & agents Power LLMs with Web Context Power Generative AI Ground RAG in Fresh Content Monitor Websites for Changes Product & brand experiences Autofill Onboarding Programmatic Theming Automated Brand Kits Enrich Company Profiles Featured stories Mintlify How Mintlify used Context.dev to power a tool that transforms any GitHub repo URL into a complete, branded documentation site — and got there in under 10 minutes of integration time. Read more SiteGPT SiteGPT, the AI chatbot platform for customer support, switched from Firecrawl to Context.dev to scrape entire websites and turn them into the knowledge base behind its customers' bots. The migration took under a day. Read more Sourcely Sourcely uses Context.dev to crawl academic journals and PDFs at scale with a web crawling API its team found fast, accurate, and higher quality than the alternatives. Read more View all stories Book a Call Sign Up Backed by Combinator The web context {API} for teams building software and AI agents One API, every piece of web context your agent needs. Extract Markdown Brand Images Sitemap Styleguide Screenshot +5 https:// or get an API key free. 500, no card required Powering products and agents at From maintaining data infrastructure to shipping product features Before After Feeding agents knowledge frozen at the model's cutoff Pull live web data the moment your product needs it Building crawlers, scrapers, and pipelines internally Access web, brand, and company data through APIs Maintaining infrastructure that isn't part of your product Let Context.dev handle the data infrastructure layer Combining multiple vendors to fill data gaps Replace multiple vendors with a single platform Spending weeks collecting data before building features Start building features sooner AGENTIC SETUP Set it up your way. Do it yourself in the dashboard, or let your AI agent handle the whole thing. Do it yourself 1. Sign up and verify your email. 2. Copy your API key from the dashboard. 3. Install the SDK and start calling the API. Get API Key Let your agent do it RECOMMENDED Paste one line into your coding agent — it signs you up, grabs your key, and integrates Context.dev for you. agent setup Signup for an account & get API key with context.dev/auth.md, then follow docs.context.dev/agent-quickstart to integrate into the codebase Copy Agent Setup FOR AI NATIVE PRODUCTS The {APIs} powering your next feature Scrape any URL, crawl an entire website, and extract structured data in seconds: markdown, HTML, sitemaps, screenshots, and brand intelligence. Extract Crawl any site and extract structured data into a JSON Schema you define. Scrape web content Scrape any URL, or crawl an entire site, for clean markdown, rendered HTML, or extracted images. Extract site map Crawl and discover all page URLs from any domain via sitemap. Retrieve brand data Resolve a full brand profile by company identifier, or extract details from one specific page URL. Extract styleguide Get the complete visual identity: colors, elements, and fonts from any website. Get products Extract product listings or individual product details with AI. Capture screenshots Generate high-quality viewport or full-page screenshots of any website. Identify transaction Match transaction strings to brands with optional location and MCC hints. Extract Try in Cursor import ContextDev from 'context.dev'; import { z } from 'zod'; const contextDevClient = new ContextDev({ apiKey: process.env['CONTEXT_DEV_API_KEY'] }); // Define the exact shape Context.dev should extract from the page. const schema = z.ob

Pricing change log

What moved since we started tracking this page, newest first. A price that changes silently is the failure mode of every other pricing guide.

2026-08-29First published, extracted from https://www.context.dev/?dub_id=pHeYBuRuJNWzgg31/pricing.