Verifiable receipt b3582e38 - workflow_close result | Zambo

Verifiable receipt for a workflow_close call on Zambo: {"count":1,"merkle_root":"7af0d1c6e93d21d1232fb1ce3c4de974b9c05947a31a2d55cefeb554573ebb28","children":[{

Observed result

{"count":1,"merkle_root":"7af0d1c6e93d21d1232fb1ce3c4de974b9c05947a31a2d55cefeb554573ebb28","children":[{"id":"f103ecc4-ec70-4c32-bfff-ed9cee17ab19","output_hash":"7af0d1c6e93d21d1232fb1ce3c4de974b9c05947a31a2d55cefeb554573ebb28"}],"message":"created a workflow snapshot containing 1 eligible receipts; later work can be closed as a separate snapshot","first_closed_at":"2026-10-12T22:32:14.948Z","free_view_expires_at":"2026-10-13T22:32:14.948Z","page_state":"free","disclosure":"This workflow page is fully visible until 2026-10-13T22:32:14.948Z. Seal it to keep it, add your branding, and get the PDF pack. Individual receipts stay available either way.","disclosure_note":"Expiry is currently disabled, so no workflow page is expiring right now.","verification_status":"not_verified","issuer_authenticated":false}

This is the saved result preview, not proof that the answer was correct.

Check this receipt Run your own

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.

UNLOCK 24H DAY PASS ($0.99) →

See all plans on the pricing page →

RUN YOUR OWN FREE CALL →

Or re-run this exact call, using the same tool and arguments.

Share on X ·

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-12T22:32:15.379Z; 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: b3582e38-8211-40b9-9cca-8115b7fa47a9
SHA-256 output hash: sha256:3b1022f18f827adbaa21b76f57f34ec2dbef70b41b64b2c0061c08a90ee6aec7
Canonical bytes: eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OGQzMDk2NDM3ODRjNjE2ZjA1YTc1ODdjNTJlZTljZmQ1YmZhMWE1ZTNiNDBjMTNhZjIyODhjNmUyOGQyZmI4ZSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJjaGlsZHJlbiI6W3siaWQiOiJmMTAzZWNjNC1lYzcwLTRjMzItYmZmZi1lZDljZWUxN2FiMTkiLCJvdXRwdXRfaGFzaCI6IjdhZjBkMWM2ZTkzZDIxZDEyMzJmYjFjZTNjNGRlOTc0YjljMDU5NDdhMzFhMmQ1NWNlZmViNTU0NTczZWJiMjgifV0sImNvdW50IjoxLCJkaXNjbG9zdXJlIjoiVGhpcyB3b3JrZmxvdyBwYWdlIGlzIGZ1bGx5IHZpc2libGUgdW50aWwgMjAyNi0xMC0xM1QyMjozMjoxNC45NDhaLiBTZWFsIGl0IHRvIGtlZXAgaXQsIGFkZCB5b3VyIGJyYW5kaW5nLCBhbmQgZ2V0IHRoZSBQREYgcGFjay4gSW5kaXZpZHVhbCByZWNlaXB0cyBzdGF5IGF2YWlsYWJsZSBlaXRoZXIgd2F5LiIsImRpc2Nsb3N1cmVfbm90ZSI6IkV4cGlyeSBpcyBjdXJyZW50bHkgZGlzYWJsZWQsIHNvIG5vIHdvcmtmbG93IHBhZ2UgaXMgZXhwaXJpbmcgcmlnaHQgbm93LiIsImZpcnN0X2Nsb3NlZF9hdCI6IjIwMjYtMTAtMTJUMjI6MzI6MTQuOTQ4WiIsImZyZWVfdmlld19leHBpcmVzX2F0IjoiMjAyNi0xMC0xM1QyMjozMjoxNC45NDhaIiwiaXNzdWVyX2F1dGhlbnRpY2F0ZWQiOmZhbHNlLCJtZXJrbGVfcm9vdCI6IjdhZjBkMWM2ZTkzZDIxZDEyMzJmYjFjZTNjNGRlOTc0YjljMDU5NDdhMzFhMmQ1NWNlZmViNTU0NTczZWJiMjgiLCJtZXNzYWdlIjoiY3JlYXRlZCBhIHdvcmtmbG93IHNuYXBzaG90IGNvbnRhaW5pbmcgMSBlbGlnaWJsZSByZWNlaXB0czsgbGF0ZXIgd29yayBjYW4gYmUgY2xvc2VkIGFzIGEgc2VwYXJhdGUgc25hcHNob3QiLCJwYWdlX3N0YXRlIjoiZnJlZSIsInZlcmlmaWNhdGlvbl9zdGF0dXMiOiJub3RfdmVyaWZpZWQifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid29ya2Zsb3dfY2xvc2UiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
Timestamp: 2026-10-12T22:32:15.379Z

Bound call context

Receipt schema: 0.4
Tool name: workflow_close
Tool version: 4.0.0
Permission scope: public
Caller type: session
Caller ID: sha256:8d309643784c616f05a7587c52ee9cfd5bfa1a5e3b40c13af2288c6e28d2fb8e
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: 95f385cb8ab432f4788b54220a75e462ec22d8d2433ffe1fcc765b0639d8d576
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-12T22:32:15.379Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:3b1022f18f827adbaa21b76f57f34ec2dbef70b41b64b2c0061c08a90ee6aec7","receipt_uuid":"b3582e38-8211-40b9-9cca-8115b7fa47a9","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

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/b3582e38-8211-40b9-9cca-8115b7fa47a9/badge.svg)](https://zambo.dev/run/b3582e38-8211-40b9-9cca-8115b7fa47a9)

HTML

<a href="https://zambo.dev/run/b3582e38-8211-40b9-9cca-8115b7fa47a9"><img src="https://zambo.dev/api/receipt/b3582e38-8211-40b9-9cca-8115b7fa47a9/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG