Skip to content
agentics.you
Start free

Check a receipt

Check a receipt.

An agent acted under a rule, and the action left a receipt. Check that receipt here. No account needed.

Paste a receipt

A receipt hash is the id of one recorded action. A signed record checks here too. Nothing is marked passed unless that step passed.

  1. The receipt is unchanged

    The receipt’s text still gives the fingerprint it had when it was written.

    Not checked yet

  2. The receipt is in sequence

    The receipt points to the receipt written just before it, so none can be slipped in or taken out.

    Not checked yet

  3. The receipt is in a sealed batch

    The receipt’s fingerprint is part of a batch, sealed every 30 minutes under one shared fingerprint.

    Not checked yet

  4. The batch is on a public record

    That shared fingerprint was written to a public blockchain, where no one can change it.

    Not checked yet

Sample receipt (not anchored)

Allowed

An accounts agent paid a $42 vendor invoice under a rule that approves invoices of $50 or less.

Outcome
Invoice paid. The vendor marked it settled.
Rule
Invoices of $50 or less are allowed
Amount
$42.00
Time
Oct 3, 2026, 9:04 AM PT
Hash
a3b5a7a7fd61fea0ee05fb832dc94db42eccd544f7c8d358e335a9ce3422814d
Anchor memo
e4f69600610e122cd4fc117c6a66181e50d1b84ebfbc92d8ae5d31b99793d403

Link to this receipt’s check. No account needed.

The latest anchor is read from the status check. Status

Four checks

What a check proves

That this receipt is the one that was written, and that it still matches. The four checks run on whatever you paste.

  1. 01

    The receipt is unchanged

    The receipt’s text still gives the fingerprint it had when it was written.

  2. 02

    The receipt is in sequence

    The receipt points to the receipt written just before it, so none can be slipped in or taken out.

  3. 03

    The receipt is in a sealed batch

    The receipt’s fingerprint is part of a batch, sealed every 30 minutes under one shared fingerprint.

  4. 04

    The batch is on a public record

    That shared fingerprint was written to a public blockchain, where no one can change it.

What it does not prove

It does not say the action was a good idea. It says the record was not quietly changed.

How it works under the hood
  1. Canonical JSON. The receipt is written out the same way every time: keys sorted, empty values dropped.
  2. SHA-256 leaf. That text is hashed. The hash covers the receipt, not its own id.
  3. Sorted-pair Merkle fold. Hashes in a batch are paired in order and hashed again, up to one root.
  4. Public memo anchor. That root is written as a memo on a Solana transaction.

These two lines are the whole rule for the receipt’s hash and the batch.

rules
sha256Hex(JSON.stringify(canonicalize(receipt without receipt_id, batch_id)))
sorted-pair fold: hashPair(a,b)=sha256Hex(a<=b?a+b:b+a); odd nodes duplicated; empty tree -> null

The latest anchor is read from the status check. Status