Axemere.ai

Proofs

For: Compliance officers, auditors, and operators verifying the cryptographic integrity of AI transaction records.

Policies | Approvals | Quarantine | Audit Logs | Records | Proofs

The Proofs page lets you verify the cryptographic integrity of any AI transaction recorded by the Ledger. Verification is mathematically independent of Axemere's servers; you can confirm a record has not been tampered with using only the record hash.

Navigation: console.axemere.ai/proofs

Required package: Ledger (Advanced Analytics chain)

Table of Contents

How Ledger Proofs Work

Every AI transaction routed through the gateway is recorded as an execution record. When the Ledger package is active, each record is additionally:

  1. Hashed: a SHA-256 hash is computed from the full record contents at the time of the transaction.
  2. Anchored: the hash is included as a leaf in a Merkle tree that is published at regular intervals.
  3. Proofed: a Merkle path (from the leaf to the published root) is stored alongside the record.

To verify a record, you supply its hash. The gateway walks the Merkle path and confirms that the hash resolves to the published root. If anything in the record was changed after the fact, the hash would not match, and verification would fail.

Verifying a Proof

  1. Open the Records page and locate the execution record you want to verify.
  2. Copy the Record hash from the record detail panel.
  3. Navigate to the Proofs page and paste the hash into the Record hash field.
  4. Click Verify.

The verification runs against the Ledger's Merkle tree. Results appear within a few seconds.

Interpreting the Result

ResultMeaning
Proof verifiedThe record hash matches its position in the Merkle tree. The record has not been altered since it was anchored.
Verification failedThe hash did not resolve to a valid Merkle path. The record may have been modified, the hash was entered incorrectly, or the record predates Ledger activation.

A successful verification returns the full Merkle proof as JSON, including the leaf hash, path nodes, and root. This output can be stored externally as an independent audit artifact.

Use Cases

  • Compliance audits: provide cryptographic proof that specific AI transactions occurred as recorded, without relying on Axemere's word.
  • Billing reconciliation: verify that the usage records used for billing match what was actually transacted.
  • Dispute resolution: if a workload disputes a cost or policy decision, the proof shows exactly what the gateway saw at the time.
  • Third-party audit: share the record hash and Merkle proof with an auditor who can independently verify integrity.

Related: Records | Audit Logs