cloud

name cloud description Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2, v3, or v4), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP WebSocket connections, stealth browsers, residential proxies, CAPTCHA handling, webhooks, workspaces, skills marketplace, liveUrl streaming, pricing, or integration patterns (chat UI, subagent, adding browser tools to existing agents). Also trigger for questions about n8n/Make/Zapier integration, Playwright/ Puppeteer/Selenium on cloud infrastructure, or 1Password vault integration. Do NOT use this for the open-source Python library (Agent, Browser, Tools config) — use the open-source skill instead. allowed-tools Read Browser Use Cloud Reference Reference docs for the Cloud REST API, SDKs, and integration patterns. Read the relevant file based on what the user needs. API & Platform Topic Read Current v4 setup, first run, sessions, workspaces, browsers references/api-v4.md Legacy v2 setup, pricing, FAQ references/quickstart.md v2 REST API: all 30 endpoints, cURL examples, schemas references/api-v2.md v3 BU Agent API: sessions, messages, files, workspaces references/api-v3.md Sessions, profiles, auth strategies, 1Password references/sessions.md CDP direct access, Playwright/Puppeteer/Selenium references/browser-api.md Proxies, webhooks, workspaces, skills, MCP, live view references/features.md Parallel, streaming, geo-scraping, tutorials references/patterns.md Integration Guides Topic Read Building a chat interface with live browser view references/guides/chat-ui.md Using browser-use as a subagent (task in → result out) references/guides/subagent.md Adding browser-use tools to an existing agent references/guides/tools-integration.md Critical Notes Use v4 for new hosted-agent integrations. Keep v2 or v3 only when maintaining an existing integration or using a resource not yet wrapped by the v4 SDK. Cloud API base URL: https://api.browser-use.com/api/v2/ (v2), https://api.browser-use.com/api/v3 (v3), or https://api.browser-use.com/api/v4 (v4) Auth header: X-Browser-Use-API-Key: <key> Get API key: https://cloud.browser-use.com/new-api-key Set env var: BROWSER_USE_API_KEY=<key> Cloud SDK: uv pip install browser-use-sdk (Python) or npm install browser-use-sdk (TypeScript) Python v2: from browser_use_sdk import AsyncBrowserUse Python v3: from browser_use_sdk.v3 import AsyncBrowserUse Python v4: from browser_use_sdk.v4 import BrowserUse or AsyncBrowserUse TypeScript v2: import { BrowserUse } from "browser-use-sdk" TypeScript v3: import { BrowserUse } from "browser-use-sdk/v3" TypeScript v4: import { BrowserUse } from "browser-use-sdk/v4" Browser management is available at the v4 REST /browsers resource, but its SDK wrapper still uses the explicit v3 namespace. Always stop a browser explicitly; closing CDP does not stop billing. CDP WebSocket: wss://connect.browser-use.com?apiKey=KEY&proxyCountryCode=us