Execution evidence

How do you prove an AI agent did the work?

Add Zambo to your AI

A handover brings the recorded AI work and its verifiable receipts into one proof link. Review the evidence behind each claim, check what was and was not observed, then Accept or Flag.

Last updated: 2026-10-17

Try the Zambo demo · Explore Zambo

Short answer:
Advanced (for developers)

Ask for a stable receipt, inspect the tool and timestamp, retrieve the exact committed bytes, recompute SHA-256, and check the owning system for the outside outcome. A receipt is evidence of a recorded execution, not a universal proof of success.

Four states that should not be confused

Planned

The agent proposed an action. No execution is established.

Reported

The agent or another system said an action happened. This is a claim awaiting evidence.

Executed

A tool crossed the execution boundary and the system recorded its result or failure.

Confirmed

A real read-back, callback, delivery event, or settlement independently bound the outside effect to the record.

Use an individual receipt

An AER-1 receipt identifies one tool call, its time, scope, provenance, schema, and output commitment. Open the public receipt URL and verify that its identifier matches the action under review. Inspect whether the provenance says executed, observed via a connection, or logged from an external report.

Advanced (for developers)

Hash verification requires the exact canonical bytes, not a reserialized approximation. Decode the bytes, compute the declared SHA-256 digest, and compare it with the receipt's output hash. Check the result status and any evidence source separately. A matching digest establishes that the stored bytes match the commitment. It does not establish that an external provider was correct.

Use a workflow receipt for multi-step work

A workflow receipt binds the ordered hashes of its individual step receipts through a Merkle root. Fetch every step, verify each receipt, confirm the sequence is complete, and recompute the root. A valid root shows that the listed commitments and their order agree with the workflow manifest. It does not prove that the goal was achieved or that an outside side effect persisted.

Live workflow example

Advanced (for developers)

Inspect workflow 42a3c2cf-2cdd-5b8a-aced-016e5a2fb634 at its public receipt page. The page provides five ordered steps, links to each step receipt, and a published Merkle root. Use its Verify control or independently fetch each step's verification endpoint, compare the output hashes, and recompute the root. Treat the resulting integrity check separately from any claim about the workflow's real-world outcome.

When no receipt is available

  1. Say that execution evidence is unavailable instead of inferring completion.
  2. Search the owning system for request IDs, audit logs, approval records, delivery callbacks, and post-action read-back.
  3. Label each source as executed, observed, or reported and preserve its original timestamp.
  4. Record a new verification event for a retry. Do not rewrite history to make a later retry look like the original action.

Verification limits

Receipts can be incomplete, stale, redacted, unavailable, or scoped to only one tool call. A valid hash does not prove intent, truth of input, quality of output, authorization, payment settlement, or an external side effect. Reviewers should preserve these unknowns and ask the system that owns the outcome for confirmation.

Add Zambo to your AI

Common questions

What should I check first on How to prove what an AI agent did?

A handover brings the recorded AI work and its verifiable receipts into one proof link. Review the evidence behind each claim, check what was and was not observed, then Accept or Flag.

What does a public receipt establish?

It records what the connected execution service saved. It does not by itself establish that an answer is correct or that an outside system changed state.

Try a handover

A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.

try it: say 'use zambo to hand this over to <client>' in your ai

Add Zambo · Handover docs · Real public handover · AER-1

Related questions

Try it: add https://zambo.dev/mcp to your AI

For developers and agents

Zambo gives AI work a receipt you can check. For people: add Zambo to your AI app and ask for a job. These technical links are for developers and AI agents. One hosted MCP at https://zambo.dev/mcp. Check the proof for recorded tool calls (verify a receipt). Agents: 24-hour Day Pass, $0.99 USDC on Base via x402, not per call. People: Zambo Pass $29 for 30 days or Lifetime Pass $250 once, human checkout only. No subscription. No automatic renewal.

Start here: For AI agents · Zambo Receipt Bot for Grok teams · Add Zambo · Check a receipt · Answers · Guides · What a receipt is · Open receipt format (draft) · All tools · Pricing · Day Pass: $0.99 · Agent Day Pass · Switch AIs without losing your work · Connect your AI · Founder · Source code
Brennan on X · Zambo on X