> ## Documentation Index
> Fetch the complete documentation index at: https://docs.driver.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Driver runs real Chrome on real hardware and gives you a CDP URL. Create a session, connect, do the work, stop it.

Driver is hosted browser infrastructure. A session is one real Chrome window on one real machine, on an ISP connection in the country you pick, reachable over the Chrome DevTools Protocol a few seconds after you ask for it. You write the automation; we run the browser.

> [card] [Quickstart](https://docs.driver.dev/docs/start/quickstart.md)
>
> Create a session, connect with Patchright, stop it. Five minutes.

> [card] [For agents](https://docs.driver.dev/docs/start/for-agents.md)
>
> Coding agent? Start here: the rules, the endpoints, the mistakes.

> [card] [Best practices](https://docs.driver.dev/docs/start/best-practices.md)
>
> How to stay unblocked: framework, CDP hygiene, cleanup.

> [card] [API reference](https://docs.driver.dev/api-reference/overview.md)
>
> Every endpoint, generated from the live OpenAPI document.

## How it works

**1. Create a session**

`POST /v1/browser/session` with the options you need. You get a `sessionId` and a `cdpUrl`.

**2. Connect over CDP**

Point your framework at `cdpUrl`. Use [Patchright](https://docs.driver.dev/docs/frameworks/patchright.md); stock Playwright and Puppeteer leave fingerprints that get sessions blocked.

**3. Do the work**

Navigate, fill, click, extract. It's a normal Chrome: no headless quirks, no emulated hardware.

**4. Stop the session**

`DELETE /v1/browser/session?sessionId=…`. You pay for bandwidth, so stop what you're done with.

## What you get

| | |
| - | - |
| **Real Chrome** | Consumer Chrome on real hardware, not a headless container. |
| **ISP networks** | Sessions egress from ISP connections in the country you choose. Bring your own SOCKS5 proxy if you need to. |
| **Profiles** | Save cookies and local state under a name and reuse them, so logins survive between sessions. |
| **Browser pools** | Keep browsers warm with fixed options and take one in under a second. |
| **CAPTCHA solving** | One flag loads our solver into the session. |
| **Live view** | Watch and drive any running session from the dashboard or a viewer URL. |

## Base URL and authentication

Everything goes to `https://api.driver.dev` with your workspace API key as a bearer token. Keys are under **Settings → API keys** in the [dashboard](https://app.driver.dev).

```bash theme={"dark"}
Authorization: Bearer $DRIVER_API_KEY
```

## Next

* [Quickstart](https://docs.driver.dev/docs/start/quickstart.md): create and stop a session end to end.
* [Create a session](https://docs.driver.dev/docs/sessions/create.md#options): every field you can pass.
* [Browser pools](https://docs.driver.dev/docs/sessions/pools.md): warm browsers, acquired in under a second.
* [Frameworks](https://docs.driver.dev/docs/frameworks/patchright.md): connection code for Patchright, Playwright, Puppeteer, Browser Use, Stagehand and Crawl4AI.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.