Verifiable receipt 71d734ac - 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":8,"merkle_root":"e2f2c1d6f1963e85340df0ec465e0dee39e7689b4dbbffeaa8a1c10c5916569b","children":[{

Observed result

count: 8 merkle root: e2f2c1d6f1963e85340df0ec465e0dee39e7689b4dbbffeaa8a1c10c5916569b children 1 / id: 88675c18-d152-4173-a09c-234de1b1acbd children 1 / output hash: 628e74402d6273857c49e26135983a20b7ef99427ae1adb1079e87bbe836c3bd children 2 / id: f310fbb9-7e86-4b0b-896e-ca023f95fe83 children 2 / output hash: 5db48cd472dc92bea3c0c34b3c1b844644ca6042e5f9d90a7d0d3b3a66829189 children 3 / id: 92c458b9-3332-4dda-8e8c-4f66e081ad7f children 3 / output hash: 3ef61d986fc89e2438c59e31b91ffacd232e65de7d7502032bc850abe5df6d93 children 4 / id: 60aa2f25-da12-4645-a37a-c55a5f951c2b children 4 / output hash: dba9324751ef62fb1954da0985b253794c4f0dc4f8bc86c7a58751d6dff42a12 children 5 / id: f4c04bba-33d8-4e9b-8613-6d7f6187c726 children 5 / output hash: 1dd24ff3d22cd493cc2e5dff5840f6b627afd5d9c967759fb1574ac0bba7e40e children 6 / id: 05cdbc93-4a76-45e9-bb0c-983d63ca0486 children 6 / output hash: 47e2d9babf720dfdf81f56f0176b8570b5cfe1e5cdcb1cf22a68055c5e01c324 children 7 / id: cec273ee-ec91-4d06-817a-c7a0478223cc children 7 / output hash: 5a71b96a2a32e8b94f0cb886b9e353b50f865b625817953cdc1b9391cad6b40c children 8 / id: c13f11fc-ef64-43d0-b22d-c811639ac881 children 8 / output hash: d9d3b57e3dcccc26f35a9ce4396e5e989d2f45a4e70e2b135fa4db5a9ad8d0f6

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-20T02:28:52.618Z; external immutability is not checked

Get proof like this from your own AI

Add to my AI ·

Get receipts for your own AI work: add zambo.dev/mcp

One URL, no key. Copy the line for your AI and add it yourself in its settings.

  • ClaudeSettings, Connectors, Add custom connector, paste the URL.
    https://zambo.dev/mcp
  • ChatGPTSettings, Apps and Connectors, developer mode, create a connector with this URL.
    https://zambo.dev/mcp
  • GrokAdd a remote MCP server in your Grok client and paste the URL.
    https://zambo.dev/mcp
  • CursorPaste into ~/.cursor/mcp.json.
    {"mcpServers":{"zambo":{"url":"https://zambo.dev/mcp"}}}

Nothing is installed automatically. Full setup guides

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
71d734ac-1765-4ec1-99c6-5a10448e7374
SHA-256 output hash
sha256:ae4ba1347527b8b396f968529e52f997d2a0797c3b729f31d5212554fed1a325
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZGIxNmU0NzlkYjVlZmQ5MTcyYWIwYTI2NTU4MWYwYTk1MGQ5NmI2YTI5ZDM5NTFmODcwNGYxODVmY2JkNjY4ZCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJjaGlsZHJlbiI6W3siaWQiOiI4ODY3NWMxOC1kMTUyLTQxNzMtYTA5Yy0yMzRkZTFiMWFjYmQiLCJvdXRwdXRfaGFzaCI6IjYyOGU3NDQwMmQ2MjczODU3YzQ5ZTI2MTM1OTgzYTIwYjdlZjk5NDI3YWUxYWRiMTA3OWU4N2JiZTgzNmMzYmQifSx7ImlkIjoiZjMxMGZiYjktN2U4Ni00YjBiLTg5NmUtY2EwMjNmOTVmZTgzIiwib3V0cHV0X2hhc2giOiI1ZGI0OGNkNDcyZGM5MmJlYTNjMGMzNGIzYzFiODQ0NjQ0Y2E2MDQyZTVmOWQ5MGE3ZDBkM2IzYTY2ODI5MTg5In0seyJpZCI6IjkyYzQ1OGI5LTMzMzItNGRkYS04ZThjLTRmNjZlMDgxYWQ3ZiIsIm91dHB1dF9oYXNoIjoiM2VmNjFkOTg2ZmM4OWUyNDM4YzU5ZTMxYjkxZmZhY2QyMzJlNjVkZTdkNzUwMjAzMmJjODUwYWJlNWRmNmQ5MyJ9LHsiaWQiOiI2MGFhMmYyNS1kYTEyLTQ2NDUtYTM3YS1jNTVhNWY5NTFjMmIiLCJvdXRwdXRfaGFzaCI6ImRiYTkzMjQ3NTFlZjYyZmIxOTU0ZGEwOTg1YjI1Mzc5NGM0ZjBkYzRmOGJjODZjN2E1ODc1MWQ2ZGZmNDJhMTIifSx7ImlkIjoiZjRjMDRiYmEtMzNkOC00ZTliLTg2MTMtNmQ3ZjYxODdjNzI2Iiwib3V0cHV0X2hhc2giOiIxZGQyNGZmM2QyMmNkNDkzY2MyZTVkZmY1ODQwZjZiNjI3YWZkNWQ5Yzk2Nzc1OWZiMTU3NGFjMGJiYTdlNDBlIn0seyJpZCI6IjA1Y2RiYzkzLTRhNzYtNDVlOS1iYjBjLTk4M2Q2M2NhMDQ4NiIsIm91dHB1dF9oYXNoIjoiNDdlMmQ5YmFiZjcyMGRmZGY4MWY1NmYwMTc2Yjg1NzBiNWNmZTFlNWNkY2IxY2YyMmE2ODA1NWM1ZTAxYzMyNCJ9LHsiaWQiOiJjZWMyNzNlZS1lYzkxLTRkMDYtODE3YS1jN2EwNDc4MjIzY2MiLCJvdXRwdXRfaGFzaCI6IjVhNzFiOTZhMmEzMmU4Yjk0ZjBjYjg4NmI5ZTM1M2I1MGY4NjViNjI1ODE3OTUzY2RjMWI5MzkxY2FkNmI0MGMifSx7ImlkIjoiYzEzZjExZmMtZWY2NC00M2QwLWIyMmQtYzgxMTYzOWFjODgxIiwib3V0cHV0X2hhc2giOiJkOWQzYjU3ZTNkY2NjYzI2ZjM1YTljZTQzOTZlNWU5ODlkMmY0NWE0ZTcwZTJiMTM1ZmE0ZGI1YTlhZDhkMGY2In1dLCJjb3VudCI6OCwibWVya2xlX3Jvb3QiOiJlMmYyYzFkNmYxOTYzZTg1MzQwZGYwZWM0NjVlMGRlZTM5ZTc2ODliNGRiYmZmZWFhOGExYzEwYzU5MTY1NjliIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndvcmtmbG93X2Nsb3NlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:db16e479db5efd9172ab0a265581f0a950d96b6a29d3951f8704f185fcbd668d
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
5b831de32dc9a185feb2898a06cb809ec7e0b6db18dbbced85768472ae160670
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-20T02:28:52.618Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:ae4ba1347527b8b396f968529e52f997d2a0797c3b729f31d5212554fed1a325","receipt_uuid":"71d734ac-1765-4ec1-99c6-5a10448e7374","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

Check this hash yourself

Receipt commitment: commitment matched; issuer, signature and chain not checked. This checks the saved bytes, not whether 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/71d734ac-1765-4ec1-99c6-5a10448e7374/badge.svg)](https://zambo.dev/run/71d734ac-1765-4ec1-99c6-5a10448e7374?ref=badge)

HTML

<a href="https://zambo.dev/run/71d734ac-1765-4ec1-99c6-5a10448e7374?ref=badge"><img src="https://zambo.dev/api/receipt/71d734ac-1765-4ec1-99c6-5a10448e7374/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

53,229 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