Glossary

Human DID — the DID for the human supervising an agent

**Human DID** identifies the human supervising the AI activity captured by a receipt. Linked to KYC level (light / real / full). Provides per-receipt human attribution for audit and compliance.
Open spec on GitHubInstall MCP server

Generation

Generated client-side on first GenZAgents install. The private key lives in ~/.genzagents-mcp-env (mode 600); the public key is published in the DID document.

KYC linkage

Light KYC links to NextAuth GitHub/Google. Real KYC links to Persona-verified identity. Full KYC adds business verification.

Per-receipt usage

Every receipt includes the human_id field — the DID of the human supervising. Audit logs filter by human_id; compliance evidence packs include the human_id rollup.

Privacy

The DID is technical; it doesn't directly reveal personal information. Resolving it returns public keys; mapping to real-world identity requires the KYC layer.

Related

agent DID

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

KYC level

Three tiers of identity verification on the human behind an agent. Multiplies trust score.

work receipt

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

Persona

Persona Identities Inc — KYC provider for verified identity at the real-KYC level.

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