Artem Voloskovets
MPP allows AI agents to autonomously pay for APIs, data, inference and compute using XRP or RLUSD without exposing private keys to the AI model. The software is currently in beta.
How It Works
MPP uses the HTTP 402 Payment Required flow:
Agent requests resource → service returns price → agent authorizes payment → XRPL settles payment → service delivers resource.
Supported payment modes:
- XRP: single payments and ongoing payment sessions.
- RLUSD: single payments.
- Other XRPL assets: IOUs and Multi-Purpose Tokens can be used for single payments.
- XRP sessions: use XRPL Payment Channels.
- RLUSD sessions: require a proposed XRPL upgrade and are not currently available.
Standard XRPL transactions typically settle in roughly 3–5 seconds.
XRP Payment Sessions
For repeated payments, XRP can use Payment Channels instead of recording every API request on-chain. The agent opens a channel, signs payment claims off-chain as services are consumed, and closes the channel when the session ends.
This reduces the blockchain interaction to:
- Open Payment Channel.
- Exchange signed payment claims off-chain.
- Close and settle the channel.
RippleX says payment-channel vouchers can be signed at 100,000+ per second.
Private Keys Stay Outside the Agent
v1.1 adds support for the Open Wallet Standard (OWS). The AI agent requests transactions through a wallet interface rather than receiving the wallet's private key. Developers can apply policies such as:
- maximum spending limits;
- approved destination addresses;
- transaction restrictions.
Keys remain in an encrypted wallet environment and are used only for signing.
A service returns a 402 status with a price, the agent authorizes payment, and the resource is delivered. — RippleX Developers
v1.0 vs. v1.1
| Feature | v1.0 | v1.1 |
| X402 | Yes | Yes |
| MPP | No | Yes |
| XRP payments | Yes | Yes |
| RLUSD payments | Yes | Yes |
| MPP XRP sessions | No | Yes |
| MPP RLUSD sessions | No | Not yet |
| Open Wallet Standard | No | Yes |
| Local XRPL environment | No | xrpl-up |
| MPP SDK | No | xrpl-mpp-sdk beta |
The previous Starter Kit focused on X402 payments with XRP and RLUSD. v1.1 adds MPP rather than replacing X402.
RLUSD Limitation
RLUSD works for individual MPP payments but not ongoing payment sessions. XRP sessions use native XRPL Payment Channels. Extending Payment Channels to issued assets such as RLUSD requires the proposed XLS-93d ledger upgrade.
So the current implementation is:
- XRP: single payments + payment sessions
- RLUSD: single payments only
New Developer Tools
The update adds xrpl-mpp-sdk, a beta SDK for handling MPP's HTTP 402 flow, payment credentials and sessions. It also adds xrpl-up, a local XRPL development environment with pre-funded accounts and instant ledger closes. Developers can test payments, trust lines, escrows, Payment Channels, AMMs and MPTs without relying on the public Testnet.
The resulting stack can be summarized as:
AI agent → policy-controlled wallet → MPP/X402 → XRP or RLUSD → XRP Ledger
The main technical change in v1.1 is therefore not a new cryptocurrency payment method. It is the addition of MPP, controlled wallet access and session-based XRP micropayments to the existing XRPL AI tooling.
Artem Voloskovets
