What is receipt verification?

Receipt verification independently confirms that an AI agent action was recorded in a cryptographic DAG with valid post-quantum signatures, deterministic replay, and an H33-74 proof commitment. It proves the action happened, was authorized, and has not been tampered with.

Can anyone verify an H33 agent receipt?

Yes. Receipt verification is public and requires no API key, no authentication, and no H33 account. Anyone with a receipt ID can independently verify the full cryptographic chain.

Do I need H33 infrastructure to verify a receipt?

No. Verification uses the H33 public proof API but does not require trusting H33. The same verification can be reproduced locally using the open-source HATS CLI: hats verify --node .

PUBLIC VERIFICATION · NO AUTH REQUIRED

Verify any receipt independently.

Paste a receipt ID or H33-74 commitment. This page verifies DAG integrity, signatures, replay chain, session lineage, and H33-74 proof without trusting H33.

Try a sample receipt →

VERIFYING CRYPTOGRAPHIC CHAIN...

Receipt not found.

Verify the ID and try again. Ensure you are pasting a valid receipt ID, node hash, or H33-74 commitment.

H33 PUBLIC VERIFIER v1.0

DAG FRAGMENT — CHAIN POSITION

View Full Session DAG Replay This Session

HOW IT WORKS

Client-side verification. This verification runs entirely client-side using the H33 public proof API. Your receipt ID is sent to a single public endpoint that returns the cryptographic proof bundle.

No API key. No authentication. No vendor trust. The public proof endpoint requires no credentials. The response contains all data needed to independently reconstruct and verify every signature, hash chain link, and replay frame.

Reproducible with the CLI. The same verification can be reproduced offline with the HATS verifier CLI: hats verify --node <id>. Download the verifier CLI.

CLI equivalent: $ hats verify --node 0x4f2a8b71e3c9d056