Introduction
Give your AI agents the infrastructure they need: browsers, shells, storage and isolated machines. Start with a quickstart, or pick a topic.
Boxline gives your AI agent its own computer in the cloud. Each session is an isolated machine with a real Chrome browser, an optional bash shell, and a disk they share. You drive it with Playwright, Puppeteer, the API, the SDKs, or MCP.
You pay per second while a session runs. When you only need a page, the web APIs skip the session altogether.
Start here
Pick one. Each takes about five minutes.
- QuickstartBrowser sessionsStart a cloud browser, drive it with Playwright, and watch it live.About 5 minutes
- QuickstartWeb APITurn any URL into Markdown with one request. No session to manage.About 5 minutes
- QuickstartAI agentDescribe a task in plain words and let the agent do it in a session.About 5 minutes
Explore
- SessionsOptions, lifecycle, limits and the session object.
- Playwright and PuppeteerConnect your own browser code over the Chrome DevTools Protocol.
- Proxies and CAPTCHAsBrowse from another country, and let a person or the platform handle CAPTCHAs.
- ShellRun Python, Node and ffmpeg next to the browser.
- Node SDK@boxline/sdk for Node 18 and later.
- Python SDKThe boxline package for Python.
- CLIRun the agent, fetch pages and open shells from your terminal.
- Computer useRun Claude's and OpenAI's computer-use actions on a session.
- SearchWeb results in one request, with the top pages as Markdown.
- WebhooksSigned callbacks when sessions stop or are deleted, and when runs finish.
- API referenceEvery endpoint, with examples in curl, Node, Python and the CLI.
- MCPGive ChatGPT, Claude, Cursor and other MCP clients a cloud browser as tools. Connect with a sign-in, no API key.
How it fits together
| Part | What it is |
|---|---|
| Session | One isolated machine, yours alone, for as long as you need it. See Configuring sessions. |
| Browser | Chrome, driven over the Chrome DevTools Protocol (CDP), the protocol Playwright and Puppeteer speak. You can watch it and take over in the live view. |
| Shell | An optional bash shell on the same machine, with Python, Node, ffmpeg, ImageMagick and poppler. See Shell. |
| Workspace | The /workspace disk that the browser, the shell and the API share. Downloads land there. See File uploads and downloads. |
| Web APIs | One request per page: fetch, screenshot, PDF, extract and crawl. See the Web overview. |
| AI | An AI agent that does a whole task, steps in plain English, and scripts that mix code and AI. |
What you need
- An account and an API key. Sign up, confirm your email with the 6-digit code we send you, then create a key in the console under Settings → API keys. Working with a team? See organizations, projects and team members.
- The API at
https://api.boxline.dev. The SDKs read the key fromBOXLINE_API_KEYand the address fromBOXLINE_API_URL. - Node 18 or later, or Python, if you use an SDK. Any language works with the HTTP API.
Get help
- Every response has an
X-Request-Idheader. Quote it when you ask for support. See Errors and request ids. - New features and breaking changes are in the changelog.
- How sessions are isolated is on the security page.
These docs describe a beta API. Endpoints, fields and SDK methods may change before general availability; breaking changes will be listed in the changelog.