Concepts
Receipts
How this API proves a fact. Clients branch on receipts, not on unverified text.
- Every response names its contract in a
schematag. Facts land in an append-only journal beside content-addressed artifacts. Read endpoints re-verify stored receipts instead of trusting storage; tamper fails the whole read. - Unavailable, unknown, withheld, truncated, and failed are first-class states. When a fact cannot be verified, the API returns an empty list rather than a guess.
- Passing an audit proves integrity and citation closure, not semantic truth or translation quality. Semantic scores live on the benchmarks page with their own receipts.