> ## 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.

# Browser Infrastructure quickstart

> Launch a cloud browser and connect to it from your code.

Every browser includes stealth, proxies, live preview, and recording. Its
**CDP URL** is a WebSocket endpoint for remotely controlling Chrome.

<img src="https://mintcdn.com/browseruse-0aece648-codex-docs-supported-exports/pg6YX8jO9xwCWYaf/cloud/images/browser-cdp-light.svg?fit=max&auto=format&n=pg6YX8jO9xwCWYaf&q=85&s=61358077338e67ebd34d4736761de9fe" alt="Your code using a CDP URL to connect to and control a cloud browser that accesses the web" noZoom className="block dark:hidden" width="1200" height="400" data-path="cloud/images/browser-cdp-light.svg" />

<img src="https://mintcdn.com/browseruse-0aece648-codex-docs-supported-exports/pg6YX8jO9xwCWYaf/cloud/images/browser-cdp-dark.svg?fit=max&auto=format&n=pg6YX8jO9xwCWYaf&q=85&s=eb7e4cb2d7d55ccbcb9079bdbba4d801" alt="Your code using a CDP URL to connect to and control a cloud browser that accesses the web" noZoom className="hidden dark:block" width="1200" height="400" data-path="cloud/images/browser-cdp-dark.svg" />

Get an [API key](https://cloud.browser-use.com/settings?tab=api-keys\&new=1) and
export it:

```bash theme={null}
export BROWSER_USE_API_KEY=your_key
```

## Install the SDK

Skip this step if you use curl.

<CodeGroup>
  ```bash Python theme={null}
  pip install --upgrade browser-use-sdk
  ```

  ```bash TypeScript theme={null}
  npm install browser-use-sdk@latest
  ```
</CodeGroup>

## Launch a browser

The browser-management resource currently uses the explicit V3 SDK namespace.
The equivalent REST endpoint is API V4.

<CodeGroup>
  ```python Python theme={null}
  from browser_use_sdk.v3 import BrowserUse

  client = BrowserUse()
  browser = client.browsers.create(proxy_country_code="us")
  print(browser.cdp_url)

  # When finished:
  client.browsers.stop(browser.id)
  ```

  ```typescript TypeScript theme={null}
  import { BrowserUse } from "browser-use-sdk/v3";

  const client = new BrowserUse();
  const browser = await client.browsers.create({ proxyCountryCode: "us" });
  console.log(browser.cdpUrl);

  // When finished:
  await client.browsers.stop(browser.id);
  ```

  ```bash curl theme={null}
  browser=$(curl -sS https://api.browser-use.com/api/v4/browsers \
    -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{"proxyCountryCode":"us"}')

  export BROWSER_SESSION_ID=$(echo "$browser" | jq -r .id)
  export BROWSER_USE_CDP_URL=$(echo "$browser" | jq -r .cdpUrl)
  echo "$BROWSER_USE_CDP_URL"

  # When finished:
  curl -X PATCH \
    "https://api.browser-use.com/api/v4/browsers/$BROWSER_SESSION_ID" \
    -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{"action":"stop"}'
  ```
</CodeGroup>

<Warning>
  `browser.close()`, disconnecting CDP, or `client.close()` does not stop the
  managed browser. Use `client.browsers.stop(browser.id)` or call
  `PATCH /api/v4/browsers/{id}` with `{"action":"stop"}`.
</Warning>

## Connect over CDP

Point Playwright or Puppeteer at the CDP URL. Nothing else changes in your
code. The snippets read `BROWSER_USE_CDP_URL`; if you launched with the SDK
above, pass `browser.cdp_url` / `browser.cdpUrl` instead of the variable.

<CodeGroup>
  ```python Python theme={null}
  import os
  from playwright.sync_api import sync_playwright

  with sync_playwright() as p:
      browser = p.chromium.connect_over_cdp(os.environ["BROWSER_USE_CDP_URL"])
      page = browser.contexts[0].pages[0]
      page.goto("https://example.com")
      print(page.title())
  ```

  ```typescript TypeScript theme={null}
  import { chromium } from "playwright";

  const browser = await chromium.connectOverCDP(
    process.env.BROWSER_USE_CDP_URL!,
  );
  const page = browser.contexts()[0].pages()[0];
  await page.goto("https://example.com");
  console.log(await page.title());
  ```

  ```typescript Puppeteer theme={null}
  import puppeteer from "puppeteer-core";

  const browser = await puppeteer.connect({
    browserWSEndpoint: process.env.BROWSER_USE_CDP_URL!,
  });
  const [page] = await browser.pages();
  await page.goto("https://example.com");
  console.log(await page.title());
  ```
</CodeGroup>

Selenium cannot connect to a remote WebSocket CDP URL; use Playwright or
Puppeteer. Stop the browser when you are done (see the warning above), and
the session ends with a [live preview](/cloud/browser/live-preview) and
recording you can open from the dashboard.

<CardGroup cols={2}>
  <Card title="Playwright, Puppeteer, Selenium" icon="code" href="/cloud/browser/playwright-puppeteer-selenium">
    Full connection guide and stop semantics.
  </Card>

  <Card title="Browser settings" icon="sliders" href="/cloud/api-v4/browsers/create-browser-session">
    Configure proxies, screen size, recording, and timeout.
  </Card>
</CardGroup>
