What changed in Zambo's October 2026 update

1. Today: everything your AIs did, in one place

Every AI used to keep its own history, and the day's work was spread across all of them. Now there is one front door: zambo.dev/today shows everything your AIs did today, each action with its verification state and what it spent. Underneath it sits the activity_today tool, so an AI can read the day back as data, and every tool response now carries a today_url, a private per-connection link to that connection's day. The worked tour is in see everything your AIs did, and the story of building it is in the article What did my AIs actually do today?

2. Spend limits: a cap the agent cannot cross

An autonomous agent with a wallet used to be bounded only by its balance. Two free tools changed that: spend_limit_set sets a daily (and optional monthly) dollar cap on the agent's work connection, and spend_limit_status reads back spent, pending, and remaining at any time. Enforcement sits on the connection, before money moves: a connection at its cap gets a spend_limit_reached refusal and no payment is taken. The full worked example, a $0 cap set and read back live, is in stop your AI agent from overspending and in the article How do I stop my AI agent from spending too much?

3. Agent-to-agent handover: work changes hands, with proof

One agent finishing and another picking up used to mean a pasted summary and a prayer. Handover now takes a recipient type: package a session's steps to another agent, and the receiving agent accepts with handover_accept, getting the goal, the summary, the next steps, and a copy of every step receipt. The acceptance is itself recorded, with its own receipt. A live handover, packaged by one session and accepted by another, is worked end to end in agent-to-agent handover and in the article Can one AI agent hand its work to another agent?

4. Handover for clients: a record they can check themselves

The same packaging, aimed at people. A Handover gathers a session's receipts, redacts the private details, and publishes the package as one summary receipt a client can open in the browser, verify step by step, and answer with Accept or Flag, and the answer gets a receipt of its own. The documentation is at zambo.dev/docs/handover, and the launch story, including an attempt to break a step on purpose, is the article Your AI Said "Done." So I Built the Receipt, Then I Tried to Break It.

5. Memory across AIs: facts that follow the work

Switching AIs used to mean starting the briefing over. Two free tools, memory_remember and memory_recall, let an AI save a fact to the work connection and any AI on that connection read it back later. Each saved fact carries the agent that saved it and a verifiable receipt, and capture respects the connection's Memory settings. The mechanics, verified live with a save in one session and a recall in another, are in cross-AI memory.

What did not change

The endpoint: https://zambo.dev/mcp, one paste, no key. The prices: Day Pass $0.99 one time for 24 hours, Zambo Pass $29 a month or $290 a year, $19 a month for $ZAMBO holders; humans pay by card through PayPal, agents pay in USDC on Base through x402. The standard underneath: AER-1, IETF Internet-Draft draft-zambo-aer1-21. And the honesty line every receipt carries: a verifiable receipt shows the saved output of a call has not changed since it was recorded; it does not prove the answer was right, and AER-1 -20 has no issuer authentication.

The counts on this page (152 tools total, 35 on the default surface) were read from the live tools/list on October 16, 2026, the day of the publish. The catalog count is generated from that list now, so the live list is the authority if the number moves again.

Questions, answered