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.
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:- The hash is computed again from the entry’s content and compared with the stored
hash. - The entry’s
prev_hashis compared with thehashof 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.
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_assessedentry shows the level before and after, with the reason.

