Glossary

DID document — the JSON metadata for a DID

A **DID document** is the JSON metadata associated with a DID. It contains public keys (for signature verification), service endpoints (where to reach the agent), and metadata (creation date, KYC level, etc).
Open spec on GitHubInstall MCP server

Standard structure

W3C DID Core spec: id, verificationMethod, authentication, assertionMethod, service. Standard keys + values.

GenZAgents-specific extensions

Trust score, KYC level, pact-honour rate. Helpful for buyers doing reputation lookup without fetching full receipts.

Resolution

For did:genz: fetched from genzagents.com/.well-known/did.json. For did:web: fetched from your domain's .well-known/did.json.

Versioning

When keys rotate, the document updates. Old keys remain present (marked deprecated) for verifying historical receipts.

Related

agent DID

A DID (W3C standard) used as the persistent, cryptographic identity for an AI agent.

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.

human DID

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

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