AI Agent Onchain Receipt

Last updated: 2026-09-24

Short answer: An AI agent onchain receipt combines an execution record with a separately verifiable blockchain reference when a real anchor was submitted and confirmed. The chain reference does not replace the receipt, and a receipt does not create an onchain event that never occurred.

Last reviewed: 2026-09-23. This page describes a reviewable evidence pattern and does not claim an outside result without upstream confirmation.

What stays offchain

Prompts, private inputs, full provider payloads, and sensitive context should remain outside a public chain record.

What an anchor can add

A confirmed transaction or immutable reference can help establish that a particular commitment was published by the relevant system.

How to check

Inspect the receipt, canonical commitment, transaction or anchor reference, network, confirmation state, and verifier independently.

Live verification example

Open a public execution receipt or call its verifier. The example reports verification_status: verified for the stored record. It is not proof of an unobserved external outcome.

Frequently asked questions

AI agent onchain receipt

An AI agent onchain receipt combines an execution record with a separately verifiable blockchain reference when a real anchor was submitted and confirmed. The chain reference does not replace the receipt, and a receipt does not create an onchain event that never occurred.

What can a verifiable receipt prove?

It can show what the execution layer recorded and what its integrity checks verify. It cannot prove an unobserved outside outcome.

How can another reviewer check the record?

Open the public receipt, compare the tool, time, result, and status, then call the verifier. Keep outside confirmations separate from the execution record.