Every autonomous agent transacting across organizations needs a verifiable identity its counterparty can trust. MAN is the protocol and the registry where that identity lives — beginning today with the Agent Naming Service.
When an autonomous agent acts across organizational boundaries with financial or legal consequences, the receiving party must answer three questions before it can accept the action.
None of OAuth, API keys, on-chain wallet signatures, or browser session cookies answer these questions in a way an unfamiliar counterparty can verify offline.
The receiving bank needs to know who the sender actually is, satisfy FATF Travel Rule, and verify the agent had real authority. Today this requires bilateral integration with every issuer.
ISO 15118-20 becomes mandatory in EU under AFIR in January 2027. Cross-OEM Plug & Charge requires shared trust roots and an agent identity the station can verify offline.
On-chain signatures prove a key signed. They don't prove that key was authorized to act for the DAO. Off-chain counterparties (banks, auditors) cannot accept on-chain proof alone.
The receiving system must determine: is this agent actually authorized by the employee? Is the employee actually authorized by their company? Audit trail must survive across vendors.
Every agent identity infrastructure begins with a name. ANS is the neutral, jurisdiction-portable registry where your agent's handle lives — independent of any single issuer, AI provider, or device.
You reserve the handle today. Attestation, issuer pools, and full cross-organizational verification roll in across 2027 and 2028. Your handle stays the same throughout.
handle: "@your-name"
kind: "individual"
publicKey: "ed25519:..."
reservedAt: "2026-11-04"
portable: true
upgradable: trueOne handle, resolvable from any client, anywhere. No platform lock-in. No DNS rewriting.
Your handle survives device changes, AI provider changes, issuer changes. Tenure is preserved through a portable certificate.
Compatible with W3C DID, OpenID AIIM, GLEIF vLEI bridging. Built to integrate, never to replace.
Start with naming. When you need cross-org attestation, opt-in to a regulated issuer without changing your handle.
ANS opens with a 60-day sunrise period for trademark holders, followed by 30 days of early access for DAOs and developers, before general availability. Pricing is in USD, renewals annual.
For developers, creators, and individual agent owners.
For DAOs, open-source projects, and agent collectives.
Run an entire subdomain for your organization's agents.
Single-word handles, dictionary terms, and industry primitives.
Prices are indicative for v1.0. Final pricing confirmed at launch in Q4 2026.
ANS gives every agent a portable identity. The layers above add what counterparties need to actually accept agent action: verifiable sponsorship, regulated attestation, and per-vertical compliance. Each layer is opt-in.
The neutral registry where your agent handle lives. Reservation, renewal, resolution. Independent of any issuer.
Developers · DAOs · Brands · Individuals
Sign your own attestations with your own keys, no regulated issuer required. Built for DAOs, internal automation, and developer experimentation.
DAOs · Open-source · Small teams
Mobile network operators, banks, qualified trust service providers, and government identity authorities sign attestations under a shared verification rule. First issuers in pilot.
Cross-border SMB · IoT · Algo trading · DAO treasury
The enterprise-grade operations layer above the issuer network. Compliance dashboards, audit trails, ISO 15118-20 and FATF Travel Rule modules for verticals where it's mandatory.
Charging operators · Tokenized deposit issuers
Each layer can be used without the next. A handle remains useful even without attestation. Attestation works even without enterprise compliance dashboards. You opt in to depth when you need it, and your handle never changes.
Add yourself to the reservation list. We'll confirm your handle availability when the sunrise period opens in Q4 2026, and you'll get first claim ahead of public registration.
MAN extends what's already converging in agent identity. We don't fork ecosystems. Every handle is a W3C DID at the base layer. Every attestation is a JWS. Bridges to GLEIF vLEI, ENS, and ISO 15118-20 are first-class concerns, not afterthoughts.
No call to the registry or issuer on the transaction path. Cached public keys, refreshed in background.
Identity records stay with the regulated issuer. The registry sees handles, public keys, and routing metadata.
Issuer, sponsor, KYC tier, tenure, attestation strength — all in one JWS. No recombination attacks possible.