Browsers run Chromium in the cloud and hand you a session you connect to over CDP. A session is isolated, recorded, and reachable from any Playwright, Puppeteer, Selenium, or plain CDP client, so the same automation runs on a laptop or in production without a local browser.
Create a browser session
Using a browser session
Contexts
Session live view
Files and screenshots
Long sessions
Security
Browsers API
What a session gives you
- A fresh, isolated Chromium instance per session, with its own user data directory.
- A CDP connection URL any automation library can attach to.
- Video replay, logs, live view, and downloads by default, so a failed run can be inspected after the fact.
- Optional persistence with a Context, so a login survives into the next session.
- Session-level settings for viewport, timeout, proxy egress, allowed domains, extensions, and custom metadata.
Credentials
Every request to the Browsers API carries an application Agent key:
curl https://api.agent.mq/v1/browsers/sessions \
-H "Authorization: Bearer $AGENTMQ_TOKEN"The application the key belongs to owns the sessions, contexts, and stored files; see Authentication for how an Agent key is issued and revoked.