Skip to main content
Context.dev is a web scraping and extraction API. Send a URL, get clean Markdown, rendered HTML, a screenshot, or structured JSON matching a schema you define. Send a domain, get a typed brand profile, design system, or industry classification. Every response is typed JSON (or plain Markdown you keep), served from https://api.context.dev/v1 with a Authorization: Bearer ctxt_secret_... header.

​
Context Reference

Context.dev APIs can give you these outputs.

​
Context.dev APIs

There are 4 product categories:
Render, crawl, screenshot, and extract structured data from any URL. Bot detection bypass and proxy escalation are automatic.

Crawl Websites

Get clean markdown for reachable pages on a website

Scrape Markdown

Get clean markdown with nav and ads stripped, ready for LLMs.

Capture Webpage Screenshot

Get full-page or custom viewport size screenshot of a webpage.

Extract Product

Get structured data about the products on a website

Extract Structured Data

Describe the data you want as a JSON Schema and get a typed JSON answer extracted from a website’s pages.

​
Features

  • Free plan, no credit card needed. Personal-email signups receive 250 one-time API credits; work-email signups receive 500. Every Free account also receives 10K one-time Logo Link credits.
  • Simple, credit-based pricing with a subscription. Every API call costs a fixed number of credits. Plans come with generous and clear rate limits.
  • Simple APIs and SDKs built for developers. Consistent authentication and response shapes for every endpoint.
  • Typed responses. Every endpoint returns typed JSON output, so you won’t need to parse responses.
  • Bot detection bypass on every plan at no extra cost. Automatic proxy escalation for webpage crawling on every plan.

​
Reliability

  • Warm-cache hits avoid crawl work. They are generally faster than first-time retrievals.
  • Cold hits may run a full crawl through a specialized pipeline and can take materially longer, up to the five-minute platform timeout. Use prefetch to move cold work ahead of a user-facing request, and choose timeoutMS for your latency budget.

​
Deployment and data portability

Context.dev is a hosted API — there is no self-hosted edition to operate, patch, or scale. What keeps you portable:
  • You keep every byte. Responses are plain Markdown and standard JSON delivered to you per request. Store them wherever you want; nothing lives only inside Context.dev.
  • Standard formats, no proprietary schema. Structured extraction uses JSON Schema you define, classifications use official NAICS/SIC/EIC codes, and assets are plain PNG/SVG files. Swapping providers means changing an HTTP call, not migrating data.
  • Zero Data Retention is available as an opt-in mode on scraping and parsing endpoints for sensitive workloads.
  • API stability policy documents how the API is versioned and how deprecations are announced.

​
Ways to use Context.dev

SDKs

Official SDKs for TypeScript, Python, Ruby, Go, and PHP. One bearer-token header, fully typed responses.

REST API

Call any endpoint directly over HTTPS with a bearer token. No SDK required.

MCP server

Give Claude, Cursor, VS Code, and any MCP-compatible agent direct access to Context.dev.

No-code

Drop brand and web data into Zapier, Make, Google Sheets, and Excel.

​
Next steps

Quickstart

Install an SDK and make your first call in two steps.

Agent Quickstart

Set up an AI agent to call Context.dev correctly.