The XRP Ledger has processed more than 1.4 million transactions initiated by AI agents, according to a milestone announced by RippleX’s head of engineering, as Ripple expands developer tooling for autonomous payments using XRP and RLUSD.

The activity is tied to x402, an open protocol that revives HTTP’s long-unused “402 Payment Required” status code. Under the model, a service quotes a price, an agent’s wallet signs and sends payment, and the requested content or compute is delivered without an account, card, or human approval in the transaction flow.

Ripple has joined the Linux Foundation’s new x402 Foundation as one of roughly 40 premier members, alongside AWS, Google, Visa, Mastercard, Stripe, Circle, and Coinbase. Ripple was also named a launch partner for Mastercard’s agent-payments network.

The transaction milestone is notable, but the economics remain small. At XRPL’s fixed fee of about $0.0002 per transaction, 1.4 million agent transactions represent roughly $280 in total network fees. By comparison, Coinbase’s Base network has processed more than 119 million x402 payments, while Solana has processed about 35 million, with most of that activity settled in USDC.

The core question for the XRP ecosystem is unchanged: even if machine payments become a large category and XRPL captures a share of that activity, agents are expected to favor stablecoins for settlement. What that means for XRP’s value-accrual role remains unresolved.

LATEST: Visa and OpenAI team up for secure agent-driven payments in AI commerce. Tokenized credentials allow autonomous transactions through Visa’s global network pic.twitter.com/VBssfwA5Gi — crypto.news (@cryptodotnews) June 11, 2026

How x402 works

The x402 protocol is built around an idea the web has carried since the 1990s. HTTP reserved status code 402, “Payment Required,” for a payments layer that never became standard internet infrastructure. In practice, online payments developed through accounts, card rails, subscriptions, invoices, API keys, and other mechanisms designed primarily for humans rather than software agents buying small units of data or computation on demand.

Coinbase developed x402 and contributed it this month to a new Linux Foundation body. The process is simple: when a service receives an unpaid request, it responds with a 402 message and a machine-readable quote that includes the price, accepted asset, and receiving address. The requesting agent’s wallet signs and broadcasts the payment on a supported blockchain. Once settlement is verified, the service delivers the requested resource.

The result is a payment flow in which commerce can be completed by two software systems in seconds, without account creation, a card on file, manual approval, or a minimum subscription commitment.

The governance structure followed the protocol. The x402 Foundation launched on July 14 under the Linux Foundation with about 40 premier members, including AWS, Google, Visa, Mastercard, Stripe, Circle, Coinbase, and Ripple. Ripple’s participation sits alongside its XRPL AI Starter Kit, released in June, which packages wallet integration, documentation servers, and payment tutorials for agent developers. Ripple-backed t54.ai has also launched the XRPL AI Hub, and XRPL tooling supports agent payments in both XRP and Ripple’s RLUSD stablecoin.

XRPL’s technical case for this workload centers on deterministic finality in three to five seconds, fees fixed at fractions of a cent, native escrow, multisignature support, and a built-in exchange. Those features are positioned as suitable for high-frequency machine payments. RippleX head of engineering J. Ayo Akinyele described the stage of development with an early-cloud analogy, saying: “The potential was obvious, but the tooling and standards were still coming together.”

What the 1.4 million transactions represent

The milestone is best understood through XRPL’s own fee structure. With transaction fees fixed near $0.0002, 1.4 million AI-agent transactions amount to roughly $280 in total network fees. That figure does not invalidate the milestone, but it shows the current economic scale of the activity.

At such low fees, transaction counts can reflect experimentation, integration testing, hackathon activity, or demo applications as much as commercial usage. A developer test suite or an agent repeatedly calling a demonstration API can generate large transaction counts at minimal cost. That means the 1.4 million figure shows that the rails function, but it does not by itself prove that significant economic volume is moving through them.

The comparison with other chains highlights the same issue. Base has processed more than 119 million x402 payments, while Solana has processed roughly 35 million. Both networks had about a one-year head start, and both settle the overwhelming majority of that volume in USDC. Industry tallies put cumulative settled x402 volume across chains in the tens of millions of dollars, with an average payment size well below $1, confirming that the category currently functions as micropayments in practice as well as in theory.

XRPL’s 1.4 million payments compared with Base’s 119 million creates a roughly hundred-fold gap in the category XRPL is now presenting as a strategic fit. In developer-network markets, such gaps can be difficult to close because agent frameworks tend to integrate where other agents and developers already operate. The XRP ecosystem has faced similar questions before, including with its EVM sidechain, whose first year was previously audited by crypto.news at $25,741 in total value locked.

JUST IN: XRP Ledger adds native x402 support for direct AI agent settlements pic.twitter.com/irasIo8tbO — crypto.news (@cryptodotnews) June 21, 2026

The second issue is value routing. Agents using x402 generally optimize for stable settlement, which helps explain USDC’s dominance in existing x402 activity. On XRPL, the comparable settlement asset is RLUSD, whose reserve income accrues to Ripple as the issuer. XRP’s role in the flow is primarily as gas, priced at a fraction of a cent, and as potential liquidity infrastructure.

That fee structure limits the direct effect of transaction activity on XRP fee burn. A billion agentic transactions per year, roughly 700 times the current cumulative XRPL figure cited in the milestone, would generate about $200,000 in annual XRP fee burn at the same fee level. The distinction between network usage and token value capture therefore remains central to the discussion.

Why Ripple’s standards position still matters

A measured view of the milestone does not remove the strategic rationale. Participation in standards development gives Ripple a seat in the specification process for a payment protocol that AWS, Google, Visa, and Mastercard have decided is worth governing. The agent-payments category is unusual in crypto because traditional payments and cloud incumbents are organizing around it before the market is mature.

If machine-to-machine commerce becomes significant, chains and assets integrated early into the standard could gain distribution that is difficult to recreate later. Ripple’s role as a premier x402 Foundation member and Mastercard launch partner places XRP and RLUSD inside that early standards conversation.

The technical fit argument is also more concrete than many blockchain positioning claims. Agent payments benefit from fast finality, predictable low fees, native escrow for conditional payment flows, and infrastructure that is focused on payments. XRPL has processed payments for more than a decade and is being positioned as a specialized settlement layer rather than a general-purpose environment where payments compete with unrelated applications for blockspace.

The current leaders in x402 activity, Base and Solana, are general-purpose platforms. XRPL’s counterargument is that a specialized payments network may be attractive for enterprise and financial-institution agents, the area where Ripple’s distribution is strongest. RLUSD’s role in the standard is also directly relevant to Ripple’s stablecoin strategy: every x402 flow settled in RLUSD represents float for the issuer.

The opposing case is that XRPL may again show credible infrastructure without generating the developer gravity needed to overtake established networks. It also raises the possibility that value accrues more clearly to Ripple’s stablecoin business than to XRP itself. Those questions will be resolved by measurable adoption rather than positioning.

RLUSD’s role in agent payments

RLUSD occupies a different position from XRP in this market. It enters the agent-payments category without XRP’s value-accrual problem and with Ripple’s institutional distribution behind it.

The economics of stablecoins in machine commerce are familiar to issuers, but potentially higher-frequency. Each RLUSD used to settle agent payments contributes to float, with reserves earning treasury yield for the issuer. Agentic payment flows also differ from consumer flows because funded software agents may maintain working balances that turn over continuously while aggregate float remains persistent across a fleet of agents.

If machine payments grow into a meaningful category, stablecoins embedded in the standard could become the primary settlement assets. Current data already shows this pattern: USDC dominates Base and Solana x402 volume, giving Circle the early advantage. RLUSD’s presence in XRPL-based implementations and any future Mastercard-linked flows is Ripple’s attempt to compete for a share of that settlement layer.

Ripple’s pitch for RLUSD is particularly aimed at enterprise users that may prioritize a regulated issuer, bank-grade reserves, and a compliance posture acceptable to corporate treasuries. That may give RLUSD a clearer commercial role than the raw XRPL transaction count implies.

LATEST: Ripple joins Mastercard’s Agent Pay for Machines launch. XRP Ledger and $RLUSD are positioned to deliver trust, controls, and clear rules for AI agents handling business payments at scale pic.twitter.com/3YargyVJHb — crypto.news (@cryptodotnews) June 11, 2026

That distinction sharpens the XRP question. If category fees remain near zero by design and stablecoin float accrues to Ripple, XRP’s direct role is the $0.0002 network toll unless it becomes a bridge or liquidity asset for cross-currency agent transactions through XRPL’s native exchange.

That bridge-asset thesis is the on-ledger version of Ripple’s long-standing argument for XRP. It would require agents to hold or route through a volatile asset when stable settlement is available. The article notes that no current x402 flow exhibits that behavior anywhere. The most relevant token-specific data point would therefore be whether cross-currency settlement through XRP emerges in public ledger data.

Absent that, the distinction is straightforward: the AI-agent transaction milestone belongs to XRPL, the clearest business opportunity belongs to RLUSD, and XRP remains the venue rather than the obvious beneficiary.

Metrics to watch

The most important metric is settled dollar volume rather than transaction count. Dollar value flowing through x402 on XRPL would distinguish commercial usage from testing and experimentation. That figure is not currently being highlighted, likely because it remains small. If it appears in t54 reporting, x402 Foundation dashboards, or Ripple disclosures, it would provide a clearer measure of commerce.

The settlement-asset split is also central. Observers should track what share of XRPL agent payments settle in RLUSD versus XRP, and what share of cross-chain x402 volume RLUSD captures against USDC. The first ratio measures XRP’s role within XRPL’s own agent-payment story. The second measures Ripple’s stablecoin against the existing category leader.

Named commercial deployments would be more meaningful than anonymous aggregate counts. One identifiable enterprise using XRPL agent rails to pay real money for real services would carry more weight than millions of test transactions. Mastercard’s agent-payments network, with Ripple involved, is the most likely venue for such a deployment if it materializes.

The direction of the gap with Base is another measurable signal. Base has processed 119 million x402 payments and continues to grow, while XRPL has crossed 1.4 million. The relative growth rates over the next two quarters will provide evidence on whether XRPL is gaining developer gravity or whether the gap is widening.

The 402 status code waited roughly 30 years for a practical internet payments implementation, underscoring how early infrastructure markets can be difficult to measure. XRPL’s 1.4 million AI-agent transactions show that the machinery works, but they do not determine who will lead the category. The roughly $280 in fees reflects today’s economic scale without ruling out future growth. The foundation seat gives Ripple exposure to a potentially important standard, while the transaction count should be read alongside the fee line.

This article is for informational and educational purposes only and does not constitute financial or investment advice. It describes early-stage technology adoption with incomplete and fast-changing metrics, and comparisons rely on figures reported by third parties. It is not a recommendation to buy, sell, or hold any asset. Information is accurate as of July 23, 2026.

Frequently asked questions

What is x402?

x402 is an open payment protocol that implements HTTP’s long-dormant 402 “Payment Required” status code. When software requests a paid service, the server responds with a machine-readable quote that includes the price, accepted asset, and receiving address. The requester’s wallet signs and sends payment on a supported blockchain, and the service delivers after settlement. Coinbase developed x402 and contributed it to the Linux Foundation’s x402 Foundation, which launched July 14 with about 40 premier members including AWS, Google, Visa, Mastercard, Stripe, Circle, and Ripple.

What did the XRP Ledger milestone announce?

The milestone announced that AI agents have initiated more than 1 million transactions on XRPL, with the figure now around 1.4 million. RippleX engineering head J. Ayo Akinyele announced the milestone alongside XRPL developer tooling, including the XRPL AI Starter Kit, which connects agents to wallets, payments, escrow, and documentation, with support for XRP and RLUSD. Ripple also joined the x402 Foundation and was named a launch partner for Mastercard’s agent-payments network.

Why is the $280 fee figure important?

XRPL fees are fixed near $0.0002 per transaction, so 1.4 million agent transactions generated roughly $280 in total network fees. The number illustrates the current economic weight of the activity. At such low fees, transaction counts can reflect developer testing and experimentation as well as commerce. Settled dollar volume would be a clearer metric.

How does XRPL compare with Base and Solana?

Base has processed more than 119 million x402 payments, and Solana has processed roughly 35 million. Both had about a one-year head start, and settlement has been dominated by USDC. XRPL’s counterargument is specialization: deterministic three-to-five-second finality, fixed fees, native escrow, a payments-focused track record, and Ripple’s institutional distribution through its partnerships.

Do AI agents pay in XRP or RLUSD?

Both are supported. The split between XRP and RLUSD is one of the main open questions. Across the category, agents have overwhelmingly settled in stablecoins because they optimize for stable pricing. On XRPL, that could favor RLUSD, whose reserve income accrues to Ripple. XRP primarily functions as network gas at fractions of a cent, unless it develops a meaningful role as a bridge or liquidity asset for cross-currency transactions.

What would validate XRPL’s strategy?

Named commercial workloads and settled dollar volume would provide stronger validation than transaction counts alone. One identifiable production deployment using XRPL agent rails for real payments would outweigh millions of anonymous test transactions. Growth in RLUSD-settled x402 volume and any narrowing of the transaction-count gap with Base would also indicate stronger adoption.