Crawl the web. Every page, clean Markdown.
Web crawling without running a crawler. Send one URL and Context.dev follows the links, renders JavaScript, gets past bot walls, and returns every page as LLM-ready Markdown.
POST /v1/batch/submit
Teams crawling the web with Context.dev
SiteGPTHyperspell
SourcelySoria
Construct
Adapt
“Context.dev was stupidly easy to drop in and replace that whole setup. The API makes sense, the docs are actually useful, and we got it working fast.”
- for SiteGPT to move its website crawling off Firecrawl
- < 1 day
- replaced Hyperspell’s waterfall of fallback crawlers
- 1 API
One URL in. The whole site out.
Submit a start URL as a batch with a page cap, a depth, and a URL pattern. Context.dev crawls up to 100,000 pages in the background, then you read every page as Markdown.
- 1SubmitA start URL, a page cap, and a URL pattern
- 2CrawlRendered in a real browser, in the background
- 3ReadMarkdown and metadata for every page
What teams crawl with Context.dev.
Crawl jobs our customers run in production, from support bots to research corpora.
Support chatbot knowledge bases
Crawl a customer’s help center and docs, then train their bot on clean Markdown.
SiteGPTCompany brains for AI agents
Bring public website content in next to Slack, email, and Drive as one source of truth.
HyperspellAcademic journals and PDFs
Crawl journal sites and PDFs at scale into text a research product can cite.
SourcelySearch connectors and agent tools
Give an agent one connector for search, crawling, and reading pages.
ConstructHealthcare and public data pages
Re-crawl the sources a terminal depends on without running scrapers on AWS.
Soria
Skip the crawler you’d have to maintain.
Everything a homegrown web crawler needs before it returns a usable page, and what Context.dev does instead.
| Your own crawlerbuild and maintain | Context.devone API key | |
|---|---|---|
| JavaScript-heavy pages | Run and scale a fleet of headless browsers | Every page rendered in a real browser |
| Bot protection | Buy proxies, rotate them, and write retry logic | Automatic proxy escalation and retries |
| Clean output | Write HTML-to-Markdown cleanup for every site | Markdown with the main content only |
| Large sites | Build queues and workers to fan out | Up to 100,000 pages per batch crawl |
| Cost | Servers, proxies, and engineering time | 1 credit per page, failed pages are free |
Crawling in production, in their words.
All customer storiesWeb crawling, answered.
More details in the API documentation.
What is web crawling?
Web crawling means starting from one URL and following links to discover and download every page of a site. Context.dev runs the crawl for you, renders each page in a real browser, and returns clean Markdown instead of raw HTML.
What’s the difference between web crawling and web scraping?
Web scraping extracts content from a page whose URL you already have. Web crawling discovers the pages first by following links from a starting URL, then scrapes each one. Context.dev does both: Scrape for a single URL, Crawl for a whole site.
How do I crawl an entire website?
Submit a crawl batch to /v1/batch/submit with the starting URL and an optional maxUrls, maxDepth, and regex. The crawler follows same-domain links and renders each page in the background, up to 100,000 pages. Poll the batch or receive a webhook, then read each page’s Markdown from the results.
How much does it cost to crawl a website?
1 credit per successfully crawled page. Failed pages are not billed. The free plan includes 1,000 credits every month, enough for 1,000 pages.
Can I crawl subdomains?
By default the crawler stays on the starting domain and treats www and the apex as the same site. Set followSubdomains to true to include subdomains such as docs.example.com.
Crawl your first site today.
1,000 free credits every month, enough for 1,000 crawled pages. No credit card required.



