Verifiers
Verifier metadata is a backend single source of truth. Frontend apps, SDKs, widgets, MCP, and docs should consume the backend catalog instead of maintaining parallel metadata.Verifier classes
| Class | Example use | Typical behavior |
|---|---|---|
| Ownership | Wallet, domain, NFT, token assertions | Often instant or lookup-based |
| Risk and anti-sybil | Bot, risk, human checks | Often freshness-sensitive |
| Org and social | OAuth-linked account or org membership | Usually interactive and hosted |
| Agent proofs | Agent identity and delegation | Used by agent registries and MCP flows |
Where to read the catalog
verifierId- availability tier or access constraints
- required verifier data
- interactivity and hosted flow expectations
- delegated-subject support where applicable
Detailed catalog reference
For the current public catalog, IDs, and example payloads, use the detailed page:Verifier Catalog
Detailed verifier IDs, categories, and input examples.