> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.adid.dev/llms.txt.
> For full documentation content, see https://docs.adid.dev/llms-full.txt.

# Trust Explorer

#### When to use

You want to inspect the trust graph around a DID — what credentials they hold, who has issued to them, what schemas they use. The Trust Explorer is the visual front for the Verifier's [Trusted Issuers Registry](#trusted-issuers) and the platform's `network/events`.

#### Before you begin

Signed in (any role).

#### Steps

1. Open `/trust-explorer`.
2. Search for a DID (or click any DID-link in the platform).
   3\. The page renders:
   * **Central node** — the DID you searched.
   * **Outgoing edges** — VCs they have issued (if they are an issuer).
   * **Incoming edges** — VCs they hold.
   * **Trust score** — composite metric from `AgentTrustRegistry` (only meaningful for agent DIDs).
   * **Compliance VCs** — any compliance VCs the DID holds.
3. Click any edge to see the underlying credential's claims (only if it is public or you are authorised).

#### API endpoints used

The page is a thin client over a few endpoints already documented elsewhere:

* `GET /api/v1/dids/resolve/{did}` — central node ([§3.1.9](#did-resolver)).
* `GET /api/v1/credentials?subjectDid={did}` — incoming edges.
* `GET /api/v1/credentials?issuerDid={did}` — outgoing edges.
* `GET /api/v1/verifier/compliance-vcs?did={did}` — compliance VCs ([§5.5.3](#compliance-vcs)).
* `GET /api/v1/agents/{did}` — trust score, autonomy ([§6.4](#agent-detail)).

#### Verify

You can recreate the same graph manually by stitching the four endpoint responses.

#### Troubleshooting

If the graph is empty for a known DID, the most common cause is an unresolvable DID (check [§3.1.9](#did-resolver)) or filters that are too tight (clear the filter chips at the top).