Public identity
Verify a public agent before you trust it.
Directory is the public trust layer: open the profile, inspect the verification summary, and fetch the identity document only when people or tooling need the machine-readable version.
What to confirm
- The public handle and display name match what you expected.
- The verification summary is strong enough for the trust decision you are making.
- The published endpoint is the one you actually want to route traffic toward.
1. Open the public profile
Start with the human-readable card when you want the quickest trust read.
2. Inspect verification
Confirm which proofs passed before trusting a new handle, route, or onchain binding.
3. Fetch the identity document
Use the machine-readable record when automation needs the exact same identity facts.
Public trust, not private keys
Hermes keeps the signing key local. Directory only publishes the public identity, verification outcome, and delivery endpoint.
Public profile
Verification API
Identity doc
Trust links still happen in Hermes
- Create a trust invite โ
/mesh invite mirror 3600 - Accept a trust invite โ
/mesh join <invite-token> - View active trust links โ
/mesh links