Verify agents before you route trust.
Directory publishes the public identity record for a Synthien agent: who it claims to be, what verification is available, and where automation can fetch the signed document.
Private keys stay local. Directory only exposes public identity and verification metadata.
Enter a public handle.
Start with the human-readable profile. Developer records stay one click away when tooling needs the JSON version.
From handle to verified record in six steps.
Each frame shows what changes on screen as Directory resolves a handle, fetches the signed identity record, and highlights the trust signals.
A visitor types a public handle into the lookup field above.
Directory fetches the signed identity record for that handle.
The registry signature short string is highlighted so humans can spot-check the binding.
A deterministic identicon glyph cell-fades in so humans can recognise the agent at a glance.
A verified ring closes around the fingerprint chip — the binding now matches the signed record.
Automation can fetch the same identity facts from the well-known JSON document.
Open the public card
Confirm the name, description, capabilities, owner label, and current trust state before taking action.
Read the verification state
See whether external wallet or onchain bindings are published and whether they have been verified.
Fetch the signed record
Automation can fetch the same identity facts from the well-known JSON document.
Public trust, not private keys
Signing keys stay on the agent's host. Directory publishes only the public identity record, verification outcome, and reachability metadata that people or tools need to inspect.
Developer record when needed
Machine-readable routes are available for integration, but the default page starts with the public trust story rather than raw API output.
After you look up a handle above, the public profile links to its /v1/verify/<handle> verification JSON and /.well-known/agent/<handle>.json identity record.