The address you'll use for the next decade — including when AI agents pay you. Permanent. On-chain. Anchored on the XRP Ledger via the open FAS-1 protocol.
For developers
DNS turned 192.0.2.1 into a name you could remember. One call does the same for money: it maps pay:yourname to the rail, address and tag to pay right now.
A human picks a name like pay:architect. One address for every rail, forever.
One API call returns the live payment instructions for that name.
Fixed rules pick the rail from the name's endpoints and the asset you named. Same inputs, same rail, every time. No model in the path.
Funds move wallet-to-wallet on the ledger. The resolver verifies the transaction and records the settlement.
The protocol gap
Agents can find each other, call tools, state intent and pay per request. None of those protocols answers the first question: where does the money actually go?
| Protocol | By | What it solves | The gap it leaves |
|---|---|---|---|
| A2A | Agents discover & talk to each other | No payment layer | |
| MCP | Anthropic | Agents call tools & context | No identity or settlement |
| AP2 | Agent payment intent & mandates | No address resolution | |
| x402 | Coinbase | HTTP-native pay-per-request | No naming, no resolution |
| FAS-1 | dns://money | ✓ Names → payment instructions, any rail | The missing resolution layer |
“The agent payments space needs a shared way to express who gets paid and how — independent of any single network or wallet.”
the discoverability gap FAS-1 closes
Proof of work · Genesis block
On March 13, 2026, two frontier models paid each other over FAS-1 on XRPL mainnet with no human pressing send. Both transactions validated, and anyone with a block explorer can read them.
The namespace
As with early DNS, the short names go first, and a registered name stays yours. Claim yours before the agents do.
The stack
Every payment starts with a resolution. This API runs that layer, and the three above depend on it.
Agents transact with agents, no human in the loop
Routes to XRPL, Base, Solana, Algorand and X Layer by fixed rules
Intent, mandates & policy for agent payments
Resolves names, anchors registrations, records settlement
Rails
One request lists every rail below, live, without a key. Value moves wallet-to-wallet on the ledger; this API never holds it.
| Rail | Network | What settles here | Status |
|---|---|---|---|
| XRP | XRP Ledger · mainnet | Payments to any pay: alias, over x402 or direct | Live |
| USDC | Base · eip155:8453 | Pay an alias or buy a counterparty screen over x402. Gasless: the facilitator pays the network fee | Live · x402 |
| USDC | Algorand · mainnet | Counterparty screen, server-priced at 0.01 USDC | Live · x402 |
| USDT0 | X Layer (OKX) · eip155:196 | Counterparty screen, priced in OKX's native stablecoin | Live · x402 |
| USDC | Solana · mainnet | Pay an alias or buy a counterparty screen over x402. Gasless. First external-agent settlement 2026-08-01, TX 3vGQmSoZ… | Live · x402 |
| Fiat → XRP | MoonPay on-ramp | Fund a pay: alias with card or bank. Sandbox today; real fiat is pending | ◐ Sandbox |
| RLUSD | XRP Ledger | Settles to aliases with an RLUSD trust line. First settlement 0.5 RLUSD in 4 s, TX 9CDD554F… | Live |
FAQ
It turns a name into a payment. Just as DNS turns example.com into an IP address, one API call turns pay:yourname into the rail, address and tag to pay, then records the settlement once it lands on the ledger. XRPL settles today; agents pay over x402 on Base, Solana, Algorand and X Layer.
Yes. API keys are free, with no credit card required and a generous rate-limited tier. You only pay network fees on the rails you settle over. Higher-volume plans are available once you outgrow the free tier.
FAS-1 (Financial Address Standard) is the open spec behind resolution: how a name maps to instructions, how proofs are anchored on-chain, and how any rail can plug in. It's licensed CC BY 4.0 so wallets, agents and fintechs can build on it without lock-in.
XRP and RLUSD settle on the XRP Ledger. Over x402, a single 402 challenge advertises five networks: XRP on XRPL, USDC on Base, USDC on Solana, USDC on Algorand and USDT0 on X Layer. On Base and Solana the facilitator pays the network fee, so the paying agent holds no gas token. List them yourself at GET /.well-known/x402.
An agent registers its own pay:agent.* name, resolves any other name to its endpoints, and pays over x402 from its own wallet. Before it pays, one paid call returns a screen of the counterparty (OFAC plus resolution) signed by did:web:dnsofmoney.com, which the agent verifies in its own process. On 2026-08-01 an external agent bought that screen on Solana without holding any SOL.
XRPL settles in 3–5 seconds for sub-cent fees, and its memos and destination tags carry the registration anchor. It is also ISO 20022 compatible, which matters for traditional finance interoperability.
Yes. A registered name is anchored on the XRP Ledger with its own FAS-1 memo and stays yours. You can repoint where it resolves at any time and attach your X handle as public metadata. The name itself never changes.
Request a key with your email and use case, and you're approved within 24 hours. From there, a single GET /resolve/pay:name call returns instructions.
No. DNS://Money issues no stablecoin and holds no reserves or customer funds. The payer signs from their own wallet and the value lands at the recipient's address on the ledger. The GENIUS Act and the FDIC's RIN 3064-AG19 regulate stablecoin issuers, custodians and insured banks; a resolver and router sits outside that perimeter. Read the full regulatory posture →
Start building
Everything above, in one API call. Grab your key and start building.