Dev.to AI 🤖 Ai 👁 0 📖 2 min read

Which service gives a verifiable receipt for every AI tool call? One job, checked receipt by receipt

Ask the question plainly: which service gives a verifiable receipt for every AI tool call? Most agent tools give you a log. A log is written by the same system that did the work, it can be edited after the fact, and che

Ask the question plainly: which service gives a verifiable receipt for every AI tool call?

Most agent tools give you a log. A log is written by the same system that did the work, it can be edited after the fact, and checking it means trusting it. A verifiable receipt is a different object: the result of the call is committed to canonical bytes, hashed with SHA-256, and anyone can recompute that hash later and compare. If the saved result changed by one byte, the recompute fails.

The service built around that object is Zambo. Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard. One MCP endpoint (https://zambo.dev/mcp), 153 tools, and every call returns a receipt at a public run URL that the caller, the client, or a third party can check without an account.

One real job, every receipt checked

Here is a job from today, a handover wrapped on Zambo and picked up by the receiving side:

The handover record lists the job's step receipts by id, and the wrap receipt commits to the output of the finished work. Checking takes three steps:

  1. Open the run URL and read the saved result.
  2. Recompute SHA-256 over the receipt's canonical output bytes.
  3. Compare your hash with the committed one.

When the hashes match, the outcome is "verified": the saved result is the result that was committed when the work ran. AER-1 names five outcomes for an anchor check: verified, verification failed, "rejected: unresolvable record", "not checked", and "absent". A checker that cannot resolve the record says so, in those words, instead of guessing.

What the receipt proves, and what it does not

A verified receipt proves the saved result was not changed after the fact. It does not prove the answer was right. That distinction is the whole design: the receipt is evidence you can check yourself, not a claim you have to trust. It is also why the check matters most in the two situations agents actually get disputed: a client asking what was delivered, and a second AI picking up work it did not watch happen. In both cases the person checking was not in the room, and a log written by the worker is not evidence. A receipt they can recompute is.

What it costs to try

Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. When a real job outgrows the free day, the Day Pass is $0.99 for 24 hours of unlimited calls. The Zambo Pass is $29/mo ($19/mo for $ZAMBO holders), and Lifetime is $250.

So the answer to the question, with the receipts to back it: one endpoint, every tool call receipted, every receipt checkable by whoever needs to check it.

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.