# The agent watched the price, but you cannot prove what it saw. Now you can.

An alert is a claim about the past: the price crossed your line at a moment that no longer exists anywhere, and a missing alert is even harder, because silence and diligence look identical without a record. When the watcher runs on Zambo, every reading is saved as a step with a verifiable receipt under one watch job, baseline first with the rule written beside it, quiet readings included. What the agent saw becomes a list anyone can open and check, so the alert and the quiet are both provable.

- HTML version: https://rambozambodotdev.gitlab.io/aer1-hub/the-agent-watched-the-price-but-i-cannot-prove-what-it-saw.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-watch` or `npm install zambo-watch`, guides https://rambozambodotdev.gitlab.io/aer1-hub/signal-watch-package.html and https://rambozambodotdev.gitlab.io/aer1-hub/scheduled-agent-heartbeat.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. Author: Brennan Zambo.

## New to this? Start here, no code

Add the Zambo endpoint (https://zambo.dev/add/) to the chat AI that does the watching, then paste:

```
Watch a price and keep the proof 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 watcher; keep the same handle for every check, it is what ties the readings together.
2. Open one job for the watch: pick a single job id and call live_price for the asset. Save the baseline with memory_remember under the job id: the price, the time, the price receipt, and the rule you will judge by, such as flag any move of 1 percent or more.
3. At every check, call live_price again and save the reading the same way: price, time, receipt, the move against baseline, and whether the rule fired. Save quiet readings too; a watch that only records its alerts cannot prove it was watching in between.
4. When anyone questions an alert, or a quiet stretch, wrap the job with handover and send the link: every reading in order, each with its receipt, checkable at https://zambo.dev/verify/.
```

## The pattern

1. Baseline first: the first reading saved with its price receipt and the rule written next to it.
2. Every check saved, alert or quiet, with the move computed against the saved baseline.
3. Wrap the watch: one handover holding the whole series, provable as a set.

## The real run

Executed November 2, 2026, job uc-watch-2026-11-02, one watcher identity.

- Baseline price call, BTC $76,708.00: https://zambo.dev/run/2f6e84c8-3d47-44e9-a6fc-b8f648f9b227
- Baseline step, with the 1 percent rule saved beside it: https://zambo.dev/run/a2c6ca3a-74d8-4138-9e97-79823699fcf7
- Second reading, BTC $76,743.00 (move +0.046 percent, no flag under the rule): https://zambo.dev/run/7454d0ec-805f-4bee-aa49-e14d5d5c513a
- Check step: https://zambo.dev/run/36e4b832-9a46-4477-abc0-2bea242d8b69
- The watch handover (11 steps, 11 of 11 step receipts checked): https://zambo.dev/handover/83809882-1f02-4660-a156-749f0898c393

Nothing dramatic happened in this run, and that is the point: the record proves the watcher was watching, reading by reading, on a quiet day exactly as it would on a loud one.

## 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 plus the free wrap. 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

**My agent was watching a price for me, but I cannot prove what it actually saw. How do I prove it?** Save every reading, not just the alerts. On Zambo the watcher keeps one job for the watch: the baseline reading with its receipt and the rule, then every check as a saved step with the move against baseline, wrapped as one handover. Anyone can open it and check each price receipt at https://zambo.dev/verify/, so what the agent saw is a record, not its say-so.

**The price never crossed my line. Can the record prove the agent was even watching?** Yes, and that is why quiet readings get saved too. The handover on this page holds a baseline and a check minutes apart with a +0.046 percent move and no flag: a continuous, receipted series is the proof of watching, in a way an empty alert log never is.

**Does the receipt prove the price was correct?** No. A receipt proves the saved result was not changed since it was saved. It proves what your agent saw and recorded, which is what the watch is responsible for; the feed's own accuracy is a separate question.

**What does a watch cost?** The run on this page used 4 counted calls of the watcher's daily free 20. Around-the-clock multi-asset watches are what the Day Pass ($0.99, unlimited for 24 hours) and the Zambo Pass ($29 for 30 days) are for, one-time payments, never subscriptions.

## Related

- The index of receipt use cases: https://rambozambodotdev.gitlab.io/aer1-hub/receipt-use-cases.html
- The signal watch pattern guide: https://rambozambodotdev.gitlab.io/aer1-hub/signal-watch-package.html
- The scheduled agent heartbeat: https://rambozambodotdev.gitlab.io/aer1-hub/scheduled-agent-heartbeat.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/