A headless browser API for your stack.
What I mean by a headless browser API
Running headless Chrome yourself means a server, a Chromium build to keep current, memory leaks, zombie processes and a restart script at 2am. A headless browser API moves the browser off your machine. Your script opens a session over a WebSocket, drives the page with the protocol it already speaks, and closes it. Each session starts on fresh Chrome, so one bad run never poisons the next. You keep your code. We keep the browsers.
1import { chromium } from "playwright";2 3const browser = await chromium.connectOverCDP(4 `wss://cdp-lb.axiom.ai/?token=${process.env.AXIOM_API_KEY}`5);6 7try {8 const context = browser.contexts()[0];9 const page = context.pages()[0] ?? await context.newPage();10 await page.goto("https://example.com");11 await page.screenshot({ path: "out.png", fullPage: true });12} finally {13 await browser.close();14}One runtime
Three layers on one headless browser API.
Start with raw CDP for the scripts you already have. Use step functions when you'd rather not write the waits and loops. Trigger whole saved bots over REST.
See the APIChrome API
A CDP WebSocket to fresh headless Chrome. Puppeteer, Playwright or any CDP client, with full protocol access.
- Existing scripts run as-is
- Execute JavaScript in the page
- Per-session proxy, viewport and user agent
Read about the Chrome API
Step API
High-level browser actions as Node functions. Scrape a paginated list, fill a form or solve a captcha in one call.
- Waits and retries built in
- Mix with raw CDP in the same session
- Exposed to agents over MCP
Read about the Step API
Orchestrate API
Trigger saved bots over REST and read back their runs. For cron, queues, serverless and CI.
- Trigger from anywhere that sends HTTP
- Poll run status and data
- Schedules and retries
Read about the Orchestrate API
Open a cloud session, scrape a paginated list with one step call, and close it. Swap the selectors for your own page.
Get API key1import { AxiomApi } from '@axiom_ai/api';2 3const axiom = new AxiomApi(process.env.AXIOM_API_KEY);4 5await axiom.browserOpen();6try {7 const rows = await axiom.scrape(8 'https://example.com/products',9 '.product-card',10 'button[data-load-more]',11 200,12 {}13 );14 console.log(rows.length);15} finally {16 await axiom.browserClose();17}18 FAQ
Headless browser API questions
No. Replace launch() with connect() or connectOverCDP() pointed at our WebSocket. The rest of the script stays the same.
By the time a session is open. Close sessions as soon as the work is done. Every new account starts with 2 hours of free runtime and free AI tokens.
Yes. Every session starts on fresh Chrome, so cookies and state don't carry between runs unless you set them.
Yes. Set a proxy per session, along with viewport and user agent.
Yes. The step functions are exposed over MCP, so Claude, Cursor or your own agent can drive the browser on your API key.
Run your first script on our headless browser API.
Start with 2 hours of free runtime and free AI tokens for AI steps. No card required.