Drive a browser with JSON steps.
Send a URL and a list of page actions — click, type, scroll — and get the page back after they run, as markdown, HTML, or the result of your own JavaScript. Every call is a fresh browser and nothing is kept between calls. Scale it with batch and async jobs, without a single line of Playwright.
For single-page extraction see the scraping API; for rendering and screenshots see the browser API.
Explicit actions, fresh browsers, zero browser ops.
Explicit page actions
Describe the steps as JSON: click a selector, type into a field, scroll to the bottom. Up to 50 actions run in order on the loaded page before it is captured, so the same request runs the same steps every time. No browser code to write.
A fresh browser every call
Each request gets a clean headless browser that is discarded when the call ends. No cookies, storage, or logged-in state carry from one call to the next — nothing to keep alive, nothing to reap, no state leaking between jobs.
Read the page with your own JS
Pass js_eval with any JavaScript expression and its value comes back in eval_result. Wrap it in JSON.stringify to pull a list of names, prices, or links out of the rendered DOM and parse it on your side.
No Playwright fleet to run
There is no headless Chrome to deploy, no browser pool to scale, no stealth tuning — scrape calls run in stealth mode by default. Run the same actions over many URLs with batch requests, or queue async jobs that post results to your webhook.
Drive it five ways.
Page actions, JavaScript evaluation, element screenshots, batch runs, and async jobs with a webhook.
# Click, type, and scroll on the loaded page, then capture it. One call, one fresh browser.
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/catalog",
"format": "markdown",
"wait_until": "networkidle0",
"actions": [
{"action": "click", "selector": "button.load-more"},
{"action": "click", "selector": "button.load-more"},
{"action": "scroll_to_bottom"}
]
}'
# => { "status": "success", "url": "...", "format": "markdown",
# "content": "...", "time_ms": 3120, "fallback": false } # Act on the page, then read it with your own JavaScript.
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/catalog",
"actions": [
{"action": "type", "selector": "input[name=filter]", "text": "wireless headphones"},
{"action": "scroll_to_bottom"}
],
"js_eval": "JSON.stringify([...document.querySelectorAll(\".product h2\")].map(e => e.textContent.trim()))"
}'
# eval_result comes back as a string — parse it in your code:
# -> { "status": "success", ..., "eval_result": "[\"Model A\",\"Model B\"]" } # Wait for an element to appear, then screenshot just that element.
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/pricing",
"wait_for_selector": "#pricing-table",
"selector": "#pricing-table",
"format": "png",
"output": "json"
}'
# -> { "status": "success", "url": "...", "final_url": "...",
# "content_type": "image/png", "bytes": 48213, "image_base64": "..." } # Run the same actions across many URLs in one request.
curl -X POST https://api.ollagraph.com/v1/scrape/batch \
-H "Authorization: Bearer $OLLAGRAPH_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"urls": [
"https://example.com/catalog?page=1",
"https://example.com/catalog?page=2",
"https://example.com/catalog?page=3"
],
"concurrency": 3,
"format": "markdown",
"actions": [
{"action": "click", "selector": "button.load-more"},
{"action": "scroll_to_bottom"}
]
}' # Queue a scrape and get the result posted to your webhook.
curl -X POST https://api.ollagraph.com/v1/scrape/async \
-H "Authorization: Bearer $OLLAGRAPH_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/catalog",
"webhook_url": "https://your-app.example/hooks/ollagraph",
"format": "markdown",
"actions": [{"action": "scroll_to_bottom"}]
}'
# -> { "status": "queued", "job_id": "..." } Flows that ship today.
Common patterns — each is one or two readable calls.
Load everything, then read it
Click the load-more button a few times, scroll_to_bottom, and get the fully expanded page back as markdown. One scrape call, one fresh browser.
Pull structured data with JS
Add a js_eval expression that JSON.stringify-s the product cards on the rendered page, then parse eval_result in your code into name, price, and URL fields.
Filter a client-side list
Type into an in-page filter box and click apply before capture. Works for interactions that update the page in place — actions don't wait for a navigation to a new page.
Same steps across many URLs
Send a list of URLs to /v1/scrape/batch with one actions array and a concurrency limit. Each URL runs in its own fresh browser.
Fire and forget with a webhook
Queue a scrape with /v1/scrape/async and a webhook_url. You get a job_id immediately and the result is posted to your endpoint when it finishes.
Visual check of the result
Use /v1/screenshot with wait_for_selector and selector to capture just the element you care about, as PNG or JPEG, for visual diffs or reports.
Browse all recipes, or wire results to your stack with webhooks.
Automation questions
1 What is the difference between this, the scraping API, and the browser API?
What is the difference between this, the scraping API, and the browser API?
2 Do I need to write CSS selectors?
Do I need to write CSS selectors?
3 Is there a natural-language or AI agent mode?
Is there a natural-language or AI agent mode?
4 Are sessions persistent across calls?
Are sessions persistent across calls?
5 What happens if an action navigates to a new page?
What happens if an action navigates to a new page?
6 Which actions are supported?
Which actions are supported?
7 How do I get structured data out?
How do I get structured data out?
8 Can I run the same actions on many pages?
Can I run the same actions on many pages?
9 How is this billed?
How is this billed?
Skip the headless-browser fleet.
1,000 free credits, one bearer token, failed calls auto-refund. A scrape call costs 1 credit, with JavaScript rendering and page actions included.