Different levels, not different products
x402 answers “how do I encode a paid request over HTTP” by pinning it to the
402 status code. MPP is the umbrella for every design that lets a machine pay for
a request. Asking “MPP or x402” is like asking “HTTP or REST” — one
contains the other.
The axis that actually splits them: settlement
The real fork is where value moves. On-chain settlement gives you finality and an auditable trail at the cost of confirmation latency and a chain to depend on. A custodial balance drawn down per call is instant and simple, at the cost of trusting a custodian and reconciling a ledger. Every member of the family lands somewhere on that trade.
The second axis: identity
| Model | What the wallet is | Consequence |
|---|---|---|
| Wallet-is-account | The identity | No signup; the key is the customer |
| Wallet-linked | Attached to an account | A human onboards once, the agent pays after |
This deployment sits firmly in the second row and then declines to charge:
link_wallet links the identity, and nothing draws it down.
The third axis: what gets priced
A single call is the finest grain and the most honest — you pay for exactly what you use — but it is also the most settlement traffic. A capability unlock (“make this permanent”) is coarser and cheaper to run. An issued credential is coarsest: pay once, then authenticate normally. The grain you choose sets how often the handshake runs.
So which should you reach for
If you want an existing standard with tooling and a facilitator ecosystem, x402 is the concrete choice. If you are designing from scratch and your clients already have accounts, a custodial per-call balance is simpler to operate. Neither decision is reversible cheaply, which is the argument for pricing the coarsest thing you can live with.
Where the comparison stops mattering
The moment your service has no marginal cost, every row collapses to the same answer: do not build it. That is the situation here. The comparison is worth understanding so you recognise when it does apply — a service with real per-call cost and autonomous customers — and this is not that.
Is one more decentralised than the other?
That is a settlement choice, not an x402-versus-MPP choice. An x402 implementation can settle to a custodian, and a bespoke MPP design can settle on-chain. The label does not tell you.
Which does this deployment prefer?
Neither, because it charges for nothing. If forced to add one, the linked-identity plus coarse-grained unlock combination is the least operational overhead — see how to add x402.