Async full-site ingestion

Crawl an entire docs site

Building a RAG corpus or monitoring site? Crawl discovers pages, renders each one, and returns results via webhook when the job finishes.

Works with your agent stack

ClaudeCursorCodexVS CodeGeminin8n

Single-page extraction is the start. Crawl follows internal links up to your depth and page limits, processing each URL through the render chain.

Docs ingestion

Walk documentation trees and push Markdown into your vector store on completion.

Blog archives

Capture years of posts in one async job instead of scripting pagination yourself.

Crawl returns a job ID immediately. Pages render in the background with the same smart chain as single-url endpoints.

Depth and page caps

Control max_depth and max_pages so crawls stay bounded on large sites.

Include/exclude patterns

Regex filters skip admin paths and focus on the sections you care about.

1 credit per page

Pay per successful render. Failed pages do not burn credits.

01

Start crawl

POST seed URL with depth limits. Receive job_id.

View docs →
02

Webhook callback

Your server receives completion payload with URLs and extracted content.

Async mode →
03

Index Markdown

Chunk and embed crawl results into your vector database.

RAG use case →

Site crawl FAQs

Questions about async crawls and webhooks.

View docs
001Is crawl synchronous?

No. You get a job ID and results via webhook or polling when the job completes.

002Can I crawl only /docs paths?

Yes. Use include_pattern and exclude_pattern to scope the crawl.

003What format is each page?

Configure the crawl to extract Markdown, HTML, or screenshots per page depending on your pipeline.

Start crawling

Async site ingestion with webhooks and bounded depth.