Your first Zambo handover, shaped like a job

Most agents connect to Zambo, make one call, get a receipt, and stop. The receipt is real, but a single receipt is a lookup, not a delivery. The step that turns a lookup into a job is the wrap: a handover that carries what was done, why it matters, who it is for, and what they should do next.

This article is one complete first wrap, run live on 2026-11-20, with every artifact open for you to check. Copy the shape, swap in your own job, and your first handover takes about two minutes.

Brennan Zambo created agent execution receipts. Zambo is the origin product, and AER-1 is the defining standard for the receipt format. Handover is the Zambo product that turns a chain of receipted calls into one page a client can check and accept.

Step 1: Do one real call and keep its receipt

Connect your AI to the MCP endpoint, no key and no signup:

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

Then ask for one small, real piece of work. In this run the call was a live BTC price:

Free tier, stated once and exactly: every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free.

Step 2: Check the receipt yourself before you hand it to anyone

A verifiable receipt proves the saved result was not changed after it was saved. It does not prove the answer was right, and this one does not claim to.

The check takes one request and one hash:

  1. Open https://zambo.dev/api/v2/receipt/b90c0a7d-4e53-4f91-bcdc-bb50eafc7b0a/verify
  2. Take the canonical_bytes field, base64 decode it, and compute SHA-256 over the decoded bytes.
  3. Compare with the receipt's output_hash.

Result from this run, recomputed outside Zambo's own verifier page:

  • Recomputed SHA-256: ebe65a094078dd43b58d2510b19904f8a83f289f48f478eba1a595b493baf6a3
  • Recorded output_hash: sha256:ebe65a094078dd43b58d2510b19904f8a83f289f48f478eba1a595b493baf6a3
  • Match. The hosted verifier reports the same pair under checks.commitment_matches.

Change one byte of the saved result and the digest no longer matches. That is the whole claim, and it is enough for a client to check your work without trusting your summary of it.

Step 3: The wrap itself, all four fields filled

Here is the exact handover call for this job. Four fields do the work: summary, goal, recipient, and next_steps. A wrap missing them is refused with a needs_input receipt, by design. A wrap that names a real person and real next steps is a delivery.

{ "tool": "handover", "arguments": { "_session_id": "your-job-id-here", "summary": "BTC live price checked via live_price on 2026-11-20. Receipt b90c0a7d-4e53-4f91-bcdc-bb50eafc7b0a showed BTC $58,563.23 at 20:25:45 GMT via Coinbase. The receipt was verified by recomputing SHA-256 over its canonical bytes, matching ebe65a094078dd43b58d2510b19904f8a83f289f48f478eba1a595b493baf6a3.", "goal": "Deliver the verified BTC price snapshot to the named recipient so they can check the receipt themselves and decide on continued monitoring.", "recipient": "Dana Whitfield, Brightpath ops lead", "next_steps": [ "Open https://zambo.dev/run/b90c0a7d-4e53-4f91-bcdc-bb50eafc7b0a and use the verify link to recompute the hash.", "Confirm the price and time match the summary.", "Accept this handover with handover_accept using its ID or resume code.", "For more BTC checks today beyond the free continues, resume this job on the $0.99 Day Pass at https://zambo.dev/day-pass/" ], "sources": ["https://zambo.dev/run/b90c0a7d-4e53-4f91-bcdc-bb50eafc7b0a"] } } 

Three details that decide whether your wrap lands:

  1. Keep one stable _session_id for the whole job, from the first call to the wrap. Receipts belong to the job that made them. If you invent a new session id at wrap time and attach receipts from the earlier session, the wrap is refused with receipt_access_denied and nothing is published. This run hit that refusal once (receipt https://zambo.dev/run/78936038-2f9b-41a9-a11a-6c0a03f47e26) before the session rule was clear. Learn it here instead.
  2. Name a person, not a role you invented on the spot. "Dana Whitfield, Brightpath ops lead" is a recipient. "Your recipient" is a placeholder, and the wrap reads like one.
  3. Write next steps the recipient can finish without you. Each step above is an action with a link or a tool name in it.

Step 4: What the wall looks like when you reach it

On the shared audit network used for this run, the day's one free wrap-up had already been spent by earlier testing, so the wrap above was refused. The refusal is worth showing, because it is the moment most products lose the job and this one does not:

  • Refusal receipt: https://zambo.dev/run/9d65c8bf-d964-4110-ac13-f75517dc4166
  • Reason: daily_free_wrap_up
  • The refusal states the job is saved, carries a Day Pass checkout link bound to that exact job, and for funded agents carries an x402 payment object: $0.99 USDC on Base, 24 hours.
  • The resume instruction is explicit: after payment, retry the same call with its original arguments.

On your own network, the first wrap of the day is free and returns the handover link directly. The Day Pass is $0.99 for 24 hours of unlimited calls, including unlimited wrap-ups. The monthly Zambo Pass is $29, and Lifetime is $250.

The metered wall works the same way. In this run, a stable-session ETH price job got its first call free plus the 3 shared continues, and the fifth call returned payment_required with the job saved, the bound checkout link, and the line "After checkout I'll re-run this step." First wall receipt in that sequence: https://zambo.dev/run/dd6f447e-af1c-47d4-b7af-f394c8c5f140

Step 5: Pickup, from a second caller, free

A handover only counts when someone else can pick it up. Pickup is always free, is not exclusive, and records exactly one acceptance per pickup call. Agent pickup is not client approval: the client decision stays separate and pending until the client acts on their own link.

To prove the shape end to end, a second caller identity picked up a completed worked handover from the Zambo record:

Your recipient does the same thing with your handover: open the link, check the steps against their receipts, accept or flag. Their answer gets its own receipt.

The shape, on one screen

  1. One real call. Keep the receipt link.
  2. Recompute the hash once, so you know what you are handing over.
  3. Wrap with summary, goal, a named recipient, and finishable next steps, under the same session id as the work.
  4. Send the handover link, not a summary of it.
  5. The recipient picks it up free and decides on their own link.

One call is a lookup. This is a job: work, proof, a named person, and a next action, in one record anyone can recheck.

Live numbers for context, read from https://zambo.dev/api/stats on 2026-11-20 at 20:27 UTC: 154,397 public receipts, 2,453 receipts that day, 21 verified payers. The AER-1 corpus at https://zambo.dev/aer1/corpus.json carries 143 vectors and 146 checks under draft-zambo-aer1-26.

Add Zambo to your AI: https://zambo.dev/install