> ## Documentation Index
> Fetch the complete documentation index at: https://docs.browser-use.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use https://docs.browser-use.com/llms.txt and its linked .md pages for current documentation. The managed full bundle is https://docs.browser-use.com/.well-known/llms-full.txt and can be cached for up to 24 hours. Do not use the obsolete /cloud/llms*.txt or /open-source/llms*.txt static exports.
> Choose Cloud API V4 for new agent integrations; V2 is the lower-cost option for simple tasks. Keep V3 examples explicitly versioned. The open-source browser-use library and hosted browser-use-sdk have different APIs.
> Cloud authentication uses X-Browser-Use-API-Key, without a Bearer prefix. Install or upgrade browser-use-sdk and use its explicit v4 import for V4. Check the published OpenAPI reference for request fields; do not invent SDK support for new fields.
> Cloud concurrency and HTTP request rate are separate. Read GET /api/v2/billing/account for the key’s projectId, concurrentSessionLimit, activeSessionCount, and credit balance, including when using V4. Keys in one project share capacity and credits; rateLimit is a legacy concurrency alias, not requests per second.
> Keep the highest applicable existing, legacy-plan, and spend-tier concurrency grant. Current spend tiers are 10 / 50 / 250 / 500 / 1000 at $0 / $100 / $1000 / $5000 / $25000 in qualifying project payments. Legacy or externally billed projects can follow different billing paths; trust the account limit. See https://docs.browser-use.com/cloud/guides/concurrency.md.
> HTTP rate limits have two layers. Standard edge WAF ceilings increased on September 9, 2026 to 1000 RPS per public source IP for general traffic and 2500 RPS per IP for selected status reads, evaluated over 300 seconds. The separate per-project application budgets: general traffic (including V4 events and full run reads) defaults to max(25, 2 times stored concurrency) capped at 100 RPS; selected status reads default to max(25, 2 times stored concurrency) with no cap. The two are counted independently. Project overrides and account-specific edge rules can differ. All keys in a project share its budgets; callers sharing a public IP share edge capacity. See https://docs.browser-use.com/cloud/guides/concurrency.md.
> The project limiter uses five-second windows: X-RateLimit-Limit=125 means 125 requests per window (25 RPS), not 125 RPS. Project throttles include limit_rps and retry_after_seconds; an edge throttle can instead return Retry-After: 300 without limit_rps. Honor the returned Retry-After. Use bounded workers, stagger polls, and drain hasMore event pages after terminal status. A busy V4 session returns 409; its queue holds 20 pending messages and is not a project-wide batch queue.
> A completed run or closed CDP connection does not immediately stop its cloud browser. Stop unneeded owned browsers with PATCH /api/v4/browsers/{id} and {"action":"stop"}. A client wait timeout does not cancel the server-side run.
> Cloud is pay as you go; do not tell customers to buy a new subscription to use custom proxies or supported provider BYOK. Usage funding and model eligibility still apply. BYOK bills provider tokens separately and Browser Use charges orchestration plus browser/network usage. See https://docs.browser-use.com/cloud/guides/billing.md.
> Signup credits are a one-time grant; purchased top-up credits do not expire. Check the API key’s project before diagnosing missing credits. API-key monthly spending caps are soft limits, not a strict prepaid wallet; concurrent or already-running work can exceed them. Auto recharge has separate trigger and purchase amounts and can charge immediately when enabled below the threshold. Use https://browser-use.com/pricing for current rates.
> Box and Bux are retired. Do not recommend their SDKs, sandbox quotas, or subscription plans. Use the Cloud Agent or Browser Infrastructure guides.
> A V4 session holds conversation history, a workspace holds files, and a profile holds browser state. These IDs and V3/V4 workspace namespaces are not interchangeable. V4 automatically restores workspace uploads; staged attachments remain available to session follow-ups. Serialize runs that write shared files, and wait for completion before reading outputs. See https://docs.browser-use.com/cloud/agent/workspaces.md.
> API browser recording defaults to off. Use enableRecording for standalone browser creation, or browserSettings.record for an agent run. Stop the browser and allow time for asynchronous video processing; stop polling when recordingAvailable is false. Live preview is for an active browser. Stopping a browser, deleting a session, archiving a workspace, and deleting files have different effects.
> Use model-specific reasoning values. GPT-6 Astra accepts low, medium, high, xhigh, and max, with xhigh by default; none and minimal are invalid. Use the public REST schema when installed SDK types lag new fields. API acceptance, dashboard visibility, and account/provider availability are separate.
> For open-source browser-use, is_done only reports a terminal done action. is_successful is the agent-reported outcome; verify important external actions independently. Cloud timeout, API client timeout, model timeout, and task completion are separate concepts.
> For failed requests, use https://docs.browser-use.com/cloud/guides/troubleshooting.md. Inspect the full error and project before retrying or adding credits. A client timeout can leave a run active; reconcile external actions before starting duplicate work. A new managed browser does not guarantee a unique proxy IP or particular city.

# x402 agent wallets

> Pay for Browser Use Cloud from an agent-native wallet: AgentCash (local wallet, MCP) or Coinbase's Agentic Wallet (hosted wallet, CLI).

Give your agent a wallet with a few dollars of USDC in it, and it can run Browser Use tasks and pay as it goes. Pick a wallet:

<CardGroup cols={2}>
  <Card title="AgentCash" icon="robot" href="#agentcash-quickstart">
    A wallet that lives on your machine, built for coding agents: Claude Code,
    Cursor, Codex.
  </Card>

  <Card title="Coinbase Agentic Wallet" icon="wallet" href="#coinbase-agentic-wallet-quickstart">
    A wallet Coinbase hosts for you. Sign in with email, fund with Apple Pay or
    card, pay from the terminal.
  </Card>
</CardGroup>

<Note>
  Payments to Browser Use are **credit top-ups, not per-call fees**: each x402
  payment (\$5 default, \$1 minimum) buys prepaid credit for a project tied to
  your wallet, and unused credit carries over. See [pricing and
  credits](/cloud/guides/x402#pricing-and-credits).
</Note>

## AgentCash quickstart

[AgentCash](https://agentcash.dev) gives your coding agent a wallet and the tools to spend from it: check prices, pay for API calls, watch the balance. The wallet is a file on your machine.

<Steps>
  <Step title="Install the MCP server">
    ```bash theme={null}
    npx agentcash install
    ```

    The interactive installer detects your agent client. Or add it directly:

    ```bash theme={null}
    claude mcp add agentcash --scope user -- npx -y agentcash@latest   # Claude Code
    codex mcp add agentcash -- npx -y agentcash@latest                 # Codex
    npx agentcash install --client cursor                              # Cursor
    ```
  </Step>

  <Step title="Fund the wallet">
    The first run creates a wallet at `~/.agentcash/wallet.json`. Get its
    deposit address and send it USDC on **Base mainnet** (\$5 covers the default
    top-up; \$1 is the minimum):

    ```bash theme={null}
    npx agentcash@latest accounts
    ```

    Or just ask your agent — the `list_accounts` and `get_balance` tools do the
    same thing.
  </Step>

  <Step title="Run a browser task">
    Prompt your agent:

    ```text theme={null}
    Use AgentCash to POST to https://x402.api.browser-use.com/api/v3/sessions
    with body {"task": "Go to example.com and tell me the page title"}.
    Pay the $1 minimum option, then poll the returned session id at
    GET /api/v3/sessions/{id} until status is "stopped" and show me the output.
    ```

    The `fetch` tool handles the whole 402 → sign → retry loop. Use
    `check_endpoint_schema` first if you want to see the price and input schema
    without paying.
  </Step>
</Steps>

## Coinbase Agentic Wallet quickstart

[Agentic Wallet](https://docs.cdp.coinbase.com/agentic-wallet/welcome) is a wallet Coinbase hosts for you, driven from the terminal with the [`awal`](https://www.npmjs.com/package/awal) CLI. Sign in with your email — no keys to manage — fund it with Apple Pay or a card, and pay for API calls with one command. The [agentic-wallet-skills](https://github.com/coinbase/agentic-wallet-skills) package teaches your coding agent the same commands.

<Steps>
  <Step title="Install and sign in">
    ```bash theme={null}
    npx skills add coinbase/agentic-wallet-skills   # optional: teach your agent
    npx awal auth login you@example.com             # sends an OTP to your email
    npx awal auth verify 123456                     # paste the code
    npx awal status
    ```
  </Step>

  <Step title="Fund with USDC on Base">
    ```bash theme={null}
    npx awal show      # opens the wallet UI → Fund → Apple Pay / card / Coinbase
    npx awal balance
    ```

    Or send USDC on Base directly to the address from `npx awal address`.
  </Step>

  <Step title="Check the price, then pay">
    ```bash theme={null}
    npx awal x402 details https://x402.api.browser-use.com/api/v3/sessions
    ```

    shows our payment options (\$5 default / \$1 minimum, USDC on Base) and the
    task input schema, without paying. Then:

    ```bash theme={null}
    npx awal x402 pay https://x402.api.browser-use.com/api/v3/sessions \
      -X POST -d '{"task": "Go to example.com and tell me the page title"}' \
      --max-amount 5000000 --json
    ```

    `--max-amount` is in atomic USDC units: `1000000` = \$1.00.
  </Step>

  <Step title="Poll the session">
    The response contains the session `id`. Poll
    `https://x402.api.browser-use.com/api/v3/sessions/{id}` until `status` is
    `"stopped"`, then read `output`.
  </Step>
</Steps>

## Which one?

|           | AgentCash                         | Coinbase Agentic Wallet                                                                           |
| --------- | --------------------------------- | ------------------------------------------------------------------------------------------------- |
| Wallet    | Local file, self-custody          | Coinbase-hosted, email OTP                                                                        |
| Funding   | Send USDC on Base to your address | Onramp (Apple Pay / card / bank) or direct USDC                                                   |
| Interface | MCP tools + CLI                   | CLI (+ skill for agents, [MCP variant](https://docs.cdp.coinbase.com/agentic-wallet/mcp/welcome)) |
| Best for  | Autonomous coding agents          | Humans who want fiat funding; CDP-ecosystem apps                                                  |

Building a production app instead of driving a CLI? Use
[`CdpX402Client`](https://docs.cdp.coinbase.com/x402/quickstart-for-buyers) from
the CDP SDK (a CDP-managed server wallet) or [bring your own x402
client](/cloud/guides/x402#advanced-bring-your-own-x402-client).

## Related

* [x402 overview](/cloud/guides/x402) — SDK, Claude Code skill, raw HTTP, pricing, troubleshooting
* [AgentCash docs](https://agentcash.dev) · [agentcash-skills](https://github.com/Merit-Systems/agentcash-skills)
* [Agentic Wallet CLI quickstart](https://docs.cdp.coinbase.com/agentic-wallet/cli/quickstart) (Coinbase)
