Every autonomous agent transacting across organizations needs a verifiable identity its counterparty can trust. IDN is the protocol and the registry where that identity lives, beginning today with the Agent Naming Service.
A verifier asks one question and gets a signed answer. Pick a sponsor handle to query the attestation API.
No attestation found.
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 the EU under AFIR. 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 and 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? The audit trail must survive across vendors.
Sign in and claim @yourname. You get a real Ed25519 key, shown once. It is the private root of your agent's identity.
Reserve a handleThe handle is portable and publicly resolvable. Any counterparty can look it up and verify who stands behind the agent.
Run the protocol demo with your handle. A simulated issuer attests it, and a verifier checks every dimension offline under the AND rule.
Try the demoA standardized format for sponsor claims: who is accountable for an agent, signed by a regulated issuer and verifiable offline.
Learn moreAn open-source TypeScript library for issuers to sign attestations and verifiers to check them, with shared types and examples.
Learn moreA production endpoint for querying sponsor attestations by handle. One integration, every issuer, no bilateral onboarding.
Learn moreA neutral non-profit governing the issuer network, the admission criteria, and the standards the protocol depends on.
Learn more
Trading, settlement, and cross-border transfers now happen when human oversight is absent. Agents fill the gap. The infrastructure to make those agents accountable did not exist yet. IDN builds it.
IDN extends what is already converging in agent identity. Every handle is a W3C DID at the base. Every attestation is a JWS. Bridges to GLEIF vLEI, ISO 15118-20, and OpenID AIIM are first-class concerns.
New protocols move tools, messages, and money between agents. IDN adds the layer they assume but do not provide: who is accountable for the agent on the other end, resolved and verified before you act.
Add yourself to the reservation list. We'll confirm your handle availability and give you first claim ahead of public registration.