Verifiable receipt f04c308f - continuity_get_recent result | Zambo
Verifiable receipt for a continuity_get_recent call on Zambo: {"status":"ok","events":[],"has_more":false,"cursor":null,"next_cursor":null,"handoff_text":"No ve
Observed result
{"status":"ok","events":[],"has_more":false,"cursor":null,"next_cursor":null,"handoff_text":"No verified work is saved for this job yet.\nRun a Zambo tool with the same job ID to add a receipt-backed step.\nA matching receipt shows the saved record was not changed. It does not prove the answer is right or that an outside action happened.\nAny AI client label shown here was reported by the caller and is not independently verified.","privacy":{"capture_enabled":true,"global_capture_enabled":true,"per_ai":[],"note":"New anonymous sessions start with capture off. A verified Pass starts with capture on. These settings only control future private timeline entries. Public receipts remain available."}}
Check this receipt
This record shows the result and timestamp stored for the call. Recompute the SHA-256 commitment from the saved bytes in your browser; signatures and chain proofs are not checked.
Provenance for every timeline entry
- EXECUTED BY ZAMBOZambo ran the tool call itself.
- OBSERVED VIA GATEWAYA Zambo gateway observed request and response bytes from the named external executor. Zambo did not run that external action.
- LOGGED BY AGENTAn agent or local hook reported the action. Zambo attests that the record is unchanged since logging, not that the action happened as described.
Private agent reasoning, built-in client actions, and direct calls to unrelated MCP servers are not included unless an agent or gateway reports them.
What is this?
Zambo's receipt store reports a tool call and records its result. The SHA-256 commitment covers the exact canonical bytes. The provenance label is bound to v0.4 receipt bytes when that check passes, but no pinned signature or trusted issuer key is checked. An anchor can timestamp a fingerprint; it does not authenticate the issuer.
What is an execution receipt?
An execution receipt is a public record of a reported AI agent tool call. Its byte commitment and provenance claim can be checked independently; neither alone authenticates the issuer. Read the canonical definition of an AI agent execution receipt.
Keep the work moving
This receipt records a completed tool call. When the free allowance is not enough, choose the access path that fits the job.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
Verification checks
- SHA-256 commitment: Checked independently against the exact decoded bytes
- Provenance binding: PASS; The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
- Metadata binding: PASS; metadata_hash matches the canonical metadata block.
- Issuer authentication: NOT CHECKED; no pinned signing key or trusted issuer was supplied
- Signature: NOT CHECKED; no Ed25519 signature or pinned key is supplied
- Chain: NOT CHECKED; no append-only chain proof is validated
- Stored timestamp: 2026-10-10T13:02:56.021Z; external immutability is not checked
Want a verifiable receipt for every job your bots do?
Add Zambo Receipt Bot to your team · File this in Receipt Bot
Committed provenance claim
EXECUTED BY ZAMBO
The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
- Receipt ID
f04c308f-a942-4b38-ac7a-af8f7b9eeb79- SHA-256 output hash
sha256:61d96e745a01b309be002d7acc1676dd56c41df82744181e94a95df59675f667- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MmQ2MmExMmMwMTVjMTRhYWNhMGFlYjgxYjExNjBlODNmZGE4ZTllZTBjM2YxOWI3NTQ4ZmUwZWI4MDU4MjBmYiIsImxhYmVsIjoiYXVkaXQtY29udCIsImxhYmVsX3NvdXJjZSI6ImNhbGxlcl9yZXBvcnRlZCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJjdXJzb3IiOm51bGwsImV2ZW50cyI6W10sImhhbmRvZmZfdGV4dCI6Ik5vIHZlcmlmaWVkIHdvcmsgaXMgc2F2ZWQgZm9yIHRoaXMgam9iIHlldC5cblJ1biBhIFphbWJvIHRvb2wgd2l0aCB0aGUgc2FtZSBqb2IgSUQgdG8gYWRkIGEgcmVjZWlwdC1iYWNrZWQgc3RlcC5cbkEgbWF0Y2hpbmcgcmVjZWlwdCBzaG93cyB0aGUgc2F2ZWQgcmVjb3JkIHdhcyBub3QgY2hhbmdlZC4gSXQgZG9lcyBub3QgcHJvdmUgdGhlIGFuc3dlciBpcyByaWdodCBvciB0aGF0IGFuIG91dHNpZGUgYWN0aW9uIGhhcHBlbmVkLlxuQW55IEFJIGNsaWVudCBsYWJlbCBzaG93biBoZXJlIHdhcyByZXBvcnRlZCBieSB0aGUgY2FsbGVyIGFuZCBpcyBub3QgaW5kZXBlbmRlbnRseSB2ZXJpZmllZC4iLCJoYXNfbW9yZSI6ZmFsc2UsIm5leHRfY3Vyc29yIjpudWxsLCJwcml2YWN5Ijp7ImNhcHR1cmVfZW5hYmxlZCI6dHJ1ZSwiZ2xvYmFsX2NhcHR1cmVfZW5hYmxlZCI6dHJ1ZSwibm90ZSI6Ik5ldyBhbm9ueW1vdXMgc2Vzc2lvbnMgc3RhcnQgd2l0aCBjYXB0dXJlIG9mZi4gQSB2ZXJpZmllZCBQYXNzIHN0YXJ0cyB3aXRoIGNhcHR1cmUgb24uIFRoZXNlIHNldHRpbmdzIG9ubHkgY29udHJvbCBmdXR1cmUgcHJpdmF0ZSB0aW1lbGluZSBlbnRyaWVzLiBQdWJsaWMgcmVjZWlwdHMgcmVtYWluIGF2YWlsYWJsZS4iLCJwZXJfYWkiOltdfSwic3RhdHVzIjoib2sifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiY29udGludWl0eV9nZXRfcmVjZW50Iiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=- Timestamp
Bound call context
- Receipt schema
0.4- Tool name
continuity_get_recent- Tool version
4.0.0- Permission scope
public- Caller type
session- Caller ID
sha256:2d62a12c015c14aaca0aeb81b1160e83fda8e9ee0c3f19b7548fe0eb805820fb- Caller-reported label
- audit-cont (caller_reported, not authenticated team ownership)
- Declared side effects
none- Side-effects schema
zambo-side-effects/1- Declaration hash
sha256:45aad38f3aa982b9aafe92ecb416ebe98791eddbaf8ab6df0bd08605b7c1bfee
This records what the server-side tool contract declared at call time. It does not independently verify that a downstream side effect happened.
Bound upstream evidence
- Status
- no_upstream_bytes_captured
- Evidence SHA-256
unavailable- Byte length
- unavailable
Neutral Nostr anchor
- Event ID
69d66978a05caa5295b9a923e50353de52fdc6c4c984f51acb17350d5291f3c2- Anchor status
- published
- Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41
Relay hints: wss://relay.damus.io · wss://nos.lol · wss://relay.primal.net
Schema: zambo-receipt-anchor/1
Anchor envelope bytes:
{"anchored_at":"2026-10-10T13:02:56.021Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:61d96e745a01b309be002d7acc1676dd56c41df82744181e94a95df59675f667","receipt_uuid":"f04c308f-a942-4b38-ac7a-af8f7b9eeb79","schema_version":"zambo-receipt-anchor/1"}
Anchor status "published": Published to all configured relay targets.
Check this hash yourself
API v2 status: verified. This status summarizes the v2 commitment and provenance checks; it does not prove the answer was correct. Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. See the Nostr anchor event on a public viewer. The fingerprint is timestamped outside Zambo too.
Embed this receipt
Markdown
[](https://zambo.dev/run/f04c308f-a942-4b38-ac7a-af8f7b9eeb79)
HTML
<a href="https://zambo.dev/run/f04c308f-a942-4b38-ac7a-af8f7b9eeb79"><img src="https://zambo.dev/api/receipt/f04c308f-a942-4b38-ac7a-af8f7b9eeb79/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
41,787 verifiable receipts minted
Run your own calls. Free, 20 free calls per metered tool each day, no account.