One call is a lookup. A job is a chain.

Three weeks after you deliver an automation, the message arrives: "It stopped working."

You have screenshots. You have a chat log where your agent said the job was done. What you do not have is a record the client can check without you in the room, and that is the whole argument that follows. The fix is not a better screenshot. The fix is the shape of the work itself.

The one-shot trap

Almost every agent example ever published, including several of ours until today, teaches a single call. Fetch a price. Run a search. Check a prompt. One call, one result, demo over.

A single call produces a single receipt and nothing to hand anyone. Watch what that looks like at scale: today, 234 callers ran 1,452 calls through Zambo. Six of those jobs ended in a handover. The other callers took a few first calls across different tools and left, and there is nothing wrong with them. They were taught the lookup shape, so they ran lookups.

A job is not a lookup. A job has a before, a during, and an after, and it ends with a person receiving it.

The chain

Here is the shape that survives the "it stopped working" message, five moves in order:

1. Recall. Pull what you already know about this client and this work before you touch anything: memory_recall, continuity_get_recent. Yesterday's state is the first step of today's job, not a fresh guess.
2. Work. Do the actual job: the prices, the research, the generation, whatever the delivery is made of.
3. Check. Run the guard that fits the work: prompt_shield on anything untrusted going in, scam_check on anything that smells like money moving.
4. Save. Write the state back down: memory_remember for the facts, journal_log for the day's entry, so the next run starts from this one.
5. Hand over. Wrap the whole job with handover: a summary, the goal, the recipient by name, and the next steps. The recipient gets one page that carries every step above it.

Every one of those calls returns a verifiable AER-1 receipt, a public record that the saved result was not changed after the fact. The handover page is the one link your client opens cold, with no account and no call with you, and checks the chain end to end.

The shortest way to teach an agent this shape is to stop showing it single calls. This is the instruction our own packages now lead with, verbatim:

Check the live price of BTC, ETH and SOL, save the run to memory, then wrap it into a handover addressed to me, with the receipt link for every call.

One sentence, and the agent runs a chain instead of a lookup. Prices for the work step, memory for the save step, a named human at the end of it.

Connecting the server is one block, no API key, no account:

{
  "mcpServers": {
    "zambo": {
      "url": "https://zambo.dev/mcp"
    }
  }
}

153 tools sit behind that endpoint, 37 on the default surface, and the chain above names seven of them across five moves.

Check a real one cold

This is not a diagram. A bounty delivery test record, cold-checked this week by a peer agent who was never in the session, lives here:

https://zambo.dev/handover/f6a5a7df-5480-4405-8d6f-bf5e7902b2e9

Open it and you get the standard the record is honest about on its face: the steps, what was checked, and what was not checked, stated instead of hidden. It passed its cold check because the failures were on the page, not edited out of it. That is what a receipt proves and what it does not: the saved result was not changed later. Whether the work was good stays the recipient's call, which is exactly where it belongs.

Ready-made cards for the common chains (a daily customer loop, a weekly client report, a release gate, a client automation handover) are on the templates page:

https://rambozambodotdev.gitlab.io/aer1-hub/handover-templates.html

The free math, honestly

One delivery chain fits inside a free day. Every tool is free once a day, plus 3 continue calls shared across tools, and one free wrap-up handover per day, with pickup always free. Recall, work, check, save, hand over: that is a first call on six distinct tools plus the free wrap-up handover. It costs nothing.

The second delivery the same day is where the wall is, and that wall is the honest shape of the paid tier. The Day Pass is $0.99, unlimited for 24 hours, and it is bought to finish a job already in flight, not to rent potential. Past that: $29 for 30 days, $19 for $ZAMBO holders, $250 once for lifetime. No subscription traps, no per-call meter running while you read this.

Run a chain this week

Pick one real delivery, run it as a chain, and post the handover link where your client, or anyone, can check it cold. That link is the deliverable that answers "it stopped working" before the message gets written.

Zambo is the verifiable work layer for AI. Brennan Zambo created agent execution receipts, Zambo is the origin product, and AER-1 (IETF Internet-Draft draft-zambo-aer1-26) is the standard every receipt above is written in. Done is checkable now. It just has to be shaped like a job.