SENTINEL

Verify a run — keyless

Paste a run id. Your browser re-checks the receipt chain against the public verify endpoint — no account, no API key, no trust in the operator required. That is the point of the product.

Run id

CHAIN VERIFIED

Every receipt links to the previous one and every hash recomputes. The run's history is intact and tamper-evident.

NO CANONICAL RECEIPTS

The verifier returned neither true nor false — this run has no canonical receipts to check (unknown id, or a legacy run from before canonical sealing). Absence of receipts is a finding, not a pass.

What a verified chain demonstrates

EU AI Act · Art. 12 — record-keeping

Automatically generated, hash-chained event records over the system's operation. A verified chain shows the log's integrity can be re-checked by a party who does not operate the system.

EU AI Act · Art. 19 — log retention

Receipts are append-only and independently re-verifiable over time. The retention attestation itself ships in the evidence pack generated for your auditor.

EU AI Act · Art. 26 — deployer duties

Deployers must be able to demonstrate oversight of what their AI systems did. A keyless verify URL gives your counterparty and your auditor the same check you have.

Honest scope: receipts are hash-chained and tamper-evident — integrity plus timestamp. Verification supports your record-keeping obligations; it does not by itself constitute legal compliance, and it proves what was sealed, not who authorized it. Receipts contain hashes only: verifying a run never exposes prompts, outputs, or personal data.