01 / Clean output
Only the data you need.
Choose markdown, HTML, links, and metadata instead of building a parser for every site.
Product / Scrape
Turn any URL into clean data.
Extract markdown, HTML, links, and metadata from a page with one predictable request.
curl -X POST https://api.beecrawl.dev/scrape \
-H "X-Web-Extract-Api-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com","formats":["markdown","links"]}'Features // Product / Scrape
Make any page useful to an agent, whether it is static, dynamic, or full of noisy markup.
02 / Browser rendering
Handle modern pages.
Turn on browser rendering and wait for page content when a plain HTTP request is not enough.
03 / Stable interface
One request shape.
Use the same endpoint from cURL, Python, Node, or Rust as your sources change.
How it works //
From request
to ready data.
01
Pass a URL and formats.
02
Render and normalize the page.
03
Use structured content in your workflow.
{
"requestId": "req_01H...",
"status": "ready",
"data": "useful web content",
"metadata": { "provider": "beecrawl" }
}FAQ //
Everything you need
to get moving.
Which formats are supported?
BeeCrawl supports markdown, HTML, links, and page metadata through the scrape request.
When should I use browser rendering?
Use it for JavaScript-heavy pages or pages where the useful content appears after the initial document load.