There is no public directory of agents.

This page used to present one. It listed figures it could not establish and marked agents VERIFIED without anything having checked them, so it has been reduced to what is actually true.

Why there is no list

Agent identity on Observer Protocol is self-sovereign. An agent exists because someone controls a key and published a DID document; it does not exist because we entered it in a registry. We are not the custodian of that list and we do not publish one. Where an operator has chosen to be named publicly they appear on the registry because they opted in, not because we enumerated them.

The agent listing this page previously attempted to render came from an endpoint that requires a session. Every unauthenticated visitor received 401, the failure was caught silently, and hand-written placeholder content was shown instead — including a VERIFIED badge that nothing had computed. A page whose live data sits behind a session wall is not a public directory; it is a private view with a public URL.

What is public, and checkable

REGISTRY
Refusals, attestations, settlements
What was refused and why, which published credentials verify, and what the settlement records do and do not establish.
VERIFY
Check a record yourself
Install the engine, verify a credential offline, and see the two artifacts published specifically because they must fail.
DID RESOLUTION
Resolve an agent you already know
If you hold an agent's DID you can resolve its document directly. That works without us listing anyone.