Browser Use Cloud Pricing (Sep 2026): Rates, Examples, Alternatives

Short version, as of 27 Sep 2026: Browser Use Cloud charges $0.02 per browser hour, $5 per GB of residential proxy traffic (on by default), and for its hosted agents the model price plus 20%. No subscription, credits from $5 that never expire, and $15 free for eligible sign-ups. Every number below comes from browser-use.com/pricing; check it before you commit, prices move.

We run a competing product, Human Browser, so we say plainly where Browser Use is cheaper and where it is not.

The two products you can pay for

Browser Use started as an open-source Python framework for LLM browser agents. Browser Use Cloud sells two things on one balance:

• Browsers: hosted Chrome sessions for your own agent or Playwright code.
• Browser Use Agents: you give it a task, its agent runs it in one of those browsers.

Browser Use Cloud rates

Model prices, per 1M tokens (20% fee included)

Concurrency grows with what you have spent

Agents and browsers share one project limit. Free credits and disputed payments do not count toward the spend.

What a job actually costs

Browser time is almost free at $0.02 an hour: a 5-minute session is under a fifth of a cent. What decides your bill is traffic and, for agents, the model.

• Your own Playwright script, 10,000 page loads a month, 1 minute each, 2 MB per page over the residential proxy: browser 10,000 minutes is about $3.33; traffic 20 GB is $100. Traffic is 97% of the bill. Moving the pages that do not need a residential IP to direct traffic ($0.20 per GB) is the biggest saving.
• A hosted agent task is mostly model tokens. As an illustration (our assumption, not a measurement): 25 steps at about 8,000 input and 300 output tokens each on Gemini 3.6 Flash is about $0.36 input and $0.07 output, plus a cent or two of browser time and traffic. A cheaper model such as GPT-5.6 Luna or BU 2.0 cuts that by several times; Opus or GPT-6 Astra multiplies it. Prompt caching (the cached-input column) lowers it further on long runs.

Browser Use Cloud vs Human Browser

Human Browser is a goal-level API: you send a task in plain English, our agent drives a real headful Chrome on a residential IP, and you get the result and a live viewer URL.

Where Browser Use wins: raw browser time by a factor of five ($0.02 against $0.10 an hour), model billing at list price + 20% or your own key (we charge $0.02 per agent step with the model included), raw CDP for your own scripts, much higher concurrency as you spend, more free credit on sign-up (we have none), and SOC 2. If you write your own agent or Playwright code, it is the cheaper home for it.

Where we win: residential traffic ($4 against $5 per GB), a person can take over any task in the live viewer without paying for that time, and you do not run an agent loop at all. On our production the median task took about 8 agent steps and cost $0.24 all-in (132 successful customer tasks, Sep 2026).

Trying Human Browser

One call starts a task; poll for the result. The response carries a viewer_url to watch it live.

curl -X POST https://agent.humanbrowser.cloud/a2a \
  -H 'Authorization: Bearer hb_live_xxxx' \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc": "2.0", "id": 1, "method": "message/send",
    "params": {
      "message": { "role": "user",
        "parts": [{"kind":"text","text":"Open news.ycombinator.com and return the top 5 story titles as JSON."}] },
      "metadata": { "country": "us" }
    }
  }'

curl -X POST https://agent.humanbrowser.cloud/a2a \
  -H 'Authorization: Bearer hb_live_xxxx' -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tasks/get","params":{"id":"<task id from result.id>","wait_seconds":30}}'

MCP for Claude, Cursor or Codex is in the MCP guide; everything else is in the docs. Related: Browser Use alternative, Skyvern alternative, vs Steel, vs Hyperbrowser, Browserbase pricing.