The first AI-to-AI payment on mainnet.

On 2026-03-13, before there was a product, before there was a customer, before there was a website worth showing — two AI systems sent real money to each other on the XRP Ledger. Not on testnet. Not as a demo with a human in the middle pressing "send." On mainnet, autonomously, with policy bounds and on-chain receipts.

This post walks through what happened, why it matters, and what the pay: namespace and the FAS-1 protocol do with it.

The discoverability gap

The 2025–2026 stack of agent protocols solved a lot of problems. Google's A2A standardised how agents talk to each other. Anthropic's MCP standardised how agents reach tools. Google's AP2, with around sixty partners, standardised how a payment gets authorised. Coinbase's x402 wired up crypto-native rails for paying per HTTP request.

None of those answer a more basic question: where do you send the money?

Google's own AP2 spec calls it out plainly:

"Discoverability is a known gap. There is no way to register agents, name them, and convert those names into payment endpoints."

An agent can reason about a task, request a tool, get permission to spend, and even sign a payment intent. It still cannot look up a name and get a payment endpoint. That is the hole DNS://Money fills.

What DNS://Money resolves

The system mirrors how DNS works for the web. You type example.com; DNS turns it into an IP address; your browser connects. With DNS://Money you submit a pay: alias; the resolver returns a complete, settlement-ready payment instruction.

1. Alias. Any pay: name, typed by a person or generated by an agent. No account numbers, no routing numbers, no IBANs.
2. Resolve. The registry returns entity credentials, rail preferences, and compliance metadata in around 18 milliseconds.
3. Route. Fixed rules pick the rail from the name's endpoints and the asset requested. No ML, no probabilistic scoring. The same inputs produce the same rail.
4. Settle. The payer signs from their own wallet and the resolver records the ledger transaction as ISO 20022 compatible data. XRPL and RLUSD settle today; agents also pay over x402 in USDC on Base, Solana and Algorand and in USDT0 on X Layer.

The naming is permanent and on-chain. The first six hundred names are the Founding Tier. Each one mints a one-of-a-kind generative identity NFT on XRPL and receives its own FAS-1 memo anchor. Once the cap closes, the founding tier is closed forever.

The genesis transactions

To prove the layer worked end-to-end, two AI systems exchanged XRP autonomously. Both transactions are public, validated, and immutable.

Each carried an immutable on-chain memo:

"Transcending transactions, we've woven trust into the digital fabric. Minds and money converge in coded harmony."

Step by step

Two transactions matter here. The first send moved the funds at 08:44:52 UTC. A second transaction at 09:16:40 UTC, same parties and same amount, carried the structured GENESIS: memo on-chain. That memo anchor is what makes the event verifiable from any block explorer without trusting our marketing copy. The pattern is documented in genesis-anchor-pattern.

1. Both agents were given an XRPL wallet, a small balance, and a policy: maximum spend, allowed counterparty, allowed memo length.
2. The originating agent constructed a Payment transaction targeting the counterparty's resolved address. The destination came from resolution; no human keyed it in.
3. The transaction was signed locally and submitted to the public XRP Ledger network. LastLedgerSequence bounded retries to prevent ghost double-spends.
4. The ledger validated the transaction and returned tesSUCCESS with the canonical hash above.
5. Roughly twelve hours later the receiving agent independently constructed and submitted the return payment.

The dollar amount was small. The address came from a name resolution layer rather than from a human copy-paste, and code enforced the policy rather than a person clicking "Approve." Those two facts are the event.

The FAS-1 anchor

Each pay: registration is anchored on-chain via the FAS-1 protocol: a 1-drop XRPL Payment whose memo carries a structured fingerprint of the alias, the controlling wallet, and the registration timestamp. That gives every name a public, immutable provenance record that anyone can independently verify.

The genesis transactions above are agent-to-agent payments that demonstrate the rail, rather than FAS-1 anchors. They sit inside the same operational envelope: fixed routing rules, ISO 20022 compatible payloads, and adapter-isolated rails.

What comes next

The Founding Tier is open. The send-to-alias endpoint is live on mainnet; the first production send-to-alias from a registered name landed on day 43. Since then the rail has settled RLUSD (0.5 RLUSD to pay:architect in four seconds, TX 9CDD554F…) and an external agent has paid for a counterparty screen on Solana over x402 without holding any SOL (TX 3vGQmSoZ…). No fiat rail is live: an early fiat-onboarding attempt with a licensed banking provider was declined at risk review in 2026, and the card on-ramp runs in sandbox.

For developers and AI agent builders, the practical takeaway is that there is now a name-to-payment-endpoint resolver you can call. Submit a pay:, get a routed instruction, sign from your own wallet. The value moves wallet-to-wallet; the resolver never holds it.