> ## 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 / $100 / $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. > HTTP rate limits have two layers. Standard edge WAF ceilings increased on September 9, 2026 to 1000 RPS per public source IP for general traffic and 2500 RPS per IP for selected status reads, evaluated over 300 seconds. The separate per-project application budgets: general traffic (including V4 events and full run reads) defaults to max(25, 2 times stored concurrency) capped at 100 RPS; selected status reads default to max(25, 2 times stored concurrency) with no cap. The two are counted independently. Project overrides and account-specific edge rules can differ. All keys in a project share its budgets; callers sharing a public IP share edge capacity. See https://docs.browser-use.com/cloud/guides/concurrency.md. > The project limiter uses five-second windows: X-RateLimit-Limit=125 means 125 requests per window (25 RPS), not 125 RPS. Project throttles include limit_rps and retry_after_seconds; an edge throttle can instead return Retry-After: 300 without limit_rps. Honor the returned Retry-After. Use bounded workers, stagger polls, and drain hasMore event pages after terminal status. A busy V4 session returns 409; its queue holds 20 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. # Upload Workspace Files > Presigned PUT URLs for input files, placed under ``uploads/`` in the workspace. The agent pulls them in at the start of every run. URLs are pinned to the declared Content-Type and exact Content-Length. ## OpenAPI ````yaml /cloud/openapi/v4.json post /workspaces/{workspace_id}/files/upload openapi: 3.1.0 info: title: Browser Use Public API v4 summary: Browser Use agent runs API (v4) version: 4.0.0 servers: - url: https://api.browser-use.com/api/v4 description: Production server security: [] paths: /workspaces/{workspace_id}/files/upload: post: tags: - Workspaces summary: Upload Workspace Files description: |- Presigned PUT URLs for input files, placed under ``uploads/`` in the workspace. The agent pulls them in at the start of every run. URLs are pinned to the declared Content-Type and exact Content-Length. operationId: upload_workspace_files_workspaces__workspace_id__files_upload_post parameters: - name: workspace_id in: path required: true schema: type: string format: uuid title: Workspace Id requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/WorkspaceFileUploadRequest' responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/WorkspaceFileUploadResponse' '400': description: Invalid request (bad session/workspace pairing or file path). '403': description: Zero Data Retention is enabled on the project (V4 unsupported). '404': description: Run, session, workspace, or profile not found. '409': description: One or more files would replace existing workspace files. '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - APIKeyHeader: [] components: schemas: WorkspaceFileUploadRequest: properties: files: items: $ref: '#/components/schemas/WorkspaceFileUploadItem' type: array maxItems: 10 minItems: 1 title: Files allowOverrides: type: boolean title: Allowoverrides description: >- When false, return 409 before reserving storage if any uploaded filename would replace an existing workspace file. default: true type: object required: - files title: WorkspaceFileUploadRequest WorkspaceFileUploadResponse: properties: files: items: $ref: '#/components/schemas/WorkspaceFileUploadResponseItem' type: array title: Files type: object required: - files title: WorkspaceFileUploadResponse HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError WorkspaceFileUploadItem: properties: name: type: string maxLength: 255 minLength: 1 title: Name description: Filename, e.g. "data.csv" contentType: type: string maxLength: 255 title: Contenttype description: MIME type, e.g. "text/csv" default: application/octet-stream size: type: integer maximum: 52428800 minimum: 1 title: Size description: Exact file size in bytes; the presigned URL is pinned to it. type: object required: - name - size title: WorkspaceFileUploadItem WorkspaceFileUploadResponseItem: properties: id: type: string format: uuid title: Id description: >- Upload id. Pass THIS in RunCreateRequest.attachedFileIds to attach the file to a run. name: type: string title: Name description: Original filename from the request storedName: type: string title: Storedname description: Sanitized filename the object is stored under, e.g. "data.csv". path: type: string title: Path description: Path within the workspace, e.g. "uploads/data.csv" willOverride: type: boolean title: Willoverride description: >- True if a file with this stored_name already exists in the workspace and uploading will replace it. Surface a warning to the user. uploadUrl: type: string title: Uploadurl description: >- Presigned PUT URL (5 min expiry). PUT the file bytes with the matching Content-Type and Content-Length headers. type: object required: - id - name - storedName - path - willOverride - uploadUrl title: WorkspaceFileUploadResponseItem ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: APIKeyHeader: type: apiKey in: header name: X-Browser-Use-API-Key ````