Render any page. One call, fresh browser.
Send a URL, get the page as a real browser sees it — hydrated HTML, markdown, the result of your own JavaScript, or a screenshot. Click, type, and scroll before capture. Every call is a fresh browser and nothing is kept between calls — not a server farm you have to run.
Need click, type, and scroll steps across many URLs? See browser automation. Just need one page fetched? Use the scraping API.
The headless browser primitive, without the server fleet.
Every call is a fresh browser
Each request starts a clean headless browser, does its work, and throws the browser away. Cookies, localStorage, and cache are not kept between calls, so there is nothing to open, keep alive, or clean up — and no state leaking from one request into the next.
Stealth and fallback built in
Scrape calls run in stealth mode by default, and you can opt into captcha solving with solve_captcha. Renders that get blocked escalate through fallback tiers automatically, and the response tells you which tier served it in tier_used.
Render JavaScript, get clean HTML
Point the API at a URL and it executes the page's JavaScript, waits for load or network idle, and returns rendered HTML, markdown, text, or links. Evaluate your own JavaScript expression in the page with js_eval and get the value back in eval_result.
No browser farm to run
No idle Chromium pool, no autoscaling to tune, no out-of-memory crashes at 3 a.m. Send a request, get the page back. Render and scrape cost 1 credit each (JavaScript rendering adds nothing), screenshots cost 3, and failed calls are refunded.
Render, evaluate, act, capture.
Four independent calls, one bearer token. Each starts a fresh browser; nothing carries over to the next.
# Render a URL in a fresh headless browser. JavaScript runs; you get the hydrated HTML.
curl -X POST https://api.ollagraph.com/v1/render \
-H "Authorization: Bearer $OLLAGRAPH_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://example.com/app"}'
# => { "status": "success", "url": "...", "final_url": "...",
# "html": "<!doctype html>...", "tier_used": "...", "status_code": 200 } # Wait for the network to settle, return markdown, and evaluate a JS expression.
curl -X POST https://api.ollagraph.com/v1/scrape \
-H "Authorization: Bearer $OLLAGRAPH_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/dashboard",
"wait_until": "networkidle0",
"format": "markdown",
"js_eval": "document.querySelectorAll(\"article\").length"
}'
# => { "status": "success", "url": "...", "format": "markdown", "content": "...",
# "eval_result": "24", "time_ms": 2310, "fallback": false } # Run page actions on the loaded page before it is captured — click, type, scroll.
curl -X POST https://api.ollagraph.com/v1/scrape \
-H "Authorization: Bearer $OLLAGRAPH_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/reports",
"format": "html",
"actions": [
{"action": "type", "selector": "input[name=filter]", "text": "2026"},
{"action": "click", "selector": "#load-report"},
{"action": "scroll_to_bottom"}
]
}'
# Actions run once, in order, then the page is captured. They don't wait for a
# navigation, so use them for in-page interactions, not multi-page flows. # Capture a full-page screenshot. Raw PNG bytes by default.
curl -X POST https://api.ollagraph.com/v1/screenshot \
-H "Authorization: Bearer $OLLAGRAPH_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/dashboard",
"full_page": true,
"wait_until": "networkidle0",
"device_scale_factor": 2
}' -o dashboard.png
# Pass "output": "json" instead to get
# { "status", "url", "final_url", "content_type", "bytes", "image_base64" } Part of the full 123-endpoint surface. For one-shot fetches see scraping, for whole-site sweeps see crawling, and for page actions at scale see automation.
Headless browser questions
1 How is the browser surface different from the scraping API?
How is the browser surface different from the scraping API?
2 How is this different from browser automation?
How is this different from browser automation?
3 Which endpoints make up the browser surface?
Which endpoints make up the browser surface?
4 How is it billed?
How is it billed?
5 Is any state kept between calls?
Is any state kept between calls?
6 What page actions are supported?
What page actions are supported?
7 What about pages behind a login?
What about pages behind a login?
8 Can I run a multi-step interaction across several calls?
Can I run a multi-step interaction across several calls?
Render your first page in five minutes.
1,000 free credits, one bearer token, no browser to run, failed calls auto-refund.