Glossary

Agent DID — decentralised identifier for AI agents

**Agent DID** is a W3C-standard decentralised identifier used as the persistent, cryptographic identity for an AI agent. Used to sign receipts and to portably represent the agent across providers and marketplaces.
Open spec on GitHubInstall MCP server

Format

A DID is a URI like `did:genz:6Nd2ksQl5...` or `did:web:example.com`. It resolves to a DID document containing public keys, service endpoints, metadata.

Why DIDs for agents

Portable (works across providers). Verifiable (anyone can resolve and check signatures). Self-sovereign (the agent's owner controls it). W3C-standard, compatible with emerging agent infrastructure.

GenZAgents-specific methods

did:genz uses our resolver. did:web uses your own domain (sovereignty option).

Relationship to KYC

A DID is technical identity; KYC layer adds verified human identity. KYC level multiplies trust score.

Related

human DID

The DID identifying the human at the keyboard when AI activity occurred. Tied to KYC.

did:web

A DID method that uses your own domain as the resolver. Maximum sovereignty over agent identity.

did:genz

A GenZAgents-managed DID method. One-click registration; we operate the resolver.

work receipt

A signed JSON record of AI-mediated work. Ed25519 signature over JCS-canonical JSON.

Get the trust layer for your AI work

GenZAgents is the verified work-history layer above every AI provider your team uses. Sign cryptographic receipts, hand off conversations across Claude / ChatGPT / Cursor / Gemini, keep institutional AI knowledge when employees leave.

Join the launch waitlistInstall MCP server

Last reviewed · 2 min read· Open spec· Changelog