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

# Hermes Agent

> Give Hermes Agent cloud browser automation with Browser Use.

[Hermes Agent](https://github.com/nousresearch/hermes-agent) is an open-source, self-improving AI agent by Nous Research. It has built-in browser automation tools that work with local Chromium out of the box. Add Browser Use and those tools run on cloud browsers with anti-detect profiles, residential proxies in 195+ countries, and stealth browsing.

Two ways to set it up: configure Browser Use as Hermes's cloud browser backend, or install the Browser Use CLI and let Hermes drive it directly.

## Option 1: Cloud Browser Backend

Hermes has built-in browser tools (`browser_navigate`, `browser_click`, `browser_snapshot`, etc.) that default to local Chromium. Point them at Browser Use cloud browsers instead — no extra dependencies, same Hermes experience.

### Setup

**1. Get your API key**

Create an API key from [Settings → API Keys](https://cloud.browser-use.com/settings?tab=api-keys\&new=1).

Running Hermes without a human? Use [x402 pay-per-request](/cloud/guides/x402) instead; it needs no account or API key.

**2. Configure Hermes**

Run the setup wizard:

```bash theme={null}
hermes setup tools
```

Select **Browser Automation**, then **Browser Use**, and paste your API key when prompted.

Or configure manually — add your key to `~/.hermes/.env`:

```bash theme={null}
BROWSER_USE_API_KEY=your_key_here
```

And set the provider in `~/.hermes/config.yaml`:

```yaml theme={null}
browser:
  cloud_provider: browser-use
```

**3. Use it**

Just chat with Hermes — any browsing tasks automatically route through Browser Use cloud browsers:

```
> Find the top trending repositories on GitHub today and summarize them
```

## Option 2: Browser Use CLI

The [Browser Use CLI](https://docs.browser-use.com/open-source/browser-use-cli) is a standalone tool that gives Hermes browser automation through terminal commands. Hermes drives the browser directly via its terminal tool, using Browser Harness and Python helpers through the `browser-use` command.

### Setup

**1. Install the CLI**

```bash theme={null}
uv tool install browser-use
```

**2. Verify the installation**

```bash theme={null}
browser-use doctor
```

**3. Register the skill**

Register the Browser Use skill with the installed CLI:

```bash theme={null}
browser-use skill install
```

Or ask Hermes directly in chat to install it.

**4. Authenticate for cloud browsers**

Authenticate with your API key:

```bash theme={null}
browser-use auth login
```

**5. Use it**

Once the skill is loaded, Hermes can drive the browser through CLI commands via its terminal tool:

```
> Use browser-use to open github.com/trending and summarize the top repos
```

For the complete CLI reference and Python execution examples, see the [Browser Use CLI docs](https://docs.browser-use.com/open-source/browser-use-cli).