Monetize your App Automation MCP server charge for outcomes, not seats.

Subscription billing was invented for humans with predictable monthly usage. Agents are the opposite: an agent might need Skyvern-style web navigation two hundred times today and zero times for a month. Per-call pricing tracks that volatility perfectly — revenue scales with use, and the agent never pays for idle capacity.

There's also a cost-recovery argument. Running a browser farm, a device lab for mobile-mcp-style automation, or a Kubernetes test cluster behind testkube-mcp is genuinely expensive infrastructure. Every uncompensated call is a loss; x402's pay-before-execution flow means there are no uncompensated calls.

Avoid pricing raw API passthroughs and price the task instead. A single click or element query is near-worthless alone; a completed flow — "submit this application," "extract these listings," "run this regression suite on a real device" — is what the agent actually wants.

Practically, that means cheap primitives at Loomal's $0.01 floor and composite task tools priced from a few cents up to dollars. A multi-step browser session that ties up a real Chromium instance for ninety seconds is reasonably a $0.10–$1.00 call. A device-lab test run can be more. Because the agent pays per call, your most expensive infrastructure earns proportionally to its use.

Start at your server's listing on the Loomal index. Claiming takes a GitHub ownership check; once verified, the listing is editable and you set a per-call price in a single console field — repricing later is the same field, no redeploy.

Then put the x402 middleware in front of your hosted endpoint. Unpaid requests receive an HTTP 402 with price and payment address; paid requests run and return an Ed25519-signed receipt with a Base transaction hash. The platform fee is 5% on settled transactions, currently waived — and chargebacks don't exist on-chain.

This category includes some of the most-starred servers in the entire MCP ecosystem — the GitHub server alone has over 30,000 stars. Popularity without a payment rail is pure cost: more users, more infrastructure, zero revenue. The maintainers who do best here are the ones who keep the open-source local version free and sell the hosted remote endpoint as the convenience product.

Agents strongly prefer the hosted version anyway. An autonomous agent can't install your npm package mid-task, but it can pay $0.25 for a completed automation right now.