> ## Documentation Index
> Fetch the complete documentation index at: https://browseruse-0aece648-codex-docs-supported-exports.mintlify.site/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.

# FAQ

> Common questions and solutions.

## Which model should I use?

* **GPT-5.6 Luna** (`gpt-5.6-luna`, recommended) — the best balance of accuracy, speed, and price for most tasks.
* **Claude Opus 5** (`claude-opus-5`) — maximum intelligence for difficult, long-horizon work.
* **Grok 4.5** (`grok-4.5`) — a strong general-purpose alternative.
* **GPT-5.6 Sol** (`gpt-5.6-sol`) — a higher-cost OpenAI option for complex tasks.
* **MiniMax M3** (`minimax-m3`) — inexpensive for simple and high-volume tasks.

See [Models](/cloud/agent/models) for the complete V4 picker and pricing.

## How do I get the live browser URL?

The V4 run's `browser.ready` event contains `live_view_url`. Embed it in an iframe or open it in a browser.

```python theme={null}
from browser_use_sdk.v4 import BrowserUse

client = BrowserUse()
created = client.runs.create("Go to example.com")
client.runs.wait_for_completion(created.id)
events = client.runs.events(created.id, limit=100)
ready = next(event for event in events.events if event.type == "browser.ready")
print(ready.data["live_view_url"])
```

Poll events until `browser.ready` appears if you need the URL while the run is still active. See [Human in the loop](/cloud/agent/human-in-the-loop) for a complete flow.

## Getting blocked by a website

Stealth and proxies are active by default. If you're still getting blocked:

* **Use a profile** with logged-in cookies to bypass login walls.
* **Try a different proxy country** to match the target region.

If it still doesn't work, contact support inside the [Cloud Dashboard](https://cloud.browser-use.com) — send us a link to the page where you're getting blocked.

## Rate limited (429 errors)

HTTP request limits, browser concurrency, and a full session message queue can all return 429. Inspect the response before retrying: increasing browser concurrency does not increase the general request bucket used by V4 event reads.

Use bounded workers, stagger polling, and respect `Retry-After` when provided. The SDK retries 429 responses, but a sustained workload needs its own request budget. See [Concurrency and limits](/cloud/guides/concurrency) for account-limit lookup, polling budgets, queue behavior, and error handling.

For insufficient-balance or API-key spending-cap errors (402), see [Billing and credits](/cloud/guides/billing).

## V2 or V4 — which should I use?

Use **V4** for difficult tasks where accuracy matters. It supports:

* Run-focused API with a cheap status polling endpoint
* Conversation sessions with follow-ups
* Persistent workspaces and turn-scoped file attachments
* Incremental events for custom UIs and monitoring
* Per-run cost totals, cost caps, and optional judgement

Use **V2** when tasks are simple and your priority is very low cost and
predictable speed. Its accuracy is substantially lower.

See Browser Use at #1 on the
[Odysseys benchmark](https://odysseysbench.com/leaderboard).