Agents
An agent opens a real browser, works through the site and reports back. Watch it live and take over any time. About 15 credits a minute, about $0.07 to $0.08.
1,000 free credits every month. No card needed.
How it works
Ask in a sentence.
Say what you want done, the way you would ask a person. Name the fields you want back, and the answer comes back in exactly that shape.
You get an id straight away.
A run is a job, not a call you hold open: the id comes back in milliseconds, and the run takes seconds, minutes or hours, as the task needs.
It works in a real browser.
It makes a plan, then opens pages, clicks, types and reads, and writes down every step and everything it finds as it goes.
It reports back.
You get its answer and a recording of the whole run. A run you stop early keeps everything it already found.
While it runs
watchUrl
A link to watch the browser live while it works. The same link plays the recording once it has finished.
outcrawl_agent
status
Where the run has got to: its plan, what it has spent so far, and its answer once it has one.
outcrawl_agent_status
events
Every step, finding and change of plan, in order. Pick up from where you last read.
outcrawl_agent_events
results
What it has collected so far. Records land during the run, so you can read them before it ends.
outcrawl_agent_results
control
Pause it where it stands, do one step yourself, such as a sign-in or a final confirm, and hand it back. It carries on from the page you left.
outcrawl_agent_control
answer
When it needs something only you know, it pauses and asks. Answer, and it carries on from where it stopped.
outcrawl_agent_answer
files
Give it a file to upload, like a resume. The model never reads it, and it is deleted when the run ends.
outcrawl_agent_file_add
cancel
Stop it at any time. Everything it found stays yours.
outcrawl_agent_cancel
notify
Have every step, or only the ending, sent to your webhook as it happens. Signed, and retried for hours if your endpoint is down.
notify.level
Find any earlier run, with what it spent and its recording, with outcrawl_agent_list.
Before it starts
caps.budgetprofileexitrulesoutcrawl_rules_set.schemasecretsintegrationsrecordWhere agents stop
It takes no new instructions once it starts. Take control to step in, or cancel and start again.
A question waits for you, not forever. If nobody answers in time, it carries on without the answer.
Saved credentials and connected tools are set up by a person, never by an agent over MCP.
What you can build
A monitor watches a booking page; when a slot opens, your rules pick it and an agent books it, or holds it for you to confirm in the live view.
Benchmark
Browser Use built this test from the 80 sites where AI agents got blocked most often in their own traffic. We ran it on Outcrawl and scored it with their own code. The next best result was 81.4%.
Pages reached
92.5%
Mean of 3 runs on 71 scored tasks, 95% interval 91.5% to 94.4%.
Mean pass rate, 71 scored tasks, Browser Use’s own scoring code. Ours: 3 runs, 7 October 2026.Method
Pricing
Tool
Dollars on
Agents
A task in plain English, done in a real browser.
About 15 credits a minute
about $0.07 a minute
Browsers
A real browser in the cloud that you control.
1 credit a minute
about $0.29 an hour
Proxy usage
Data through a proxy, on browser sessions and agent runs.
2,000 credits a GB
$9.80 a GB
Agent runs are billed for the AI model's usage, browser time and proxy usage, in credits. The estimate is a typical run; the actual cost depends on the task. The middle half of runs land between 10 and 25 credits a minute on Builder. Model usage converts at your plan's price per credit, so on Pro and Scale the same minute is more credits.
A run of 5 minutes, estimated
About the same in dollars on every plan, because cheaper credits mean more of them. An estimate: the real cost depends on the task.
The budget is a hard ceiling: a run with a budget of 100 credits never bills more, $0.49 on Builder.
While you have control, only browser time and proxy usage are billed, no model usage.
Cancelling stops the spending. What the run already did stays billed.
FAQ
outcrawl_agent, checks on it with outcrawl_agent_status and reads what it found with outcrawl_agent_results. The same run is in the CLI (outcrawl agent "<task>"), the TypeScript and Python SDKs, and plain HTTP.caps.duration to bound it by the clock as well.capped. A bigger budget is the fix; nothing about the task needs to change.