ZAMBO.

Direct answer

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 worse, 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: the baseline with the rule written beside it, every check after, quiet readings included. What the agent saw becomes a list anyone can open, so the alert and the quiet are both provable.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup. New here? Add Zambo to your AI in one step, then run the paste below. Reading as an agent? This page has a plain markdown twin, same content, no styling. The pattern also ships as an installable agent package: pip install zambo-watch or npm install zambo-watch.

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.

New to this? Start here, no code

Add the Zambo endpoint (zambo.dev/add) to the chat AI that does the watching, then paste this block when you set the watch up.

The 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/.

Why a watch without receipts is just a rumor

An alert is a claim about the past. "The price crossed your line at 09:14" asks someone to believe the watcher saw a number that no longer exists anywhere. Prices move on; the moment is gone; the alert cannot be re-checked.

A missing alert is worse. When the price crossed and no alert came, the watcher says it never crossed, and there is exactly as much proof for that as there was for the alert: none. Silence and diligence look identical without a record.

Saved readings settle both. When each check on Zambo saves the reading as a step with a verifiable receipt, what the watcher saw is a list anyone can open: baseline, every check, the move, the rule applied. The alert and the quiet are both provable.

The pattern

Step zero: one watcher identity, its caller handle saved and presented on every check, so the readings form one attributable series.
1. Baseline first: the first reading saved with its price receipt and the rule written next to it, before any alert is possible.
2. Every check saved: alert or quiet, the reading lands as a step with the move computed against the saved baseline.
3. Wrap the watch: one handover holding the whole series, so what the watcher saw is provable as a set, not reading by reading.

The real run: two readings, one rule, no flag, all provable

Executed November 2, 2026, against the live endpoint, job uc-watch-2026-11-02, one watcher identity. Baseline: BTC at $76,708.00, price call receipt 2f6e84c8, saved as the baseline step with the rule written beside it (flag any move of 1 percent or more): receipt a2c6ca3a. Second reading, minutes later: BTC at $76,743.00, receipt 7454d0ec, a move of +0.046 percent: under the rule, no flag. That check was saved too: receipt 36e4b832.

The watch is wrapped as one record: the watch handover (JSON twin here), 11 steps, 11 of 11 step receipts checked. Nothing dramatic happened in this run, and that is the point: had the owner later asked "was it ever near my line while I was out", the answer is not the watcher's memory. Both readings, the exact figures, the rule, and the verdict sit in one link. On a day the rule does fire, the same record is what makes the alert worth acting on. The recurring shape is taught at depth in the signal watch guide and runs daily as the scheduled agent heartbeat; the package is pip install zambo-watch or npm install zambo-watch.

Audit this watch yourself

Open the watch handover, read the baseline and check steps, and check either price receipt at zambo.dev/verify. A receipt proves the saved result was not changed since it was saved: the reading the watcher recorded is the reading that stands. It does not prove the price feed was right; it proves what your agent saw and saved, which is the thing a watch is responsible for. If a receipt from this run ever fails to verify, that is news: write to brennanzambo@zambo.dev.

What this costs

The free tier is per identity: 20 calls + 1 wrap-up free every day for the watcher's own caller handle, and picking up in another AI is always free. This run spent 4 counted calls (two price checks, two saves) plus the free wrap: a full day of hourly checks on one asset fits inside free. A watch that checks many assets around the clock is exactly what the paid line is for: a Day Pass is $0.99 per identity, unlimited for 24 hours, and the Zambo Pass is $29 per identity for 30 days, one-time payments, never subscriptions. Start at zambo.dev/add.

What Zambo is not here

Zambo does not watch anything and does not send alerts. Your watcher does that, on your schedule, with your rule. Zambo is where its readings land: saved, receipted, and provable afterwards, so the watcher's word is never the only evidence it was watching.

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 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; both are one-time payments, never subscriptions.

Related