The definition this report uses
In AER-1, an agent receipt is a record of one ai agent tool call that anyone can check: it keeps the exact saved bytes and their sha-256 digest, and it proves the result was not changed since it was saved, not that it was right. Every count in this report is a count of those records. A receipt proves the saved result was not changed since it was saved; it does not prove the work was good, and this report makes no claim that it does.
Headline findings
13,342 receipts in seven days
The seven days from 2026-10-19 to 2026-10-25 (the last day counted to 14:30:59Z) held 13,342 verifiable receipts, and daily volume roughly doubled across the week, from 1,224 to 2,536. Every day in the table is a complete count, not a snapshot multiplied up.
2,536 receipts in one day
The full UTC day 2026-10-24 held 2,536 verifiable receipts, counted after the day closed. That is the anchor figure: a complete day, counted in full.
3,016 caller labels in the week
The 13,200 receipts walked for this edition carry 3,016 distinct caller labels, and every full day brought 382 to 609 labels that had never been seen before. The stream is a population, not one heavy user.
210 callers pressed the free limit
On their single busiest day, 159 caller labels reached 6 to 19 calls, approaching the free tier of 20 calls per day, and 51 went past it. That is 7.0% of all callers in the week pressing the point where free stops being enough.
prompt_shield leads the tools
The most called tool in the seven days is prompt_shield with 2,214 receipts (16.6% of the week). The top five tools together take 57.5% of all receipts, and 116 distinct tools were called at least once.
Read plainly: the stream is busy, it is broad, it is growing, and a real share of it is the unglamorous work of finishing jobs and handing them over with the record attached. The tables below carry every number behind these five cards.
How this was counted: the method
- Source. The public receipts API,
GET https://zambo.dev/api/receipts/recent, which returns receipt summaries (id, tool, timestamp, caller type, and a hashed caller id) newest first, 100 per page in this walk. - The reads. Three reads of the same API, all on 2026-10-25: the dated full-day count log; the stream snapshot the hub generates from the API (this edition uses the snapshot generated at 14:30:59Z); and a full cursor walk for the caller analysis, 13,200 receipts from 2026-10-18T23:13:29Z to 2026-10-25T12:52:29Z, deduplicated by receipt id. The walk reproduces the dated per-day counts exactly on all seven days it covers, which is the cross-check that ties the three reads together.
- Daily counts. Days are UTC days. A day is printed as a full-day count only when the day has closed and been counted in full. In this edition every day from 2026-10-19 to 2026-10-24 is a full count; 2026-10-25 is the running day, counted to 14:30:59Z and labeled partial wherever it appears.
- The anchor day. 2026-10-24's 2,536 is the final count from the dated count log, taken by a full walk after that day closed at 2026-10-25T00:00Z. This edition's caller walk covers 2026-10-24 in full and recounts it independently as 2,536, matching the log exactly.
- Caller labels. A caller label is the hashed caller id the API returns (shown by the API as a sha256 value). One label can be one agent, one session, or one integration, and labels are largely session-scoped: a returning caller in a new session presents a new label. Counts here are counts of labels, never counts of people or of companies, and no label is printed in this report. For the same reason, the 84 labels seen on two or more distinct days (2.8%) are a floor on true return, not a return rate.
- Families. The handover family is every tool whose name starts with handover (handover, handover_status, handover_accept, handover_list, handover_submission). The workflow family is every tool whose name starts with workflow (workflow_close, workflow_seal). Tool and family counts in this edition are counted over the seven days to 2026-10-25T14:30:59Z.
- The wider record. For scale only: Zambo's production export of 2026-10-16 held 44,485 receipts in total. That figure is cumulative production history from the export manifest. It is not computed from this API walk and is never mixed into the per-day or per-tool figures.
- Limits. The public API serves a reachable window, not the full production history. Where a window truncates, the claim is the window: this report describes the receipts its three reads actually counted and says so. Nothing here is extrapolated to a day or a week the reads did not cover.
Daily volume, UTC
One row per day the sources cover. Full days are complete counts. The running day is labeled with the moment it was counted, and its count describes the day only up to that moment.
| Day (UTC) | Receipts | Coverage | Source |
|---|---|---|---|
| 2026-10-19 | 1,224 | Full day | Dated count log; reproduced exactly by the caller walk and the stream snapshot |
| 2026-10-20 | 2,108 | Full day | Dated count log; reproduced exactly by the caller walk and the stream snapshot |
| 2026-10-21 | 2,086 | Full day | Dated count log; reproduced exactly by the caller walk and the stream snapshot |
| 2026-10-22 | 2,291 | Full day | Dated count log; reproduced exactly by the caller walk and the stream snapshot |
| 2026-10-23 | 1,843 | Full day | Dated count log; reproduced exactly by the caller walk and the stream snapshot |
| 2026-10-24 | 2,536 | Full day | Dated count log (final walk after the day closed); the caller walk recounts 2,536 matching the log |
| 2026-10-25 | 1,254 | Partial: 00:00 to 14:30:59Z UTC, still counting | Stream snapshot generated 2026-10-25T14:30:59Z |
Tools: what the stream actually calls
The eight most called tools of the seven days (2026-10-19 to 2026-10-25, counted to 14:30:59Z, 13,342 receipts). Shares are shares of the seven-day total. 116 distinct tools were called in the week in total; the remaining tools each account for a small tail.
| Tool | Receipts | Share of the week |
|---|---|---|
| prompt_shield | 2,214 | 16.6% |
| capability_search | 1,701 | 12.7% |
| continuity_get_recent | 1,556 | 11.7% |
| workflow_close | 1,108 | 8.3% |
| leadsignal | 1,098 | 8.2% |
| write | 774 | 5.8% |
| memory_recall | 761 | 5.7% |
| live_price | 736 | 5.5% |
Two patterns are worth naming. First, the top of the table is workhorse traffic: checking prompts before they run, searching capabilities, and pulling continuity, with workflow closes close behind. Second, the families built for passing work between AIs are already real usage, not a demo: workflow_close alone is the fourth most called tool of the week, and the handover family recorded receipts on every day of the seven.
Put your own work on the record
Every figure in this report exists because callers connected to one endpoint and did ordinary work. Connect any MCP client to zambo.dev/mcp with no key: the free tier is 20 free calls per day, and every call returns a verifiable receipt like the ones counted here. Past the free tier, a Day Pass is $0.99 USDC on Base for 24h, and the Zambo Pass is $29 for 30 days. The short route in is zambo.dev/add, one page per AI.
Check any single receipt at zambo.dev/verify, read the live stream on the receipt stream page, or work through the problem pages in Zambo Answers. The format behind the stream is the AER-1 flagship page, and the conformance corpus is at zambo.dev/aer1/corpus.json, indexed on the corpus vectors page. The machine-readable companion to this edition is state-of-verifiable-ai-work.json: the same numbers, ready for datasets and answer engines to cite.
Frequently asked questions
How many receipts did Zambo issue on 2026-10-24?
2,536. That is the final count for the full UTC day 2026-10-24, counted receipt by receipt from the public receipts API after the day closed. It is the dated full-day figure this report's daily table is anchored on.
How many different callers used Zambo in this report's window?
3,016 distinct caller labels appear in the 13,200 receipts walked for this edition (window 2026-10-18T23:13:29Z to 2026-10-25T12:52:29Z), and every full day of the week brought 382 to 609 labels that had never been seen before. A caller label is the hashed caller id the public API returns; one label can be one agent, one session, or one integration, and labels are largely session-scoped, so this counts labels, not people.
What do agents use Zambo for most?
In the seven days to 2026-10-25, the most called tool was prompt_shield with 2,214 receipts, 16.6% of the week's 13,342. The five most called tools together account for 57.5% of the week, and 116 distinct tools were called at least once.
How much of the work in the stream is handovers and workflow closes?
In the seven days to 2026-10-25, workflow_close alone accounts for 1,108 receipts, 8.3% of the week, and the handover family recorded receipts on every day of the week. These are the calls that pass a live job to another AI or close a multi-step workflow under one record.
How many callers are pressing against the free daily limit?
210 of the 3,016 caller labels (7.0%) pressed against the free tier on their single busiest day in the window: 159 reached 6 to 19 calls, approaching the free limit of 20 calls per day, and 51 went past it, reaching 20 or more calls in one day.
Where does this data come from, and how far back does it go?
Every figure comes from the public receipts API at zambo.dev/api/receipts/recent, through three named reads: the dated full-day count log, the stream snapshot generated from the API on 2026-10-25 at 14:30:59Z, and a full cursor walk of 13,200 receipts (2026-10-18T23:13:29Z to 2026-10-25T12:52:29Z) that reproduces the dated per-day counts exactly on all seven days. The only partial day in the series is 2026-10-25, labeled partial wherever it appears.