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 actually happened, why it matters, and what the resulting infrastructure — the pay: namespace and the FAS-1 protocol — is built to do.

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 — human-typed or machine-generated. 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. A deterministic router chooses the optimal rail by cost, speed, and availability. No ML, no probabilistic scoring — just rules.
4. Settle. The instruction is dispatched as ISO 20022 compatible data on the chosen rail. Today XRPL is live on mainnet; ACH, FedNow, and SWIFT live behind adapter interfaces.

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. 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, 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. No human keyed in the destination — it came from resolution.
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.

What is significant is not the dollar amount. It is that the address was discovered through a name resolution layer rather than copy-pasted by a human, and that the policy was enforced by code rather than by a person clicking "Approve."

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 not themselves FAS-1 anchors — they are agent-to-agent payments that demonstrate the rail. But they sit inside the same operational envelope: deterministic routing, ISO 20022 compatible payloads, and adapter-isolated rails so the codebase never crosses the line into being a bank.

What comes next

The Founding Tier is open. The send-to-alias endpoint is live on mainnet — the first real production send-to-alias from a registered name landed on day 43. Multi-rail adapters for ACH and FedNow exist behind interfaces and will switch on as bank partners come online; the first attempt at fiat onboarding (Column Bank) was rejected by their risk team in March 2026, and that path is being reworked through alternative partners.

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. No banking license needed on either side, because the layer never holds funds — it resolves and routes.