Product evidence · Attestation
Check a record.
Understand the result.
Start with a record identifier you hold. The public verifier returns its current chain status so you can inspect the result for that record.
A matching hash establishes consistency of the checked data. Evidence of historical work and evaluations of an AI system require their own supporting observations.
Inspect a record
Enter an existing seal number to get its verification link. Opening the JSON response reads the record; it does not create or change one.
GET /api/attest/verify/{seal}
Replace the placeholder with your seal number. Read both the HTTP status and the returned chain_status; a successful HTTP response alone does not mean the chain is verified.
Read the returned status
- verified
- The requested record is sealed and the current chain check succeeded.
- seal_unsealed
- The requested record is not sealed; its chain membership is not verified.
- no_sealed_rows
- There is no sealed chain available to verify this record.
- broken
- The current chain check did not succeed.
If the response reports an invalid identifier, a missing record, a rate limit or an unavailable service, no successful verification result has been returned. Check the identifier and follow any retry guidance in the response.
Check a published receipt chain
The receipt-chain response describes the current published selection of product review records. Its specification explains how to recompute the chain and interpret a signature when one is present.
The published selection can change. Save the response you inspected if you want to compare it later. A matching head or a valid signature establishes properties of that data; neither establishes completed work or a complete, unchanged history.
Questions about verification
- What does a verified record establish?
- A verified chain status means the returned record is sealed and the current chain check succeeded. Interpret that result for the supplied record and the response you inspected.
- Does a matching hash establish that historical work happened?
- No. Matching hashes establish consistency of the checked data. Establishing that an event happened requires evidence of the event; assessing an AI system requires evaluations appropriate to its task.
- How should I interpret receipt-chain signatures?
- Check whether signing is enabled in the response and verify any signature against a public key whose authenticity you have established. A valid signature binds the key holder to the checked chain head. It does not establish the events described by the records or a complete, unchanged history.
- What if verification is unavailable or no record is found?
- An unavailable response or a missing record gives no successful verification result. Confirm the record identifier and inspect the response status before drawing a conclusion.