Context.dev

One web context API for software and AI agents

A single API for scraping pages to LLM-ready markdown, crawling sites, web search, structured extraction and brand data — billed from one credit pool instead of five vendors.

Screenshot of the Context.dev homepage

Context.dev collapses a stack most teams assemble themselves. Scraping a page to clean markdown, crawling a site, running a web search, extracting typed fields, pulling a company’s logo and colours, resolving it to an industry code, watching a URL for change — those are usually six vendors, six keys and six invoices. Here they are one API drawing on one credit pool.

The output is shaped for what people actually do with it. A scrape returns markdown with the navigation and cookie furniture already gone, which is the form a prompt or a RAG index wants; the Brand API returns several marks per company tagged light, dark and opaque-background, which is what you need when you’re drawing them onto a surface whose colour you control. The no-code integrations — Make, Zapier, Sheets, Excel — mean the brand and enrichment calls are reachable by people who were never going to write a client.

The credit model is the thing to think about before committing. One pool across six products is simpler to buy and harder to forecast: a month heavy on crawling and a month heavy on brand retrieval spend at very different rates, and the free plan stops dead at 500 credits rather than throttling. The ladder itself is reasonable — $25 for 10K credits, $149 for 200K, $499 for 1M, with overage getting cheaper as you climb — but SSO, custom limits and the 99.9% SLA don’t appear until Enterprise.

Features

Scrape to LLM-ready markdown

A URL in, clean markdown out — boilerplate stripped, ready to drop into a prompt or a RAG index without a parsing step of your own.

Crawl and web search

Walk a whole site or run a search from the same API, so discovery and retrieval don't come from two different vendors with two different bills.

Structured extraction

Pull typed fields off a page, including a product-specific endpoint for catalogue data, instead of writing a selector per site.

Brand API

Retrieve a company's logos, colours, fonts and metadata from its domain — several marks per brand, tagged light, dark or opaque-background.

Classification API

Resolve a company to NAICS and SIC industry codes, which is the join key most enrichment pipelines are missing.

Page monitoring

Watch URLs for change and get told when they move, with concurrency scaling by plan rather than a separate uptime product.

Use cases

  • Feeding an agent clean page text without maintaining a scraping fleet
  • Building a RAG index from a documentation site in one crawl
  • Pulling logos and brand colours for a directory, CRM or partner page
  • Enriching a lead list with industry codes from nothing but a domain
  • Watching competitor pricing pages and reacting when they change
  • Replacing a stack of single-purpose API subscriptions with one credit pool

Compare Context.dev head to head

Side-by-side comparisons, on pricing, platforms and where each one wins.

Looking for something similar?

Other data & analytics tools worth comparing against Context.dev.