Axiom Browser Automation - No-Code to Claude-Powered RPA

TL;DR

TL;DR: Axiom.ai is a browser automation platform (YC W21) that lets you build bots via no-code drag-and-drop, Puppeteer/Playwright code, or natural language prompts to Claude — running on Axiom’s cloud or your own infrastructure.

What Is Axiom?

Axiom.ai is a browser automation tool that sits between classic RPA (Robotic Process Automation) and modern AI-native agents. It targets the same problem as tools like Axiom.ai, Browse.ai, and browser-based Selenium workflows — automating repetitive browser tasks — but offers three distinct interfaces:

• No-code builder — a visual drag-and-step editor for building automations without writing any code
• Code editor — use Puppeteer, Playwright, or any CDP-speaking client to drive Axiom’s cloud browsers via a WebSocket API
• Claude integration — describe what you want in plain English, and Claude builds the automation for you

The product launched on Hacker News in 2021 as a Y Combinator W21 batch company and has accumulated significant user traction since then.

Source and Accuracy Notes

⚠️ This section is MANDATORY. All links must be verified from actual source, not guessed.

• Project page: axiom.ai ← verified June 23, 2026
• HN launch thread: news.ycombinator.com/item?id=26327717 (160 points, YC W21)
• License: Proprietary (Axiom AI Limited) — not an open-source project

Core Features

No-Code Builder

The builder interface lets you construct browser workflows step-by-step by selecting pre-built actions (click, type, extract, scroll, wait, etc.) and chaining them together. Each step maps to a specific browser action. The builder is designed for non-developers and supports:

• Scrapers, form fillers, monitors, and reporters
• Loop and conditional logic
• Scheduling (cron-like triggers)
• Integration with Google Sheets, APIs, and webhooks

Developer API (Chrome API)

For developers who prefer code, Axiom exposes a long-lived WebSocket endpoint (wss://cdp-lb.axiom.ai/) that speaks Chrome DevTools Protocol (CDP). You connect via Puppeteer or Playwright using browser.connectOverCDP():

import { chromium } from "playwright";

const browser = await chromium.connectOverCDP(
  `wss://cdp-lb.axiom.ai/?token=${process.env.AXIOM_API_KEY}`
);

const context = browser.contexts()[0];
const page = context.pages()[0] ?? await context.newPage();
await page.goto("https://example.com");
await page.screenshot({ path: "out.png", fullPage: true });
await browser.close();

This is the same protocol that powers Chrome DevTools, meaning any tool that speaks CDP (Puppeteer, Playwright, Chrome DevTools, Debugging Protocol clients) can drive Axiom’s cloud browsers.

Step API

A higher-level Node.js library (axiom-api) wraps the Chrome API with pre-built step functions for common browser actions:

• step.click(selector)
• step.type(selector, text)
• step.extract(selector)
• step.waitForNavigation()

This lets you build automations programmatically without managing CDP sessions manually.

Claude Integration

The most distinctive feature is the natural language path. You describe the automation you want (“Get every job listing from this careers page and put it in a Google Sheet”), and Claude generates the Axiom automation. This is described on the Axiom website as “Build bots with no-code, code them, or describe them to Claude.”

Deployment Options

• Cloud — Axiom runs the browsers on their infrastructure; you manage automations via the dashboard
• Self-hosted — run the browser automation on your own machine (your data stays local)

Automation Types

Axiom’s website lists these primary use cases:

| Type | Example prompt | |---|---| | Scrapers | “Get every job listing from this careers page” | | Form fillers | “Submit each row from my CSV into this signup form” | | Monitors | “Watch this page and alert me when stock changes” | | Reporters | “Pull yesterday’s analytics into a sheet” | | Multi-step workflows | “Find leads, enrich them, push to my CRM” |

Practical Evaluation Checklist

Setup

• [ ] Install the Chrome extension from the Chrome Web Store
• [ ] Create a free Axiom account at axiom.ai
• [ ] For cloud runs: generate an API token from the dashboard
• [ ] For code access: npm install axiom-api (Node.js)

First no-code automation

• [ ] Open the builder and add a “Go to URL” step
• [ ] Add an extraction step using CSS selector or text match
• [ ] Set a trigger (manual, schedule, or webhook)
• [ ] Run and verify output

First code automation

export AXIOM_API_KEY="your-token-here"
node -e "
const { chromium } = require('playwright');
// connect to Axiom cloud browser
"

Monitoring runs

• [ ] View execution history in the Axiom dashboard
• [ ] Inspect screenshots captured at each step
• [ ] Check step-level timing and error logs

Security Notes

• API tokens are required for all cloud API calls — never commit them to source code
• Self-hosted mode processes all data locally in your browser; Axiom states they do not store automation results on their systems
• The Chrome extension needs permission to read and modify page content — review the permissions before installing
• Data processed through cloud runs is subject to Axiom’s privacy policy and terms of service

FAQ

Q: How is Axiom different from Selenium or Puppeteer? A: Selenium and Puppeteer are code-first libraries that run locally or on your own servers. Axiom adds a no-code visual builder layer, a cloud-hosted browser fleet, and a Claude-powered natural language interface on top of standard CDP — giving non-developers a path in while keeping the code-first exit ramp.

Q: Can I run Axiom without the cloud? A: Yes. Axiom supports self-hosted mode where the automation runs on your own machine and browser. Your data does not leave your environment in this mode.

Q: Does it work with frameworks other than Puppeteer? A: Yes. Since it uses Chrome DevTools Protocol (CDP) over WebSocket, any CDP-speaking client works — Playwright, raw CDP clients, or even Chrome DevTools itself.

Q: Is there a free tier? A: Axiom’s website mentions “Free to install. Get started in minutes.” Specific plan limits, pricing tiers, and usage quotas should be confirmed on the pricing page at axiom.ai/pricing.

Q: What happens if the automation fails mid-run? A: The dashboard provides per-step screenshots and error logs. You can re-run from a specific step or the beginning. Scheduled runs can be configured to retry on failure.

Conclusion

Axiom.ai occupies an interesting middle ground in the browser automation space. It is not as developer-centric as a raw Puppeteer script, but not as limited as pure no-code RPA tools either. The three-layer approach (no-code builder, Chrome API, Claude natural language) means you can start with a visual workflow and drop into code when you hit the walls of the builder.

For developers already using Playwright or Puppeteer, the Chrome API provides an infrastructure alternative — Axiom handles the browser fleet management while your code stays the same. For non-technical users, the builder and Claude integration lower the barrier significantly.

If you need browser automation and want flexibility without building your own infrastructure, Axiom is worth evaluating.