Skip to main content
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.

Quickstart

Create a session, connect with Patchright, stop it. Five minutes.

For agents

Coding agent? Start here: the rules, the endpoints, the mistakes.

Best practices

How to stay unblocked: framework, CDP hygiene, cleanup.

API reference

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; 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

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

​
Next

  • Quickstart: create and stop a session end to end.
  • Create a session: every field you can pass.
  • Browser pools: warm browsers, acquired in under a second.
  • Frameworks: connection code for Patchright, Playwright, Puppeteer, Browser Use, Stagehand and Crawl4AI.