Re-verify a generated evidence pack
Re-hashes the stored document and re-resolves every citation it made against live data, scoped to the pack’s project or organization. Never errors on a data condition — a deleted record, a deleted storage object, or a pack that never finished generating are all reported as results, not exceptions. See Verification for the full field reference, in particular what unverifiableRefs means and why it must be read alongside evidenceStillPresent rather than ignored.
Authenticated with a dashboard session (browser cookie), not x-api-key, and requires compliance:read plus the Pro plan or above.
Response
The verification result.
Overall verdict. verified: the hash matches and every checked citation still resolves. incomplete: the pack is not completed (pending, processing, or failed), or has no stored document, so there is nothing to verify. object_missing: the stored document could not be read. hash_mismatch: the stored bytes no longer hash to the recorded sha256. diverged: the hash matches but one or more cited records no longer exist or moved. The other fields are unchanged and still returned.
verified, incomplete, object_missing, hash_mismatch, diverged Citations that structurally cannot be re-checked at record level (ClickHouse aggregates, certain change-timeline event kinds). Always read alongside evidenceStillPresent — a high unverifiableRefs count means most of the document was not re-checked, even if every checkable citation passed.

