> ## 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. # Troubleshooting > Diagnose account, browser, file, and integration problems before retrying. ## My API key has credits, but a request fails Read `GET /api/v2/billing/account` with the same key. It also works for V4 users. Confirm the `projectId`, balance, and `concurrentSessionLimit` against the project selected in the dashboard. Keys in different projects do not share credits. A pay-as-you-go account can legitimately have `planInfo: null`. Read the complete error response before changing billing settings: | Response | What to check | | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 401 | Send `X-Browser-Use-API-Key`; do not put the API key in a Bearer header. | | 402 | Distinguish insufficient project credits from `api_key_monthly_spend_limit_reached`. A top-up does not raise a key's spending cap. | | 404 for a profile/workspace/session | Check the ID type, API version, and owning project. An ID visible in one dashboard project may be inaccessible to another key. | | 409 | Check the detail: a busy conversation and a workspace-file overwrite conflict require different actions. | | 413 | Check per-file and workspace limits. Retrying the same oversized payload does not make it smaller. | | 422 | Compare the request with the reference for that exact endpoint. Standalone-browser fields and V4 run `browserSettings` differ. | | 429 | Distinguish HTTP request-rate limits from occupied browser slots. Reduce polling for the first; stop unneeded browsers or reduce concurrent work for the second. | See [billing](/cloud/guides/billing), [concurrency](/cloud/guides/concurrency), and [workspaces](/cloud/agent/workspaces) for the relevant limits and remedies. ## Why am I charged when I bring my own key or proxy? BYOK means your model provider bills its tokens. Browser Use still charges orchestration plus browser and network usage. A custom proxy has its own provider charges and does not remove Browser Use browser/network charges. A Claude or ChatGPT consumer subscription is not a provider API key. See the [billing breakdown](/cloud/guides/billing). ## The dashboard works, but the same integration does not Check the API key's project, selected model, profile, proxy settings, and API version. A connected integration in the dashboard does not automatically grant every API run access to it. Pass the documented run-level bindings or grants. For example, see [1Password](/cloud/guides/1password) and [Secrets](/cloud/guides/secrets). A site can also challenge a fresh browser even if it accepts an existing logged-in browser. Reuse an appropriate [profile](/cloud/guides/profile-sync), and compare the actual proxy configuration before changing the agent prompt. ## The browser is idle, but usage or a concurrency slot remains A completed agent run can leave its browser available for follow-ups. Closing your SDK client or disconnecting CDP does not stop the managed browser. Stop an unneeded browser with `PATCH /api/v4/browsers/{id}` and `{"action":"stop"}`. See [browser lifetime](/cloud/guides/concurrency#keep-track-of-browser-lifetime). If a local wait times out, the server may still be running. Fetch the existing run's status before creating a replacement, especially if it might already have submitted a form or performed another external action. ## I cannot find a file or recording Wait for the run to finish before listing generated files, and use its V4 workspace ID. Request a fresh download URL if an old one expired. A session's conversation, workspace files, and browser profile are different resources. See [Workspaces and files](/cloud/agent/workspaces). Recordings are off by default for API browsers. Enable recording when creating the browser, stop it when finished, and allow time for processing. A live preview is not a stored video. See [Live preview and recording](/cloud/browser/live-preview). ## Does a new browser guarantee a new IP or a CAPTCHA bypass? No. Selecting a proxy country chooses a location; it does not promise a particular city or a unique IP on every launch. Websites can still block requests or require human verification. Let the automatic solver work before clicking or refreshing a challenge. See [proxies](/cloud/browser/proxies) and [CAPTCHA handling](/cloud/browser/captcha-handling). ## What should I send support? Include the API version and endpoint, run/session/browser/workspace IDs that apply, the project ID, timestamp with time zone, SDK version, and the complete redacted error response. State what you expected and what actually happened. For billing, include the payment reference and selected project; for a file problem, include the filename, size, and the operation that failed. Do not send API keys, passwords, custom-proxy credentials, session cookies, or active CDP/live-view URLs. A screenshot alone often omits the identifier needed to trace a request.