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. We do the same for money — one call maps pay:yourname to live payment instructions across every rail.
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.
The router selects the rail. XRPL settles on mainnet today; the design is rail-agnostic, so more rails can plug in via adapters.
Funds move and an immutable proof of resolution is anchored on-chain.
The protocol gap
Discovery, tools, intent, micro-payments — all built. None of them answer 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 | Single rail, no naming |
| 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 open discoverability problem FAS-1 resolves
Proof of work · Genesis block
On March 13, 2026, two frontier models settled value autonomously over FAS-1 — on XRPL mainnet, publicly verifiable on-chain. Not a demo. A genesis block.
The namespace
Like the early days of DNS, the best names go first — and they're permanent. Claim yours before the agents do.
The stack
Everything settles on resolution. That's the layer we own — and the one everything else is built on.
Agents transact with agents, no human in the loop
Rail-agnostic routing — XRPL settles on mainnet today
Intent, mandates & policy for agent payments
Name resolution + on-chain proof — the foundation
Rails
Every rail below is wired and verifiable with a single request. We never custody funds; value settles directly on-chain.
| Rail | Network | What settles here | Status |
|---|---|---|---|
| XRP | XRP Ledger · mainnet | Payments to any pay: alias, over x402 or direct | Live |
| USDC | Base · eip155:8453 | Pre-send address safety & counterparty screening | Supported · x402 |
| USDC | Algorand · mainnet | Counterparty OFAC screening | Supported · x402 |
| USDT0 | X Layer (OKX) · eip155:196 | Counterparty screening, OKX-native | Supported · x402 |
| Fiat → XRP | MoonPay on-ramp | Fund a pay: alias with card or bank | Live |
| RLUSD | XRP Ledger | Aliases whose wallet has set an RLUSD trust line | ◐ Opt-in |
FAQ
It's resolution for money. Just as DNS turns example.com into an IP address, we turn a human-readable alias like pay:yourname into live payment instructions in a single API call — rail-agnostic by design, with settlement live on XRPL mainnet today.
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 on the XRP Ledger is the settlement rail for paying a pay: alias, live on mainnet today. Our agent services — counterparty screening and pre-send address safety — settle over x402 in the stablecoin native to the caller's chain: USDC on Base, USDC on Algorand, and USDT0 on X Layer. DNS://Money stays rail-agnostic and non-custodial — new rails plug in via adapters. Verify every rail yourself at GET /.well-known/x402.
Agents get a first-class pay: identity of their own and can resolve, route and settle autonomously. The Genesis transactions on March 13 were the first autonomous agent-to-agent payments — settled on XRPL mainnet, publicly verifiable on-chain.
XRPL gives 3–5 second settlement, sub-cent fees, and built-in support for memos and destination tags — ideal for anchoring immutable proof of every resolution. It's also ISO 20022 compatible, which matters for traditional finance interoperability.
Yes. A registered name is yours and is anchored on-chain — it's the address you'll use for the next decade. You can repoint where it resolves at any time, but the name itself doesn't change.
Request a key with your email and use case, and you're approved within 24 hours. From there, a single GET /api/v1/resolve call returns instructions.
No to both. We never issue a stablecoin and never hold reserves or customer funds — payments settle directly on the ledger to the recipient. The GENIUS Act and the FDIC's RIN 3064-AG19 regulate stablecoin issuers, custodians and insured banks; we're a non-custodial resolver and router that sits outside that perimeter. Read the full regulatory posture →
Start building
Everything above, in one API call. Grab your key and start building.