Hanzo Crawl
Give it a URL, get back Markdown
It fetches the page, finds the part a person would actually read, and renders that as Markdown. Navigation, cookie banners and footers do not come with it. A page that needs JavaScript gets a real browser; everything else is a fetch and a parse, which is most of the web and far faster.
Three steps, and a boundary
Fetch, extract, render. Then the part that matters when the URL comes from a stranger.
The readable part, not the page
Deciding which subtree is the article is the hard problem, and it is the one this solves. You get the content and what the page says about itself, without the chrome around it.
A browser only when needed
Most pages are a fetch and a parse. Headless Chromium is a separate service it escalates to for the ones that genuinely need rendering, so you do not pay browser cost for a documentation page.
Markdown, and the metadata
Headings stay headings and links keep their targets, resolved against the page they came from. Title, description and canonical URL come back alongside — including the URL after redirects, which is the one worth citing.
It cannot be pointed at your cluster
The caller supplies the URL, which makes any crawler a request-forgery primitive. Loopback, link-local and multicast are refused — including the cloud metadata endpoint on 169.254.169.254 that hands out credentials.
Every redirect is checked too
Blocking the first address is not enough, because a public URL can redirect to a private one. The guard sits on the dialer, so a 302 toward metadata is refused at the hop that matters.
A tool an agent can call
It answers on MCP as well as over HTTP, so a model can read a page mid-conversation without you building the plumbing for it.
How it works
Each step is its own file and can be tested without the other two.
Fetch
One guarded HTTP request. The dialer refuses private and link-local addresses on every hop, so a URL that redirects somewhere it should not reach is stopped there rather than after the fact.
Extract
The document is reduced to the subtree a reader would call the content, plus the title, description and canonical URL the page claims for itself. If the HTML alone is not enough, this is where a headless browser gets involved.
Render
That subtree becomes Markdown with its structure intact — headings, lists, code and links, with relative URLs resolved against the page. It is the format a model reads best and a person can still diff.
Two ways to call it
Over HTTP at /v1/crawl when your code is doing the asking, or over MCP when a model is.
Pricing
You are paying for the hosted API and the browsers behind it, not for the code.
Build
- 50,000 pages/month
- 5 concurrent crawlers
- JavaScript rendering
- Markdown + structured output
- REST API access
Scale
- 500,000 pages/month
- 25 concurrent crawlers
- Priority JS rendering
- LLM-based extraction
- Direct Search + Vector integration
Enterprise
- Unlimited pages
- Unlimited concurrent crawlers
- Dedicated rendering pool
- Custom extraction schemas
- Dedicated support + SLA
The crawler is open source, and so is the headless-browser image it escalates to. Run both yourself for nothing. The plans buy you somebody else operating them.
Up to 5% of compute goes back to open source
Every deployment is SBOM-verified. Contributors to Crawl4AI earn a share of compute revenue — transparent, on-chain, and customizable by the community.
Send it a URL
One call, and the page comes back as Markdown.
From your code over HTTP, or from a model over MCP.