Every interaction. Signed. Sealed. On-chain.
Anchor cryptographic receipts on Hedera Consensus Service. Tamper-proof records of what was requested, what was returned, and when it happened. For agents, APIs, and everything in between.
$0.05 per receipt. Verification is free.
Live examples on mainnet
Two real receipts anchored by an autonomous agent. Click either card to see the full record, then click "Verify on Hashscan" to inspect the underlying HCS transaction.
Caller-only attestation
The agent signed the receipt and paid the anchoring fee. The provider is named on the receipt but never attested. One-sided proof: the caller cannot deny their claim, but the provider has no on-chain rebuttal.
Co-signed by both sides
Both the agent and the provider signed the same canonical payload. Neither party can later claim the call didn't happen or that the request or response was different. Verifiable from chain alone without trusting our backend.
Caller's wallet signs
Every receipt is signed by the caller's wallet using TIP-712 or EIP-712. The signature binds the caller's identity to the execution record.
Anchored on HCS
Receipts are submitted to Hedera Consensus Service, providing a tamper-proof, ordered, timestamped record with finality in seconds.
Anyone can verify
Receipts are publicly verifiable via Hedera mirror nodes. No account required. No trust assumptions. Just check the chain.
Why anchor receipts
SLA enforcement
Prove that a service met or missed its latency, uptime, or accuracy commitments. Receipts capture timing, status, and result hashes.
Billing disputes
Settle disagreements with cryptographic evidence. Both caller and provider can point to an immutable record of what happened.
Compliance and audit
Maintain a verifiable audit trail of every agent interaction. Auditors can independently verify records without trusting any party.
Multi-agent workflows
When agents chain calls across multiple services, each step gets its own receipt. Reconstruct the full execution path from on-chain data.
How agents use H-Seal
An agent invokes an MCP tool, REST API, or another agent.
The caller builds a receipt: request and response hashes, identities, timestamps, result.
The caller signs it via TIP-712 and anchors it on H-Seal with an x402 payment.
The receipt is permanent on Hedera; anyone can verify it via a mirror node.