# 0Browser

> Browser infrastructure for agents: persistent profiles, ephemeral or profile-backed sessions, direct CDP, a Stagehand Agent API, and reusable Skills Runs.

API base: https://api.0browser.io/api/v1
Console: https://app.0browser.io
REST authentication: Authorization: Bearer sk_... (use the user's existing key).

## Documentation

- [Complete agent guide](https://0browser.io/llms-full.txt): Setup, working examples, profiles, sessions, CDP, Agent API, Skills Build/Run, ownership, leases, errors and cleanup. Read this before executing tasks.
- [OpenAPI 3.1 specification](https://0browser.io/openapi.json): Authoritative endpoint paths, request schemas, response shapes and permissions. Fetch the relevant operations instead of guessing parameters.
- [Interactive API reference](https://0browser.io/openapi): Human-readable endpoint reference and request examples.
- [Console](https://app.0browser.io): Use the supplied API key to inspect sessions, configure account AI, manage profiles and build Skills.

## Choose a control method

- Direct CDP: Puppeteer/Playwright or another CDP client controls the session.
- Agent API: observe, act, extract, goto and state under /sessions/{id}/agent. Requires an active session attached to a profile. AI operations use this API key's own configured AI settings.
- Skills Run: assign a profile and input to an Operation, then execute an immutable published Skill version. Build authors the draft; publishing does not change existing Runs.

A Run/Build/agent lease controls a profile exclusively. Respect 409 conflicts. REST does not accept token query authentication; WebSocket endpoints accept token=sk_.... IDs are opaque: use full IDs returned by the API without truncation or redaction.