Verifiable receipt bfa06bae - workflow_close result | Zambo

✓ This result hasn’t changed since it was saved.

Saved:
What was asked: The request recorded for this receipt.

Zambo is the verifiable work layer for AI.

Zambo is the verifiable work layer for AI. Verifiable receipt for a workflow_close call on Zambo: {"count":3,"merkle_root":"784e80541ecd2372effaeb96e87e6d9870998683465b6cadc71ec6b12d2505e0","children":[{

Observed result

count: 3 merkle root: 784e80541ecd2372effaeb96e87e6d9870998683465b6cadc71ec6b12d2505e0 children 1 / id: abe8253b-3fee-4efc-b692-7427394b90b5 children 1 / output hash: 5d3b50526385bbee6109b71a9c19a5aa3e0d0f7a36b08557d1a44f5b902c3edc children 2 / id: a0a345f3-476e-47ff-9c7e-12ccc349e0bb children 2 / output hash: a878499e870460a29ebfbc770e7acbf36e703246183c9e572b1caa3028846ad5 children 3 / id: 3311d4f9-c4ec-42fc-a24a-cf9ceabae8f4 children 3 / output hash: 965cc69766657f3ff6245366be59858a363d55567942a231f1c615d63c02a77f message: Created a workflow snapshot containing 3 eligible receipts. To seal this, call workflow_seal with workflow_manage_token=Qq_fOJtSg78WIqX-pXqL2XQnJDsFB6kVLksc8_-xB3I. first closed at: 2026-10-16T08:22:06.119Z free view expires at: 2026-10-17T08:22:06.119Z page state: free disclosure: This workflow page is fully visible until 2026-10-17T08:22:06.119Z. 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
Show technical provenance details

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 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.

What the receipt can and cannot prove

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.

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 this receipt

Share on X ·

Show technical verification checks

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-16T08:22:06.567Z; 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

Show receipt data and verification evidence

Committed provenance claim

EXECUTED BY ZAMBO

The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.

Receipt ID
bfa06bae-9e29-4e09-8497-bff406f397b8
SHA-256 output hash
sha256:00e3c0e0cbabfa99c71123810dbf61e0985eb5162115c2f4262f52493a49f0e5
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NzE1MGIwZTk2ODcwM2NmOGQxNDZiMWU5NTJiNjNjZDg2MzcxYzJmOTJiMzM3ODIxZWIzYTk1OTZkM2JkZTIxZCIsImxhYmVsIjoib3duZXItZXhwb3J0LWF1ZGl0IiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7ImNoaWxkcmVuIjpbeyJpZCI6ImFiZTgyNTNiLTNmZWUtNGVmYy1iNjkyLTc0MjczOTRiOTBiNSIsIm91dHB1dF9oYXNoIjoiNWQzYjUwNTI2Mzg1YmJlZTYxMDliNzFhOWMxOWE1YWEzZTBkMGY3YTM2YjA4NTU3ZDFhNDRmNWI5MDJjM2VkYyJ9LHsiaWQiOiJhMGEzNDVmMy00NzZlLTQ3ZmYtOWM3ZS0xMmNjYzM0OWUwYmIiLCJvdXRwdXRfaGFzaCI6ImE4Nzg0OTllODcwNDYwYTI5ZWJmYmM3NzBlN2FjYmYzNmU3MDMyNDYxODNjOWU1NzJiMWNhYTMwMjg4NDZhZDUifSx7ImlkIjoiMzMxMWQ0ZjktYzRlYy00MmZjLWEyNGEtY2Y5Y2VhYmFlOGY0Iiwib3V0cHV0X2hhc2giOiI5NjVjYzY5NzY2NjU3ZjNmZjYyNDUzNjZiZTU5ODU4YTM2M2Q1NTU2Nzk0MmEyMzFmMWM2MTVkNjNjMDJhNzdmIn1dLCJjb3VudCI6MywiZGlzY2xvc3VyZSI6IlRoaXMgd29ya2Zsb3cgcGFnZSBpcyBmdWxseSB2aXNpYmxlIHVudGlsIDIwMjYtMTAtMTdUMDg6MjI6MDYuMTE5Wi4gU2VhbCBpdCB0byBrZWVwIGl0LCBhZGQgeW91ciBicmFuZGluZywgYW5kIGdldCB0aGUgUERGIHBhY2suIEluZGl2aWR1YWwgcmVjZWlwdHMgc3RheSBhdmFpbGFibGUgZWl0aGVyIHdheS4iLCJkaXNjbG9zdXJlX25vdGUiOiJFeHBpcnkgaXMgY3VycmVudGx5IGRpc2FibGVkLCBzbyBubyB3b3JrZmxvdyBwYWdlIGlzIGV4cGlyaW5nIHJpZ2h0IG5vdy4iLCJmaXJzdF9jbG9zZWRfYXQiOiIyMDI2LTEwLTE2VDA4OjIyOjA2LjExOVoiLCJmcmVlX3ZpZXdfZXhwaXJlc19hdCI6IjIwMjYtMTAtMTdUMDg6MjI6MDYuMTE5WiIsImlzc3Vlcl9hdXRoZW50aWNhdGVkIjpmYWxzZSwibWVya2xlX3Jvb3QiOiI3ODRlODA1NDFlY2QyMzcyZWZmYWViOTZlODdlNmQ5ODcwOTk4NjgzNDY1YjZjYWRjNzFlYzZiMTJkMjUwNWUwIiwibWVzc2FnZSI6IkNyZWF0ZWQgYSB3b3JrZmxvdyBzbmFwc2hvdCBjb250YWluaW5nIDMgZWxpZ2libGUgcmVjZWlwdHMuIFRvIHNlYWwgdGhpcywgY2FsbCB3b3JrZmxvd19zZWFsIHdpdGggd29ya2Zsb3dfbWFuYWdlX3Rva2VuPVFxX2ZPSnRTZzc4V0lxWC1wWHFMMlhRbkpEc0ZCNmtWTGtzYzhfLXhCM0kuIiwicGFnZV9zdGF0ZSI6ImZyZWUiLCJ2ZXJpZmljYXRpb25fc3RhdHVzIjoibm90X3ZlcmlmaWVkIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndvcmtmbG93X2Nsb3NlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
Timestamp

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:7150b0e968703cf8d146b1e952b63cd86371c2f92b337821eb3a9596d3bde21d
Caller-reported label
owner-export-audit (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
4bf0aebf8dd404e57ea305ef4838c380ccbd924b6d6e453ee95bc0dd770f0dfc
Anchor status
partial
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-16T08:22:06.567Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:00e3c0e0cbabfa99c71123810dbf61e0985eb5162115c2f4262f52493a49f0e5","receipt_uuid":"bfa06bae-9e29-4e09-8497-bff406f397b8","schema_version":"zambo-receipt-anchor/1"}

Anchor status "partial": Published to some configured relay targets; publication was not confirmed by every configured relay.

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/bfa06bae-9e29-4e09-8497-bff406f397b8/badge.svg)](https://zambo.dev/run/bfa06bae-9e29-4e09-8497-bff406f397b8?ref=badge)

HTML

<a href="https://zambo.dev/run/bfa06bae-9e29-4e09-8497-bff406f397b8?ref=badge"><img src="https://zambo.dev/api/receipt/bfa06bae-9e29-4e09-8497-bff406f397b8/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

44,609 verifiable receipts minted

RUN YOUR OWN FREE CALL →

Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.

Open the interactive receipt view