Scraping API PricesAll products / Browser Use Cloud
Browser Use Cloud pricing
How Browser Use Cloud combines browser, proxy, task, and model usage, what remains unclear, and which agent teams fit.
published session-time meter only
Fixed for this page; volume is the control.Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.
Your job
What Browser Use Cloud counts
What you pay
Successes you want
200 browser hours
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 1
Attempts you are billed for
200 browser hours
Browser Use Cloud bills failed fetches. This workload assumes none fail, so nothing is added here.
- × 1
What the meter counts
200 browser_hours
One attempt is one billed unit for this workload.
- =
Cash per month
$12.00 /mo
Pay As You Go. Cheapest of every eligible purchase option, not the first plan that fits.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
200 browser hours → 200 browser_hour → Pay As You Go $12.00/mo = $0.06 per browser hour
Every Browser Use Cloud plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Pay As You Go your job | $0.00 | n/a | n/a | n/a | 3 |
| Dev | $29.00 | $24.17 | n/a | 29 usd | 25 |
| Business | $299.00 | $249.17 | n/a | 299 usd | 200 |
| Scaleup | $999.00 | $832.50 | n/a | 999 usd | 500 |
What consumes a unit
This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.
| Operation | Costs | Per | Source |
|---|---|---|---|
| browser.session_time | 0.06 usd | browser_hour | source |
| proxy.residential_bandwidth | 10 usd | gb | source |
| compute.unit | 0.002 usd | step | source |
What Browser Use Cloud does not publish
- Failure billing for agent steps and task initialization is not published.
- The pricing page and repository docs disagree on browser-hour rate.
- Common-unit conversion requires the chosen model, step count, session duration, and proxy traffic.
What Browser Use Cloud is
Browser Use Cloud hosts browsers and an agent runtime for systems that need to navigate and act on websites. Buyers can run browser sessions, use residential proxies, and use Browser Use’s task and agent capabilities rather than assembling each layer independently. Anchor Browser, Browserbase, and Steel are its three nearest named competitors. Browser Use is distinguished by pairing its open-source agent framework with a hosted service whose bill can include browser infrastructure and model-driven execution. Sources: Browser Use pricing, Browser Use Cloud documentation, Anchor Browser, Browserbase pricing, and Steel, retrieved 2026-07-26.
How billing works
There is no single physical unit behind the credit balance. Browser time, proxy traffic, task initialization, agent steps, and model tokens can each consume value. The agent version and selected model determine whether execution is step-based or token-based, while browser duration and transferred proxy data remain separate workload dimensions. The common buying mistake is to translate included credits directly into browser hours. The useful total depends on session duration, traffic, task count, step count, and model input and output. Source: Browser Use pricing, retrieved 2026-07-26.
What Browser Use does not publish clearly
- Whether failed agent tasks reverse or retain task-initialization and step charges. Source reviewed: Browser Use pricing, retrieved 2026-07-26.
- One stable browser-hour figure across the current pricing page and the repository’s Cloud document; the two public sources disagree. Sources reviewed: Browser Use pricing and Cloud documentation, retrieved 2026-07-26.
- A universal conversion from one workflow or completed task to credits, because model choice, tokens, steps, browser time, and traffic vary. Source reviewed: Browser Use pricing, retrieved 2026-07-26.
- A success-only rule covering every browser, proxy, task, model, and skill meter. Source reviewed: Browser Use pricing, retrieved 2026-07-26.
Who it suits
Browser Use Cloud suits agent teams already comfortable with Browser Use’s framework and willing to instrument session duration, traffic, tasks, steps, and token use. It can also suit teams that prefer one provider for both hosted browsers and agent execution. It is less suitable for a browser-only workload that wants one elapsed-time meter, or for procurement that needs a fixed cost per completed task before running a representative workload. The reason is the additive model: it exposes several useful layers, but no one layer predicts the final bill. Sources: Browser Use pricing, Browser Use documentation, and Browser Use Cloud documentation, retrieved 2026-07-26.
Answer
Browser Use Cloud's dated 2026-07-26 price snapshot gives $12.00 for 200 browser hours on its Pay As You Go offer. This older figure is excluded from rankings; check the vendor before buying.
Recorded 2026-07-26 from the vendor's own pricing page.We could not confirm this price in the latest check, so it remains visible for context but cannot lead a price ranking. Check the vendor's pricing page before buying.