Monetize your Browser Automation MCP server every rendered page costs you something. Charge for it.

A free local server like playwright-mcp externalizes its cost — the user's machine runs the browser. The moment you host, that cost is yours: instances, proxies, anti-bot measures, session storage. Free hosted browsing collapses under its own success, which is why no one offers it for long.

Per-call pricing is the only model that scales with the workload. An agent that renders one page pays for one page; an agent that runs a thousand scraping sessions pays a thousand times. Because x402 settles before your handler runs, even adversarial traffic — the curse of every browser farm — pays its way or never executes.

The cleanest unit is the rendered page. A fetch-and-extract call of the kind WebPeel performs — one URL in, clean Markdown out — has predictable cost and prices comfortably in the $0.01–$0.05 range.

Sessions are the second tier. An interactive multi-step flow — navigate, log in, click, extract — occupies a browser for minutes, so composite session tools reasonably price from $0.10 upward. Artifacts are the third: a pagecast-style recording of a page as GIF or video, or a cross-browser test pass on real devices through something like the BrowserStack MCP's domain, produces a durable deliverable that can carry a dollar-plus price. Map your tools to those three tiers and the pricing mostly writes itself.

There are 54 live Browser Automation servers on the Loomal index. Claim yours with a GitHub ownership check, then set per-call prices in the console — one field per price, changeable any time without touching your deployment.

In front of your remote endpoint, the x402 middleware does the gatekeeping: unpaid calls receive an HTTP 402 with the price, paid calls execute and return an Ed25519-signed receipt. Loomal's platform fee is 5% on settled transactions, currently waived.

Monetizing doesn't mean paywalling your repo. Chrome-driving tools that run against the user's own browser should stay free — that's your distribution and your reputation. The paid product is the remote endpoint where you absorb the infrastructure burden: maintained Chromium versions, rotating proxies, session isolation.

Autonomous agents will choose the paid remote endpoint every time, because it's the only one they can reach. An agent mid-task has a wallet, not a laptop with your extension installed.