Skip to main content
Every Agentic ID has a ledger: the ordered list of everything that happened to it. When the ID was created, which kinds of identifier were linked to it, when it was merged, when a fact changed level. The ledger is how an answer stays traceable. You can ask at any time what happened to an ID, and whether the record is intact.

Properties

Read an ID’s ledger

GET /v1/ledger/{id} returns one ID’s entries, re-checked. It is not charged. Your workspace must hold the ID.
string
The Agentic ID.
string
One plain line: how many entries, which kinds, and whether the chain checked out.
boolean
true when every entry passed the re-check. false when any entry failed.
object[]
The entries, oldest first.

What “re-checked” means

The check runs every time you call the endpoint. Nothing is read from a stored result. For each entry, in order:
  1. The hash is computed again from the entry’s content and compared with the stored hash.
  2. The entry’s prev_hash is compared with the hash of the entry before it.
verified is true only when both hold for every entry. If any entry was changed, removed or reordered, a link fails, verified is false, and summary says the chain is broken. You can repeat the link check yourself: walk entries in order and confirm each prev_hash equals the hash before it. The hash itself also covers encrypted content that is not returned, so only Agentic ID can recompute it.
Treat "verified": false as a serious signal. Do not act on that ID’s record. Report it to your Agentic ID contact with the ID.

Entry kinds

What detail holds

detail names things by type, ID and hash. Some examples: An entry says that a work email was linked. It never says which address. Treat detail as a record to read, and do not depend on a fixed set of fields per kind. A fact_assessed entry is written when a fact’s shared level changes. Reports your workspace sends as feedback change your own view of a fact and do not add ledger entries.

Errors

An unknown ID and an ID held only by someone else answer the same way.

When to use it

  • Audit. Show when an ID was created and what changed since.
  • Debug a match. See which kinds of identifier were linked, and when a merge happened.
  • Explain a level. A fact_assessed entry shows the level before and after, with the reason.