human.tech docs

The identity and control layer for people, institutions, and AI. Built by Holonym Foundation.
human.tech is an open ecosystem of protocols for digital personhood, secure key management, and zero-knowledge identity. It is the foundation for Digital Public Infrastructure that civic services, institutions, and AI verify against.
How it works
One architecture, three roles, no central database.
- Issue. A trusted party issues a credential to a person. The person holds it in their own wallet.
- Hold. The credential lives with the person, backed by keys only they control. No central honeypot to breach.
- Verify. A service checks a cryptographic proof of the relevant fact. No copies stored, no central lookup.
The same primitives carry across every audience. See Use Cases for how governments, financial institutions, AI agents, and communities build on them, and Concepts for how the pieces work.
By the numbers: 43M+ credentials issued, 2M+ verified humans, more than $500M in funds protected, across systems independently audited 4×. See Security & Audits.
Start here
Four common reasons people land on these docs, and where each one should go first.
| You are | Start at |
|---|---|
| Evaluating an integration or partnership | Proof of Clean Hands, then Use Cases |
| Building on us | WaaP for wallets, Clean SDK for private value flow, TAP for agent credentials |
| Assessing our privacy or compliance claims | Proof of Clean Hands, Cryptographic Security, Security & Audits |
| Looking for one specific fact | Search, or the Glossary |
Products

Wallet as a Protocol. One-click sign-on with trustless account recovery, so people, institutions, and AI hold their own keys.

Sybil resistance and identity verification. Verify unique humans with Stamps, ML models, or ZK identity checks.

Secure cryptographic key creation using familiar authentication like web accounts, biometrics, and passkeys. Built as an EigenLayer AVS.

Privacy-preserving Ethereum-to-Aztec bridge with built-in compliance. Move tokens into Aztec’s private layer while proving you’re compliant, without revealing personal information.
The no-UI engine behind Shield. Embed compliant private bridging into your own app, without shipping a bridge front end.
Credential isolation for AI agents. Agents call APIs by credential name and never see the secret values.
