Skip to main content

Browser Sessions

Browser sessions give you a full browser instance with anti-bot stealth active. Instead of getting back markdown, you get a CDP (Chrome DevTools Protocol) WebSocket URL that Playwright or Puppeteer can connect to.

When to Use Sessions

How It Works

  1. Create a session via POST /v1/sessions
  2. Connect Playwright/Puppeteer to the returned wsEndpoint
  3. Use normally - navigate, click, type, evaluate, screenshot
  4. Stop the session via DELETE /v1/sessions/:id
The browser has anti-bot stealth active: navigator.webdriver = false, navigator/WebGL spoofing, WebRTC masking. Your automation looks like a real user.

Quick Example

Stealth Features

Every session includes:
  • navigator.webdriver = false (the #1 bot detection signal)
  • Navigator property spoofing (deviceMemory, hardwareConcurrency, platform)
  • WebGL/Canvas fingerprint randomization
  • WebRTC IP leak prevention
  • Chrome plugin array simulation

Billing

Sessions are billed at 1 credit per minute. The timer starts on creation and stops when the session is closed or expires. Sessions auto-close after the configured timeout (default: 60 minutes max).

Supported Clients

Selenium via chromedriver is not supported (requires exclusive Chrome access).