Ripple joins x402: XRP Ledger, RLUSD, and what it means for API providers

What Ripple actually shipped for x402

Through June 2026, Ripple moved the XRP Ledger into agentic payments in three steps. First, on June 10–11, it published the XRP Ledger AI Starter Kit — a developer bundle with an XRPL Docs MCP server, two Claude skills for wallet and payment operations, and an integration with the x402 machine-payments standard. Thanks to a contribution from Ripple partner t54, XRPL became a supported chain in x402, with payments settling in XRP and RLUSD. On June 21, Ripple flagged native x402 support on the ledger for direct AI-agent settlements.

Then came the milestone. On July 8, 2026, XRP Ledger agent payments crossed 1 million as t54.ai launched the XRPL AI Hub — the first ecosystem platform for agentic commerce on the ledger. The hub shipped with "x402 Secure," a trust layer on top of the base protocol that adds programmable verification and risk gating and integrates Mastercard's Verifiable Intent credentialing, so payments carry authenticated, consent-bound authorization before they settle on-chain. Ethereum-based agent platform Virtuals.io was named the launch partner, with its agents transacting natively on XRPL and settling in XRP and RLUSD.

RLUSD is the piece to watch. Ripple's regulated dollar stablecoin has passed $1.7 billion in circulation, the majority of it living on the XRP Ledger itself. Positioning RLUSD as the settlement instrument for agent traffic is the whole strategy: the analysts covering the move expect RLUSD to handle most settlement flows, while XRP earns from fees, liquidity routing, and reserve requirements.

Why one more chain joining x402 is a big deal

Ripple did not arrive first, and that's exactly why this matters. x402 launched in May 2025 on Base and Solana; XRPL only joined in June 2026. Coinbase says x402 has now processed roughly 160 million agentic payments, and Chainalysis tracked the standard crossing 100 million transactions on Base alone. Against Base's volume, XRPL's first million is tiny. But the direction is the story: when the company that spent a decade selling banks on cross-border settlement decides the open web standard for machine payments is worth adopting, x402 stops being a Coinbase experiment and starts looking like internet plumbing.

Stack the last few weeks together and the convergence is hard to miss. Cloudflare launched a Monetization Gateway built on x402. AWS wired Coinbase's x402 into CloudFront. Google's Agent Payments Protocol (AP2) uses x402 as its stablecoin rail. Visa added x402 support through its Trusted Agent Protocol, and Stripe through its Agent Commerce Protocol. Now Ripple brings a third major chain and a second regulated stablecoin. Different companies, one conclusion: the unit of commerce is shrinking from a checkout to a single API call, and the payer is increasingly a machine.

For anyone who runs an API, that convergence is the opportunity — and the trap. The opportunity is that agents will soon expect to pay for what they consume, in stablecoins, per request. The trap is assuming you have to choose a camp: Base or Solana or XRPL, USDC or RLUSD, this network or that one. You don't. x402 is the layer they all speak.

The rails are multiplying — but who lets agents pay your API?

Here's the gap Ripple's news doesn't close. The XRPL AI Hub, Cloudflare's gateway, Google's AP2, Mastercard's Verifiable Intent — these are rails and trust layers for agents to move money and prove authorization. None of them automatically turns the API you already run into something an agent can discover, get quoted a price for, pay, and call — without you writing settlement code, holding a wallet you didn't want, or onboarding into a specific chain's program.

If you sell data, inference, search, scraping, enrichment, or any metered API, the old path to charging an agent is ugly: issue API keys, run a billing system, reconcile invoices, chase fiat payouts, and eat card fees and chargeback risk on micro-amounts that don't cover the processing cost. Cards were never designed for a $0.002 call made ten thousand times an hour by a bot. That mismatch is precisely why machine-native, stablecoin settlement is winning — and precisely where most API providers are stuck waiting for "someone" to make it turnkey across whichever chain their agents happen to use.

Where Payzum fits: charge AI agents over x402, no code

Payzum is the middleware/proxy that sits in front of your existing API and makes it payable by agents over x402 — the same standard Ripple, Coinbase, Cloudflare, Google, and the rest are converging on. You don't implement a protocol and you don't become a payments company. You configure three things in a dashboard: your existing endpoint, your existing API key or bearer token, and a price.

From there Payzum publishes an x402 URL. When an agent calls it, Payzum returns the 402 Payment Required response with the price, settles the payment through an external facilitator (currently Coinbase's), and then proxies the paid call to your real endpoint using your key. The agent gets its answer; the USDC on Base lands directly in the wallet you control. Payzum is non-custodial — it never holds, pools, or controls your money. The settlement is the payment. To be precise: Payzum is the middleware/proxy, not the facilitator, and it settles USDC on Base today rather than every chain in the ecosystem — but because x402 is one open standard, serving it means you're ready for the agents these networks are minting, regardless of where they were funded.

How it works, step by step

1. Connect your endpoint. In the Payzum dashboard, point to the API you already run and paste your existing API key or bearer token. Nothing about your service changes.
2. Set a price per call. Choose what an agent pays per request — fractions of a cent up to whatever your data is worth. Payzum publishes a public x402 URL for it.
3. Agent pays in USDC on Base. When an agent hits the URL, it receives the 402, pays via the external facilitator, and the funds settle straight to your wallet — no chargebacks, no card network in the middle.
4. Payzum proxies the call. Once paid, Payzum forwards the request to your real endpoint with your key and returns the response. You start serving paying agents the same day — and watch every event in your dashboard with signed webhooks.

What this means for API providers, concretely

Ripple's move is another green light. Here's how different builders can act on it right now with Payzum's x402:

• Data & intelligence APIs — sell market data, KYC/enrichment, or proprietary datasets per query to research agents without issuing or policing API keys for anonymous machine callers.
• Inference & model endpoints — meter access to a fine-tuned model or specialized tool by the call, in stablecoins, instead of running a subscription billing stack for bots that come and go.
• Scraping, search & RAG tools — let autonomous agents pay micro-amounts for a search or a fetch, profitably, because there's no per-transaction card fee eating a $0.002 charge.

Pick a chain yourself vs. serve x402 with Payzum

Common objections

"Shouldn't I wait to see whether XRPL, Base, or Solana wins?"

That's the wrong question. The chains compete, but they all speak the same open standard — x402. Serving x402 today means you're ready for agents no matter which ledger funded them, and you're not rebuilding when the leaderboard shifts. Payzum keeps you on the open layer with no lock-in to a single closed program or chain SDK.

"I don't want to hold crypto or run a wallet."

Payzum is non-custodial: funds settle straight to a wallet you control, and you can opt into auto-conversion to a stablecoin (USDC/USDT) for volatility protection. You configure an endpoint and a price — you're not becoming a payments operator or a treasury desk.