Headless Browser sandboxes

A real Chromium session, tenant-isolated, with a Playwright-compatible API and a browser-use-compatible harness for agentic navigation. Sessions can be kept warm with cookies and storage state, or torn down per call.

Two access shapes

• API: Request a screenshot, PDF, scrape, or rendered-HTML dump in a single HTTP call. Best when your agent doesn’t need step-by-step control.
• WebSocket session: Drive Chromium directly with Playwright (or a harness like browser-use). Best when the agent’s loop wants to react to what it sees.

Egress posture

• Default egress: datacenter-IPs, suitable for public-web reads where rate-limit avoidance doesn’t matter
• Residential-egress: opt-in, billed separately, capped per session to avoid abuse — request via support before founding

We do not currently offer “human-in-the-loop CAPTCHA solving”; if your workflow depends on that, talk to us about a tenant-specific contract.

Limits

• 30 minute wall-clock per session by default
• 250 Mbps egress, capped at 10 GB / session
• 2 GB RAM default; raise to 6 GB on per-session upgrade

What we don’t allow

• Logged-in scraping where the auth credential isn’t yours
• Anything that knowingly violates a target site’s ToS — we will pull the plug on tenants that turn the platform into a complaints magnet