AI payments on XRPL: activity and evidence

Loading the research data…

x402 connects HTTP requests and payment

x402 is an open protocol for payment requirements in an HTTP exchange. A server can respond with HTTP 402 and payment instructions; a client submits payment information, and verification and settlement are part of the service workflow. It can support software clients as well as people.

The protocol’s HTTP transport defines payment-related headers and payloads. The chain, asset, facilitator, price, and service need to be checked for the particular implementation. The existence of an x402 integration is not a guarantee of universal compatibility or secure execution.

What the live tracker reads

This page fetches the public XRPL AI Hub mainnet index. It reports the selected aggregate window, the index’s as-of time, merchant labels, and recent transactions. The time series may cover a shorter period than the all-history aggregate, so its starting time is shown separately.

The current source identifies the t54 facilitator with SourceTag 804681468. A total labeled as indexed transactions describes the feed’s coverage. It is not a census of every AI service or every economic payment on XRPL.

Keep asset quantities separate

Native XRP volume is expressed in XRP. The RLUSD rows are accepted only with the documented issuer address rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De. A matching ticker from a different issuer is not the same asset.

Adding 10 XRP to 10 RLUSD would produce a meaningless mixed-unit total. The tracker does not do that, and it does not label an asset quantity as a current USD value. A count of transactions also does not establish revenue, unique paying people, or the price of an off-chain service.

A tag is a routing hint, not proof of intent

A SourceTag is a sender-set informational field. It does not cryptographically prove that an AI agent initiated a payment or that a named merchant delivered a service. The source’s merchant label is also an index attribution, not independent identity verification.

The recent-payment table shows whether the tag matches and whether the index itself asserts verified intent. Those are separate checks. If the verification flag is false, the page preserves that fact rather than turning the tag into proof.

Inspect an individual transaction

Open the linked transaction in a ledger explorer. Check the validated result, network, source and destination, transaction type, tag, and actual delivered asset. Compare them with the service’s own signed receipt or request record if you need to establish what was purchased.

To evaluate adoption, compare repeated observation windows and look at transaction sizes, concentration, distinct destinations, and the source’s coverage. An impressive cumulative count can coexist with tiny payment amounts or a small number of active services.

Keep exploring