Pay-Per-Use Pricing

Pay-per-use pricing ties what a customer pays directly to what they consume. Instead of a flat monthly fee that buys an entitlement, the seller defines a unit of usage and a price per unit, and the bill is simply units consumed times price. Cloud computing normalized the model — paying per GB stored or per second of compute — and LLM APIs extended it to tokens.

The defining property is alignment: cost tracks value delivered. A customer who consumes nothing pays nothing; a customer who consumes heavily pays proportionally.

The unit is the central design decision. It should map to something the buyer recognizes as value and the seller can meter honestly: a search query, a page scraped, a document parsed, a thousand tokens processed, a row of data returned. A unit that is too coarse (per month) recreates the subscription problem; one too fine (per byte) becomes illegible to the buyer.

For tools exposed over MCP, the natural unit is usually the tool call itself — which is why per-call pricing is the most common form of pay-per-use in the agent economy, though it is not the only one.

Subscriptions trade fairness for predictability. The seller gets recurring revenue and the buyer gets a known bill, but light users subsidize heavy ones and every new customer must clear an upfront commitment hurdle before consuming anything.

Usage-based pricing removes the hurdle and the cross-subsidy at the cost of revenue predictability for the seller and bill variability for the buyer. In human SaaS, that variability is a real objection. For software buyers — agents operating under a wallet budget — it is far less of one, because the budget itself caps exposure and every unit consumed was explicitly chosen.

An agent working through a task touches many tools sporadically: a few calls here, one call there, often against services its operator has never used before and may never use again. Subscription signup is a wall an autonomous process cannot easily climb — it involves forms, emails, and cards. Metered access via x402 removes the wall entirely: the agent encounters a price in an HTTP 402 response, its wallet pays in USDC, and settlement completes on Base in about two seconds.

Consumption-based pricing also keeps incentives clean on the seller's side. Revenue scales with the load the seller actually serves, so there is no pressure to throttle heavy users behind quotas the way flat-fee plans require.

MCP servers monetized through Loomal use pay-per-use in its per-call form: the owner sets one USDC price per call, with a minimum of $0.01, and repricing is a single field in the console. Loomal applies a 5% fee on settled transactions, currently waived, and every settled call produces an Ed25519-signed receipt the buyer can audit.