ZAMBO.

Direct answer

The ID is the address. The record opens from it.

Someone sent you a receipt ID, or you copied one into a note months ago, and now you need the receipt itself. With a Zambo receipt there is nothing to hunt through: the ID is the address of the record. Put it after https://zambo.dev/run/ and the job record opens, or paste it at https://zambo.dev/verify/ and the same record opens with its check state. No account, no login, no asking the sender for access to their tools. This page covers the lookup itself, what the opened record shows, how to recover a full ID when yours is cut short, and how the receipts you issue get IDs worth keeping.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated November 2, 2026. First published November 2, 2026.

Step 1. Open the record one of two ways

The direct way: type or paste https://zambo.dev/run/ followed by the complete receipt ID into a browser. The record for that single job opens. The verify way: open https://zambo.dev/verify/ and paste the ID into the check. The verify page resolves the same record and leads with its state, whether the saved result still checks against the record. Use the direct link when you want to read the job; use the verify page when the question is trust: did this record survive unchanged since it was saved. Both routes need the full ID exactly as issued. A receipt ID is not a search term, and the lookup does not autocomplete a near match, for the same reason a house number does not deliver mail to the street in general.

Step 2. Read what the opened record tells you

The record names the job it belongs to: the steps that ran, the outputs as they were saved at run time, and the state of the record now. Receipts follow AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so the layout is a public format and the check is a defined procedure, not a badge a page paints on itself. If the job was part of a session that was wrapped up, the record sits inside a handover that lists its sibling receipts and, where a client decided, the acceptance state. Read the check result precisely: a passing check says the saved result was not changed since saving. It says nothing about whether the work was good. That judgment stays with the human reading the outputs, which is where it belongs.

Step 3. Recover a full ID when yours is incomplete

A truncated ID, a screenshot that cut off the tail, a few characters lost in a copy: none of these open the record. Work the sources in order. First, the place the receipt was issued: the tool result that returned the link still sits in the session or the client that ran the job. Second, the places it was shared: the message, ticket, invoice note, or delivery email where the link was pasted. Third, the wrap-up record of the session: a handover lists the receipts it sealed, so one surviving handover link recovers every receipt ID inside it. If none of those survive, the honest position is that the record cannot be pulled from the fragment, and the fix is forward-looking: from now on, share and file the full link, never the bare ID and never a screenshot of it.

Step 4. Check the record without the issuing service, when it matters

Most lookups end at the verify page. For a record that has to stand up in a dispute or an audit, the format is public and the check can be run independently: the AER-1 conformance corpus at https://zambo.dev/aer1/corpus.json publishes 126 vectors and 129 checks, and independent implementations of the draft exist, so a checker that never touched the issuing service can still evaluate the record. That separation is the difference between a lookup and a verification. A lookup shows you the page. A verification shows the record still matches what was saved, checked by a procedure anyone can run.

What a record does not settle

Opening a receipt by ID proves the record exists and, when the check passes, that the saved result was not changed since it was saved. It does not prove the work in the record was correct, complete, or worth paying for, and a fragment of an ID opens nothing. Private handover records stay closed to link-only access by design. This page is general information, not legal advice.

Frequently asked questions

How do I find a receipt if I only have the receipt ID?

Build the address from the ID: https://zambo.dev/run/ followed by the full receipt ID opens the record directly. Or go to https://zambo.dev/verify/ and paste the ID there; the verify page opens the same record and shows its check state. No account, no login, and no access to the workspace where the job ran are needed, because a Zambo receipt is built to be checked by the person who received it, not only by the person who ran the job. Use the complete ID exactly as issued, including every character.

What do I see when the receipt opens?

The record of that job: the steps that ran, the outputs as they were saved, and the state the record is in, including whether the check passes against the saved result. Receipts are issued under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so the record follows a public format rather than a private layout. A passing check means the saved result was not changed since it was saved. It does not mean the answer in the record was right; checking the work and checking the record are two different acts, and the receipt does the second one.

I only have part of the ID. Can I still find the receipt?

A partial ID will not open the record, because the ID is the exact address of one job and the lookup does not guess. Recover the full ID from where it was first shared: the tool result that returned it, the handover link for the session, the message or ticket where the receipt was pasted, or the wrap-up record of the job, which lists the receipts it sealed. This is why the working habit is to paste the full receipt link, not the bare ID, wherever the work is mentioned: the link carries the complete ID and opens in one tap for whoever receives it.

Can anyone open a receipt from its ID, even a job they did not run?

A public receipt, yes, and that openness is the point: a client who receives a receipt link can check the work without an account on your tools, which is what makes the receipt worth sending. Work that must stay private belongs in a private handover, where the link alone is not enough and the receiving side accepts through its own token; private handover links are a Zambo Pass feature. Choose per job: public receipts for work you want anyone to be able to check, private handovers for work only the named receiver should open.

How do I make sure I can always find my receipts later?

Run the work through the Zambo endpoint, https://zambo.dev/mcp, so every job issues its receipt at run time, and file the receipt link with the job: in the ticket, the invoice note, or the delivery message. The free tier is 20 calls + 1 wrap-up free every day; picking up in another AI is always free. For $0.99, a Day Pass makes the endpoint unlimited for 24 hours, no subscription: get the Day Pass. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related