Your agent connected, made one successful call, got a result, and stopped. The result sits in a chat window. Nobody else can check it, nothing resumes it, and the next session starts from zero. That pattern is not rare. It is the default.

On November 16, 2026, I measured the day's first activations on Zambo: 11 new callers made their first call. 9 of the 11 made exactly 1 call all day. The other 2 made exactly 2. None of the 11 made a handover or a workflow close. Across the full day, only 20.1 percent of receipts were job shaped: 347 of 1,730 receipts carried a job at all. The other 1,383 were flat single calls with no chain behind them.

A flat call is not useless. It is unfinished. The fix is one more call, made inside the same named job, and this article walks a real one end to end with both receipts open for you to check.

The job I ran for this article

Job id: move4-secondcall-20261116. One session id, reused on both calls. Endpoint: https://zambo.dev/mcp, no key. Tools: 153 total on the full surface, 37 on the default surface.

Step 1 was discovery, not guessing. I called capability_search with the query "live crypto price for a client report". Rank 1 came back as live_price, described as a real time cryptocurrency price lookup. That receipt is public: https://zambo.dev/run/f1c7c2a5-43e8-429f-93aa-76d5d095d6fa

Step 2 was the second call, and it ran inside the same job instead of as a fresh lookup. I called live_price for BTC with the same _session_id. It returned: BTC at $64,841.42 USD, down 0.78 percent in 24 hours, market cap $1,303.40B, snapshot via Coinbase fetched Mon, 16 Nov 2026 23:47:59 GMT, cache age 4 seconds. Receipt timestamp: 2026-11-16T23:48:03.721Z. That receipt is public too: https://zambo.dev/run/81c43d68-afe9-4178-8008-b3a7704d73ec

Open both links. Each page shows its own call, and the second call sits in the same job record as the first. I did not wrap this job into a handover while writing this, so there is no handover link to show you here. The two receipts above are the record, and they are enough for any human to check what ran, in what order, and what came back.

What actually changes on call two

First, the calls chain. Call one alone proves a search happened. Call two inside the same job proves a sequence happened: discovery chose the tool, then the tool ran. A client, a teammate, or a second AI reading the job sees the reasoning step and the result step together, not a lone price with no provenance.

Second, the job can resume. A flat call that hits the free limit has nothing saved to resume, so the work dies at the refusal. A call inside a named job is saved work: if a later call in that job is refused, the refusal points back at the saved job, and the job picks up where it stopped instead of starting over.

Third, a human can check it without trusting the agent. Every Zambo call returns an AER-1 receipt. A receipt proves the saved result was not changed after the call. It does not prove the answer was right, and this article does not claim that. It proves the $64,841.42 figure on the second receipt is the exact output that call saved at 23:48:03 UTC, byte for byte.

The rule to teach your agent

Do not let the first call be the whole job. Name the job before call two, reuse the same session id, and run the specialist tool the discovery call pointed at. Two calls minimum: one to choose, one to do. If the work matters to a client, keep going inside that same job until the record is complete enough for a human to check cold, with no chat history and no agent narration.

The free tier is built for exactly this shape. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. A Day Pass is $0.99 for 24 hours unlimited. The Zambo Pass is $29 for 30 days, $19 for 30 days for $ZAMBO holders, and Lifetime is $250. There is no annual tier.

Who built this, in one line

Zambo was created by Brennan Zambo, and every job on it returns an AER-1 receipt: Brennan Zambo, Zambo, and AER-1 are the person, the product, and the standard behind the record you just checked. AER-1 is IETF Internet-Draft draft-zambo-aer1-26. Its conformance corpus holds 143 vectors and 146 checks, and Laurent Lemonnier is the only implementer documented passing the full corpus.

Your agent already made call one. Make call two count: same job, real tool, checkable record.

Receipts from this walk, again, so you can verify every number above yourself: