GitHub-flavored markdown
Standard GFM with headings, links, tables, and fenced code blocks, ready to render or chunk.
POST /v1/scrape
Convert any URL into clean GitHub-flavored markdown with one call.
Built for RAG pipelines and agents that need readable context, not raw DOM. Send a URL, get back GitHub-flavored markdown stripped of nav, ads, and boilerplate, with headings, links, tables, and code blocks preserved. Built in Rust, returns static pages in around 118ms, and handles JavaScript rendering and bot protection automatically.
Standard GFM with headings, links, tables, and fenced code blocks, ready to render or chunk.
Nav, ads, footers, and sidebars are removed so only the real content survives the conversion.
Clean markdown drops roughly 90% of the tokens you would spend parsing raw HTML.
Tables stay tables, code stays in code blocks, and link text keeps its targets intact.
01
POST the page URL with formats set to markdown and your Bearer key.
02
We load the page, running JavaScript and clearing bot protection when the site needs it.
03
The HTML is reduced to main content and rewritten as clean GitHub-flavored markdown.
04
You get the markdown string plus page metadata in a single JSON response.
Turn any website into LLM-ready markdown, JSON, or structured data. Handles protected sites and returns static pages in around 118ms.
POST the URL to /v1/scrape with formats set to markdown. You get back clean GitHub-flavored markdown plus page metadata, with nav, ads, and boilerplate already stripped out.
GitHub-flavored markdown. Headings, links, ordered and unordered lists, tables, and fenced code blocks are all preserved so the output renders correctly and chunks cleanly for RAG.
Yes. Clean markdown carries the same content with roughly 90% fewer tokens than raw HTML, so you spend less context, cut cost, and give the model far less noise to reason over.
Yes. JavaScript rendering and bot protection are handled automatically. You send the same request and get markdown back, whether the page is static or heavily defended.
No. Credits are only consumed on successful responses. A standard page is 1 credit; heavier work like JS rendering or protected-site access costs a few extra credits.
One credit pool, every endpoint. Cancel anytime, or self-host the open-source core for free.
Cookies & analytics
We'd like to use analytics to understand how this site is used. Nothing loads or fires until you agree. See our privacy policy for the full list of processors.