BROWSER USE

- Browser Use Agents: give Browser Use a task and receive completed work. API V4 is current for new integrations.
- Browser Infrastructure: connect your agent or automation to managed browsers through SDK, REST, or CDP. Starts at $0.02/browser-hour.
- Developer tools: Open Source, Browser Harness, SDK, and MCP support the two products above.

[Developer Index](https://browser-use.com/index.md)
[Product Map](https://browser-use.com/llms.txt)
[Full Product Context](https://browser-use.com/llms-full.txt)
[Pricing](https://browser-use.com/pricing.md)
[Cloud Docs](https://docs.browser-use.com/cloud/quickstart)
[Open Source Docs](https://docs.browser-use.com/open-source/introduction)

---

# Browser Use developer resources

Browser Use sells two products to developers:

- **Hosted Web Agents** (Browser Use Agents) — submit a natural-language goal and receive completed work from a managed browser agent.
- **Browser Infrastructure** — connect your own agent or automation to managed browsers through the SDK, REST API, or CDP.

## Quickstart

Create an API key in the [Cloud dashboard](https://cloud.browser-use.com/settings?tab=api-keys&new=1), store it as `BROWSER_USE_API_KEY`, and start an agent run:

```bash
curl https://api.browser-use.com/api/v4/runs \
  -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"task":"Find the top Hacker News story and return its title","model":"grok-4.5"}'
```

## Core developer resources

- [API V4 documentation](https://browser-use.com/api) — the current REST API for agent runs, sessions, browsers, profiles, and workspaces.
- [OpenAPI 3.1 specification](https://browser-use.com/openapi.json) — machine-readable API V4 endpoints and schemas.
- [Python and TypeScript SDK](https://github.com/browser-use/sdk) — typed Browser Use Cloud clients.
- [Webhooks](https://browser-use.com/webhooks) — signed task status notifications.
- [MCP server](https://browser-use.com/mcp) — browser automation tools for MCP-compatible clients.
- [Product map](https://browser-use.com/llms.txt) and [full product context](https://browser-use.com/llms-full.txt) — machine-readable Browser Use documentation.

## Authentication and permissions

API V4 and the Cloud SDK authenticate with a Browser Use API key in the `X-Browser-Use-API-Key` header. [Create an API key](https://cloud.browser-use.com/settings?tab=api-keys&new=1) in the Cloud dashboard.

The Browser Use OAuth 2.0 authorization server advertises Authorization Code with PKCE and Device Authorization as supported grant types for MCP clients. The only scope currently published in its metadata is `mcp`.

- [OAuth authorization-server metadata](https://browser-use.com/.well-known/oauth-authorization-server)
- [OAuth protected-resource metadata](https://browser-use.com/.well-known/oauth-protected-resource)
- [Authentication guide for agents](https://browser-use.com/auth.md)

The public authorization metadata currently exposes one MCP scope. Finer-grained REST API scopes are not advertised, so integrations should isolate API keys by environment, store them in a secret manager, and revoke keys that are no longer needed.