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 today, with ACH, FedNow, SWIFT and SEPA behind 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
Optimal path across XRPL, ACH, FedNow, SWIFT, SEPA
Intent, mandates & policy for agent payments
Name resolution + on-chain proof — the foundation
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 across crypto and traditional rails — in a single API call.
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.
XRPL is live on mainnet today. ACH, FedNow, SWIFT and SEPA are integrated behind adapter interfaces and switch on as banking partners come online — the multi-rail router picks the optimal path and new rails are added without breaking existing aliases.
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.
Start building
Free, no credit card, approved within 24 hours. Claim your name before the agents do.