x402 vs MPP, explained.
x402 and MPP both revive an http status code that sat dormant since 1997. each one standardizes a different slice of the same flow.
x402, built by
@coinbase, settles every request onchain with stablecoins. an agent hits a 402, signs a USDC payment on
@base or
@solana, retries, and receives the resource. no processing fees beyond gas make it the efficient rail for high frequency machine to machine calls.
MPP, from
@stripe and
@tempo, generalizes the 402 pattern into a rail agnostic framework. its session primitive lets an agent preauthorize a spending limit and stream micropayments without an onchain transaction per interaction. cards, stablecoins, and any future method plug into one negotiation flow. MPP clients can even consume existing x402 services without changes.
the two protocols are production ready, and serious agent platforms will end up speaking both. each spec ends its job at settlement, and governance begins right above that line. which agent spent what, under whose authority, against which policy, with what audit trail. payment rails standardize how money moves between machines. controls determine whether a given payment should happen at all.