Record it once.
Replay it as an API.
Some data lives behind a click, a login, or a next-page button. SmartBrowse lets you record that path once in a real browser — a recipe — then dispatch it as an API call whenever you need fresh data.
- Record clicks, logins & pagination visually
- Replay any recipe as a single API call
- 2 credits per page, charged on success only
Author in the studio. Replay over HTTP.
Recording happens visually in the dashboard studio. Once a recipe is saved, it has a run endpoint you can call from anywhere.
Record a recipe
Click through the page in the live studio browser. SmartBrowse captures the fields and actions and saves a reusable recipe.
Replay via API
Dispatch a run against the saved recipe. It returns a run_id straight away; poll for the merged result or wait for the webhook.
# replay a saved recipe — returns a run_id at once curl -X POST \ https://api.webscrape.ai/v1/smartbrowse/recipes/m3Yc2tFvN8q/run \ -H "X-API-Key: $WSG_KEY" # then poll for the result curl https://api.webscrape.ai/v1/smartbrowse/runs/k7Xb9dRmQ2p \ -H "X-API-Key: $WSG_KEY"
// dispatch returns a run to poll { "status": "queued", "data": { "run_id": "k7Xb9dRmQ2p", "recipe_id": "m3Yc2tFvN8q", "run_status": "running", "poll_url": "/v1/smartbrowse/runs/k7Xb9dRmQ2p", "created_at": "2026-07-06T12:00:00Z" }, "request_id": "req_aB3xY9Kp" }
Interaction, captured and repeatable
Everything a headless-browser script does — minus the script, the drift, and the maintenance.
Record, don’t script
Author a recipe by clicking through the page in a live browser. SmartBrowse synthesizes the selectors from what you picked — you never hand-write one.
Replay as an API
Every saved recipe gets a run endpoint. POST to it, get a run_id back immediately, then poll for the result. Same recipe, any time.
A real browser per run
Each run drives a fresh, real Chrome — full JavaScript and real rendering — so a recipe behaves exactly as it did while you were recording it.
Pagination & action chains
Recipes follow next-page links and replay your recorded action chain, collecting items across every page into one merged result.
Drift-tolerant replay
Replay is CSS-first with a structural fallback, so a recipe keeps returning data even when the page shifts underneath it.
Schedules & webhooks
Attach a cron schedule to any recipe and have results delivered to your webhook on completion — no polling loop to babysit.
Not sure you need a browser?
Record your first recipe.
Sign up free and open the studio — 500 credits on the house, no card required.