Free vs paid browser automation servers the protocol is free; the browser isn't.

For a developer's own machine, free is hard to beat. playwright-mcp automates any page Playwright can reach; Chrome DevTools MCP adds performance traces and network inspection; Tap is built specifically for logged-in tasks using your own Chrome profile, so sessions and credentials stay local. For QA on your own product, scraping your own properties, or agent workflows that ride along with a human's browser, there's no reason to pay anyone.

The constraint is the host. Each of these drives a browser where the server runs — your laptop, your CI box. The browser's identity, IP, and capacity are yours, for better and worse.

Three things break the free model. Concurrency: ten agents can't share one Chrome without trampling each other's sessions, so you're suddenly running a browser farm. Identity: sites that rate-limit, geo-fence, or CAPTCHA-check will profile your single IP quickly — note that browser-mcp advertises CAPTCHA solving and multi-session support precisely because these are the pain points. Statefulness: headless browsers leak memory, hang, and need supervision; keeping a fleet healthy is a genuine ops job.

Hosted browser services exist because of these three problems, and they charge accordingly — typically by session, minute, or subscription tier designed for human procurement.

An x402-priced browser endpoint lets an agent buy exactly one unit of browsing: fetch this page, run this interaction, return the result. The flow is in-band — 402 Payment Required, pay in USDC on Base, settled in about two seconds, handler runs after payment clears, Ed25519-signed receipt back with the response. No account with a browser-infra vendor, no API key, minimum $0.01 per call.

A listing like WebPeel, which returns any page as clean AI-ready markdown with HTTP-to-browser escalation, shows the natural unit: one URL in, one document out. That's a per-call product whether or not a price is attached yet.

Stay free and local when the browsing is low-volume, the sites are cooperative, or the whole point is using your own logged-in sessions. Move to paid per-call when you need concurrency you don't want to host, IPs that aren't yours, or someone else to fight the CAPTCHA war. Move to a hosted subscription only when volume is high and steady enough that per-call cents would exceed a flat fee — and you have a human around to manage the account.

Maintainers running real browser infrastructure behind their server have the clearest pricing story in this category: your costs scale per session, so charge per call above them. Claim the listing on Loomal; the 5% fee on settled transactions is currently waived.