> ## 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 / $200 / $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.
> Budget polling across the project: the standard general bucket is 25 requests/second, including V4 event reads and full run reads. Selected status reads have a separate higher bucket. Use bounded workers, stagger polls, respect Retry-After, and drain hasMore event pages after terminal status. A busy V4 session returns 409; its queue holds 10 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.

# Billing and credits

> Pay-as-you-go credits, project balances, BYOK charges, auto recharge, and API-key spending caps.

Browser Use Cloud uses pay-as-you-go billing. Add credits to the project that owns your API key, then pay for usage. A recurring Browser Use subscription is not required for custom proxies or supported bring-your-own-provider-key (BYOK) usage. Existing customers can retain legacy allowances and pricing.

Use the [pricing page](https://browser-use.com/pricing) for current model, browser, proxy, and network rates. New top-ups have a \$5 minimum and use whole-dollar amounts.

## Which credits does my API key use?

Credits belong to a **project**. All keys in that project use its balance. Funding one project does not fund a key from another project, even if both belong to you.

```bash theme={null}
curl --fail-with-body https://api.browser-use.com/api/v2/billing/account \
  -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY"
```

This endpoint works with the same key you use for V4. Compare `projectId` with the project selected in the dashboard. Read `totalCreditsBalanceUsd` for the reported total and `monthlyCreditsBalanceUsd` / `additionalCreditsBalanceUsd` for its components. A `null` `planInfo` is normal for a pay-as-you-go project; it does not mean the project cannot use paid features.

If a payment succeeded but the expected credits are missing, first check the project and the payment's status. When contacting support, include the project ID, payment time, amount, and receipt or invoice reference. Never include API keys or card details.

## Do credits expire or renew?

| Credit type                               | Behavior                                              |
| ----------------------------------------- | ----------------------------------------------------- |
| Signup credits                            | A one-time grant, not a recurring monthly allowance.  |
| Purchased top-up credits                  | Do not expire.                                        |
| Included credits on a legacy monthly plan | Follow the plan's billing cycle and do not roll over. |

Concurrency tiers are based on qualifying payments to the project, not credits remaining in its wallet. Using purchased credits does not lower an already-granted concurrency allowance. Credit grants do not count as payments. Higher existing or legacy concurrency grants are preserved; see [Concurrency and limits](/cloud/guides/concurrency).

## What does BYOK pay for?

With a supported provider key, the model provider bills token usage to your provider account. Browser Use still charges an orchestration fee of **0.2× the corresponding model token cost**, plus browser and network usage. Keep both accounts funded.

Configure supported provider keys in **Settings → API Keys → Bring Your Own Key**. The dashboard requires adding credits before BYOK setup is available. A pay-as-you-go top-up satisfies that requirement; no recurring subscription is needed. Accounts that have never paid also have model eligibility restrictions.

A Claude consumer subscription is not an Anthropic API key. BYOK means a supported provider credential, not an arbitrary self-hosted model endpoint. See [Models](/cloud/agent/models) for model selection.

## Proxy and browser charges

A [custom proxy](/cloud/browser/proxies) replaces the Browser Use managed proxy. Your proxy provider bills its own usage, and Browser Use browser/network charges still apply. Disabling the managed proxy also leaves browser and direct network usage billable.

Run completion does not necessarily stop the browser. A browser may remain available for the next turn. When your application no longer needs it, explicitly stop the owned browser with `PATCH /api/v4/browsers/{id}` and `{"action":"stop"}`. Disconnecting Playwright/CDP or closing the SDK client is not the cloud stop operation. See [browser lifetime](/cloud/guides/concurrency#keep-track-of-browser-lifetime).

## Auto recharge

Auto recharge has two separate settings:

* **Threshold:** the balance below which another purchase is triggered.
* **Recharge amount:** the amount of credits purchased by that recharge.

For example, a \$10 threshold with a \$50 recharge amount purchases \$50 when the balance falls below \$10. It does not target a final balance of \$50.

Enabling auto recharge while already below the threshold can trigger a charge immediately. Choose an amount that covers your expected workload and check payment history if a recharge fails. Funding and concurrent workloads can change the displayed balance while a payment is being processed.

## API-key monthly spending caps

An API key can have a monthly USD spending cap. It is a **soft limit** on Browser Use charges recorded for that key during the current UTC calendar month, shared across that key's applicable usage.

When a cap is reached, new run/browser admission can return HTTP 402 with a structured detail:

```json theme={null}
{
  "detail": {
    "code": "api_key_monthly_spend_limit_reached",
    "message": "API key monthly spend limit reached",
    "cap": 50,
    "spent": 50.25
  }
}
```

Use `detail.code`, `cap`, and `spent` to distinguish this response from an insufficient project balance. Adding credits does not raise a key's cap. Check the cap in API key settings if the project still has credits.

Spend checks use a cached snapshot, and running or simultaneous work can finish above the cap. A cap is not a strict prepaid wallet or a guarantee that costs stop at exactly that amount. BYOK provider charges are billed separately by the provider. Combine caps with bounded concurrency, project balance monitoring, and per-run controls where available.

See [Concurrency and limits](/cloud/guides/concurrency#diagnose-errors-before-retrying) for 402, 409, and 429 handling.