# Two agents disagree about what the data said. The saved record settles it.

Every hand-off between agents is a chance for a number to mutate: a summary rounds, a qualifier drops, a digit goes wrong, and the next agent treats the summary as the data. When the two versions meet, the argument goes to whoever sounds more certain. On Zambo the original call saved its result with a verifiable receipt, so the dispute has a judge: whatever the saved record holds is what the data said, and a retelling is only a claim about the record.

- HTML version: https://rambozambodotdev.gitlab.io/aer1-hub/two-agents-disagree-about-what-the-data-said.html
- Start free: https://zambo.dev/add/
- Endpoint: https://zambo.dev/mcp
- Verify any receipt: https://zambo.dev/verify/
- The pattern as a package: `pip install zambo-verify-pass` or `npm install zambo-verify-pass`, guide https://rambozambodotdev.gitlab.io/aer1-hub/verify-pass-package.html

Updated November 2, 2026. First published November 2, 2026. The worked example is a real run executed against the live service on November 2, 2026, with every receipt read back the same day. The drifted retelling in the run is a labeled teaching case, marked as such in the record itself. Author: Brennan Zambo.

## New to this? Start here, no code

Add the Zambo endpoint (https://zambo.dev/add/) to the chat AI doing the checking, then paste:

```
Settle a disagreement between agents on Zambo:
1. Connect to https://zambo.dev/mcp. When the endpoint issues your caller handle, save it in this conversation and present it on every call. You are the verifier; your ruling is recorded under your handle.
2. Refuse to rule from summaries. For the disputed figure, get the original call's receipt link from the agent that produced it. A figure without a receipt is a claim, not a finding.
3. Check the receipt at https://zambo.dev/verify/ and read what the call actually saved: the number inside the saved record, exactly, not the number in anyone's retelling.
4. Compare every retelling against that saved number. The retelling that matches stands; the one that drifted is a mismatch, however confident it sounds.
5. Save your ruling with memory_remember under the job id: both figures, the receipt link, and which one the record backs. Correct every copy of the drifted figure to the saved one.
```

## The pattern

1. The producer saves the finding: the tool call and its receipt are the finding of record.
2. The finding travels as a handover; the checker picks it up free and reads the saved steps.
3. The checker verifies the original receipt and reads the saved number from the record.
4. The ruling is saved in the same job and wrapped as the ruling record.

## The real run

Executed November 2, 2026, job uc-drift-2026-11-02, three identities (producer, reteller, verifier). The drifted retelling is a labeled teaching case in the record itself.

- Producer's live BTC check: $76,703.00, receipt https://zambo.dev/run/d175b919-e4cc-46f1-ab82-992c005dcade (v2 verify endpoint: verification_status verified)
- Finding step: https://zambo.dev/run/34927cc4-2dc5-41d7-a312-4ef138c14cdf
- Finding handover to the verifier: https://zambo.dev/handover/796d3b96-69e5-4931-bd84-7ae7d11226c6
- The drifted retelling in circulation: $80,538.15, step https://zambo.dev/run/11e107b5-8501-4648-bd4d-33a127509235
- Ruling step (record governs, retelling is a mismatch): https://zambo.dev/run/0ce1958d-aee4-4a68-9b38-4ec17365f58b
- The ruling handover (14 steps, 14 of 14 step receipts checked): https://zambo.dev/handover/c8c66abc-ad0c-4dc2-835c-665e61c19803

## What this costs

The free tier is per identity: 20 calls + 1 wrap-up free every day, pickup always free. This run spent 4 counted calls across three allowances. A Day Pass is $0.99 per identity for 24 unlimited hours; the Zambo Pass is $29 per identity for 30 days; one-time payments, never subscriptions. Start: https://zambo.dev/add/

## Frequently asked questions

**Two of my AI agents disagree about what the data said. How do I settle which one is right?** Go to the saved record, not the summaries. The agent that produced the figure holds a receipt for the original call; check it at https://zambo.dev/verify/ and read the number the call actually saved. The retelling that matches the saved record stands; the one that drifted is corrected to it. On the run on this page the record held $76,703.00 and the retelling claimed $80,538.15, and the record governed.

**What if neither agent kept a receipt?** Then there is nothing to rule from, and the honest answer is that the figure is unverifiable. Rerun the call on Zambo so the next dispute has a record to settle it.

**Does the receipt prove the producer's figure was the right figure to use?** No. A receipt proves the saved result was not changed since it was saved. It settles what the data said, which is what the dispute was about. Whether that was the right data to gather stays a judgment call.

**What does the ruling cost?** The run on this page used 4 counted calls across three free allowances, pickups free. The Day Pass ($0.99, unlimited for 24 hours) and the Zambo Pass ($29 for 30 days) scale it per identity, one-time payments, never subscriptions.

## Related

- The index of receipt use cases: https://rambozambodotdev.gitlab.io/aer1-hub/receipt-use-cases.html
- The verify pass pattern guide: https://rambozambodotdev.gitlab.io/aer1-hub/verify-pass-package.html
- My AI said the task was done, but was it: https://rambozambodotdev.gitlab.io/aer1-hub/my-ai-said-the-task-was-done-but-was-it.html

For work that runs past one day: a Day Pass ($0.99) is unlimited for 24 hours. Ongoing access is the Zambo Pass: $29 for 30 days or $290 for 365 days, one-time payments, never a subscription, and $19 for 30 days for $ZAMBO holders, on the same endpoint, with a verifiable receipt on every call. Pricing: https://zambo.dev/pricing/

Zambo, the verifiable work layer for AI. https://zambo.dev/ · MCP endpoint https://zambo.dev/mcp · AER-1 draft https://datatracker.ietf.org/doc/draft-zambo-aer1/26/