DNS of Money is a financial address resolution protocol and payment orchestration infrastructure for the machine economy. It resolves human-readable identifiers to payment endpoints across multiple rails — without touching funds, holding deposits, or requiring a banking license.
<p align="center">
<strong>Financial orchestration infrastructure for the machine economy.</strong><br>
Payments. AI agents. Autonomous commerce.<br>
<em>We are not a bank. We are the layer above it.</em>
</p>
<p align="center">
<em>"If you plant ice, you're gonna harvest wind."</em>
</p>
pay:
What This Is
Just as DNS resolves example.com → IP address, FAS-1 resolves pay:vendor.alpha → complete payment instruction.
No raw wallet addresses. No routing numbers in UX. One identifier that works everywhere.
Why This Exists
The agent address resolution gap. AI agents can now transact autonomously — but there is no standard way to name them, register them, and convert those names into payment endpoints. AP2, A2A, and MCP all have this gap. FAS-1 is the answer.
"Discoverability is a known gap. There is no way to register agents, name them, and convert those names into payment endpoints."
— FAS-1 v0.2 (draft), AP2 gap analysis
DNS of Money is the naming and resolution layer for agentic commerce.
Account and routing numbers are never returned at authorization levels 0–1. Full field
list, authorization levels, and error codes: docs/FAS-1-spec.md.
DNS of Money resolves the agent payment discoverability gap identified in AP2 and A2A-002. Any agent can advertise a pay: alias; any caller can resolve it to a ranked list of payment endpoints without prior knowledge of the agent's banking infrastructure.
| Rail | Type | Latency | Currency |
|---|---|---|---|
| XRPL | Blockchain | 3–5 seconds | XRP, IOUs |
| FedNow | Instant ACH | Instant | USD |
| ACH | Bank transfer | 1–3 days | USD |
| SWIFT | Wire | 1–5 days | Multi-currency |
| Solana/USDC | Blockchain | <1 second | USDC |
On-Chain Namespace Anchors
All root namespaces are immutably anchored on XRPL mainnet via FAS-1 memo transactions before publication of this spec. This is the moat: namespaces cannot be forked once registered on-chain.
The first 600pay: names are available at 5 XRP flat — permanently grandfathered at founding pricing. One name per XRPL wallet. On-chain proof issued at registration.
Each founding name includes:
A permanent pay: alias on XRPL mainnet
A unique generative fractal flame identity NFT (XLS-20)
IPFS-pinned art and metadata that outlives every server
Founding tier encoded on XRPL mainnet via FAS-1 memo
Permanent — cannot be revoked
Hard cap enforced atomically: SELECT ... FOR UPDATE inside the registration transaction
Check remaining spots:GET /api/v1/founding/status
Proof of Work
This is not vaporware. The transactions below are real. The XRPL ones are publicly verifiable by anyone — no login, no trust required.
XRPL Mainnet — Publicly Verifiable On-Chain
| TX | Time (UTC) | Direction | Amount | Ledger | Hash |
|---|---|---|---|---|---|
| TX1 | 09:16:40 Mar 13 2026 | Claude → GPT-4 | $0.69 USD (0.482517 XRP) | 102837427 | B92C23BA... |
| TX2 | 20:20:10 Mar 13 2026 | GPT-4 → Claude | $4.20 USD (3.0 XRP) | 102849264 | EB8F2C20... |
Click either hash. It's on the ledger. Permanent.
Bidirectional AI payment rail: proven on XRPL mainnet — publicly verifiable on-chain.
Agent Verification — AI-to-API Resolution Proven
| Step | Result | Date |
|---|---|---|
| Resolve pay:genesis at tier 3 | Full response: entity_id, compliance, ISO hint, agent_commerce, identity block | Mar 24, 2026 |
| Verify NFT on-chain | NFTokenID confirmed, taxon 420069 (founding), IPFS metadata verified | Mar 24, 2026 |
| Witness 1 XRP payment | pay:architect → pay:genesis with memo DNS-OF-MONEY-PROOF | Mar 24, 2026 |
First external AI agent (Perplexity) to resolve a pay: alias, verify on-chain identity, and witness a real payment — end-to-end.
ISO 20022 Compatibility
All payment models are ISO 20022 compatible. The resolver returns iso20022_hint on every resolution response, enabling downstream systems to generate standards-compliant payment messages without any mapping work.
✅ Payment address resolution
✅ Payment orchestration infrastructure
✅ Financial metadata layer
✅ Routing intelligence layer
✅ API gateway over licensed banking infrastructure
❌ Not a bank
❌ Not a deposit holder
❌ Not a settlement institution
❌ Not a card issuer
❌ Not a clearing network
No banking license required to use this protocol.
SDK
Official client libraries for the DNS of Money API. No external dependencies — stdlib only.
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/v1/resolve/{alias} | Resolve a pay: alias to payment endpoints |
| GET | /api/v1/aliases/available/{name} | Check alias availability |
| POST | /api/v1/aliases/register | Register a new pay: alias |
| GET | /api/v1/aliases/founding/remaining | Founding tier spots remaining |
| GET | /health | API health check |
The Financial Address Standard 1 (FAS-1) is the open protocol specification underlying pay: URIs. It is licensed under CC BY 4.0 — free to implement, extend, and build on.
Key properties:
Rail-agnostic: one alias resolves to N endpoints, ordered by policy
ISO 20022 aligned: every resolution carries a message family hint
On-chain anchored: namespace ownership is verifiable on XRPL mainnet
AP2/A2A/MCP compatible: designed for agentic commerce from day one
-green){kind=icon}
