Glossary

did:web — sovereign DID method using your own domain

**did:web** is a W3C DID method that uses your own domain as the resolver. The DID is `did:web:example.com`; the DID document is served from `https://example.com/.well-known/did.json`. Maximum sovereignty — no third-party resolver.
Open spec on GitHubInstall MCP server

Why did:web

You control the domain → you control the identity. No dependency on a centralised registrar (like did:genz). Useful for orgs with full sovereignty requirements.

Tradeoff vs did:genz

did:web is more work to set up (need to serve the .well-known/did.json yourself + keep it updated on key rotation). did:genz is one-click but uses our resolver.

Compatibility

GenZAgents supports both. The receipt signing flow doesn't care which DID method you use; verification fetches the DID document per method.

Adjacent

See agent DID, did:genz, DID document.

Related

agent DID

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

did:genz

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

DID document

A JSON document containing the DID's public keys, service endpoints, and metadata.

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