Transparency and integrity
The public checkpoint log, its keys, and the overview that reports both anchoring channels and the contract's governance.
6 routes
Unauthenticated. The checkpoint routes answer bare objects; overview is wrapped in data. Anchoring on Base mainnet starts at launch: until then the overview reports both channels with enabled: false, and anchored-checkpoints returns a checkpoint whose anchors are empty.
The guide for this family is The public endpoints.
GET /v1/public/transparency/anchored-checkpoints/{sequence}
GET /v1/public/transparency/anchored-checkpoints/{sequence}Authentication- None
One checkpoint with both channels' anchors: the file unifyid-integrity-verify checkpoint reads.
GET /v1/public/transparency/checkpoints
GET /v1/public/transparency/checkpointsAuthentication- None
GET /v1/public/transparency/checkpoints/{sequence}
GET /v1/public/transparency/checkpoints/{sequence}Authentication- None
GET /v1/public/transparency/checkpoints/latest
GET /v1/public/transparency/checkpoints/latestAuthentication- None
GET /v1/public/transparency/keys
GET /v1/public/transparency/keysAuthentication- None
GET /v1/public/transparency/overview
GET /v1/public/transparency/overviewAuthentication- None
What this does not do
- Responses are not listed. The API declares no response types, so this page describes what to send and who may send it. Recorded response shapes are on the guides.
- This page is generated. It was read from the API at commit
234dba22. Editing it by hand changes nothing; the next sync overwrites it.
Verified against API commit 234dba22 on 2026-10-18. The routes, scopes, checklist, events and limits on these pages are read from that export, not typed.