Nevermined supports
MPP alongside x402.
MPP, the Machine Payments Protocol, is a challenge-and-credential payment protocol: your endpoint answers with a standard HTTP (the web's request protocol) challenge, the agent presents a payment credential, and the charge settles by card or on chain. Nevermined supports it as a first-class protocol next to x402, in line with AP2 (Google's Agent Payments Protocol) and the other emerging agent commerce standards.
The whole payment runs inside standard HTTP headers.
MPP extends RFC 7235, the HTTP authentication standard, with a "Payment" scheme. Four steps, and no extra services to run.
Agent sends request
A standard HTTP call to a paid endpoint. No key, no pre-negotiation.
Server responds 402
An RFC 7235 “Payment” challenge with the accepted methods, price, and network.
Agent presents credential
The payment library selects a method, builds a credential, and retries the request.
Agent gets the resource and a receipt
The server verifies, settles, and returns the resource with a payment receipt.
MPP runs on our backend today, and SDK support comes next.
MPP settlement is built on the Nevermined backend today: the challenge, verify, and settle path runs by card and on the Tempo chain, settling in USDC.e or EURC.e on Tempo. SDK support lands next, and when it does you reach MPP the same way you reach x402: same client, same dashboard, same analytics.
One gateway handles both protocols
Our gateway dispatches x402 and MPP through a single handler interface and detects which a merchant speaks from its 402 header.
It settles by card or on chain
MPP settles on a card inside a spend mandate its owner set, or as a native Tempo-chain transaction in USDC.e or EURC.e. Together with x402, that covers every way your agents need to pay.
You build it the same way as x402
When MPP reaches the SDK it works just like x402: the same calls and the same monitoring, nothing new to learn.
