Public work receipt · checkable record

Workflow close · saved and checkable

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

Sent using Zambo

Saved:
What ran: workflow_close

Zambo is the verifiable work layer for AI.

Observed result

count: 5 merkle root: d4fe9d221f4c4b1063e464274986af0bdb127abc2be8e47efac99b8549b2b33d merkle version: seq-output-v1 children 1 / id: 75ab30a0-37d5-4eb6-b5e9-5debde0ec657 children 1 / output hash: 563cb7f9dbdfcc4e21f7240833bc9d33bc8be55aeacaad46257de0807182015a children 2 / id: 7ad7e098-7493-4c7e-a0df-b118de5cf756 children 2 / output hash: d6909090a888474b2feb5318366d6bb70347229daaa0432ff27f09fbbb63b7c2 children 3 / id: 9167ad4f-d45c-431a-8ee7-2baaf4dcacf4 children 3 / output hash: 2669885601baf11644263c16b445f31a8f9b6b07166dd2c61072690622d4860f children 4 / id: 4d7689f5-946e-4a55-af24-5e68264fc58d children 4 / output hash: eda61c56852ee8abaeb8e7d592fc50d2bd4e0bdcce3a413794aacf68d939034a children 5 / id: f7831e64-766f-481c-bfee-5df1da7947d1 children 5 / output hash: 40d13d53ef51ef714783ce6801b5c7de7ef15bedc4a8380084cae24263ae9bb1 handover id: 6d6adf30-b59a-47f0-88b8-1c53d1b5dbd1 steps digest: fc3dac50e80b01a6bb50ae910a14367b71b7ae35578df143c9c6ceafd3e9f9fb graph sha256: 52e15bd66b46f79c6f61127b9631f72df4abb5dccdedf48c9c30cc292ba179fe verification status: not_verified issuer authenticated: false

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

Verify saved bytes 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 · Share on LinkedIn ·

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-11-20T10:38:54.970Z; 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
cae2fe91-b6e0-4b87-9b31-68a1ca2b01ff
SHA-256 output hash
sha256:47aaad9b79ce3e9b468507d85557885d9630be746610323e55ef27bc62dc1af0
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MjUyODQ4MDZjN2IwNDE3NjRlNzg5NmM5Mjg5M2VkZTJhMWQwNTEwM2U2ZmNlOGI0NjczZTRjOGIyMGFmZmY3YiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJjaGlsZHJlbiI6W3siaWQiOiI3NWFiMzBhMC0zN2Q1LTRlYjYtYjVlOS01ZGViZGUwZWM2NTciLCJvdXRwdXRfaGFzaCI6IjU2M2NiN2Y5ZGJkZmNjNGUyMWY3MjQwODMzYmM5ZDMzYmM4YmU1NWFlYWNhYWQ0NjI1N2RlMDgwNzE4MjAxNWEifSx7ImlkIjoiN2FkN2UwOTgtNzQ5My00YzdlLWEwZGYtYjExOGRlNWNmNzU2Iiwib3V0cHV0X2hhc2giOiJkNjkwOTA5MGE4ODg0NzRiMmZlYjUzMTgzNjZkNmJiNzAzNDcyMjlkYWFhMDQzMmZmMjdmMDlmYmJiNjNiN2MyIn0seyJpZCI6IjkxNjdhZDRmLWQ0NWMtNDMxYS04ZWU3LTJiYWFmNGRjYWNmNCIsIm91dHB1dF9oYXNoIjoiMjY2OTg4NTYwMWJhZjExNjQ0MjYzYzE2YjQ0NWYzMWE4ZjliNmIwNzE2NmRkMmM2MTA3MjY5MDYyMmQ0ODYwZiJ9LHsiaWQiOiI0ZDc2ODlmNS05NDZlLTRhNTUtYWYyNC01ZTY4MjY0ZmM1OGQiLCJvdXRwdXRfaGFzaCI6ImVkYTYxYzU2ODUyZWU4YWJhZWI4ZTdkNTkyZmM1MGQyYmQ0ZTBiZGNjZTNhNDEzNzk0YWFjZjY4ZDkzOTAzNGEifSx7ImlkIjoiZjc4MzFlNjQtNzY2Zi00ODFjLWJmZWUtNWRmMWRhNzk0N2QxIiwib3V0cHV0X2hhc2giOiI0MGQxM2Q1M2VmNTFlZjcxNDc4M2NlNjgwMWI1YzdkZTdlZjE1YmVkYzRhODM4MDA4NGNhZTI0MjYzYWU5YmIxIn1dLCJjb3VudCI6NSwiZGVsaXZlcmFibGVzIjpbXSwiZ3JhcGhfc2hhMjU2IjoiNTJlMTViZDY2YjQ2Zjc5YzZmNjExMjdiOTYzMWY3MmRmNGFiYjVkY2NkZWRmNDhjOWMzMGNjMjkyYmExNzlmZSIsImhhbmRvdmVyX2lkIjoiNmQ2YWRmMzAtYjU5YS00N2YwLTg4YjgtMWM1M2QxYjVkYmQxIiwiaXNzdWVyX2F1dGhlbnRpY2F0ZWQiOmZhbHNlLCJtZXJrbGVfcm9vdCI6ImQ0ZmU5ZDIyMWY0YzRiMTA2M2U0NjQyNzQ5ODZhZjBiZGIxMjdhYmMyYmU4ZTQ3ZWZhYzk5Yjg1NDliMmIzM2QiLCJtZXJrbGVfdmVyc2lvbiI6InNlcS1vdXRwdXQtdjEiLCJuZWdhdGl2ZV9yZWNvcmQiOnsibm90X2NoZWNrZWQiOltdLCJub3RfcnVuIjpbXX0sInN0ZXBzX2RpZ2VzdCI6ImZjM2RhYzUwZTgwYjAxYTZiYjUwYWU5MTBhMTQzNjdiNzFiN2FlMzU1NzhkZjE0M2M5YzZjZWFmZDNlOWY5ZmIiLCJ2ZXJpZmljYXRpb25fc3RhdHVzIjoibm90X3ZlcmlmaWVkIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3b3JrZmxvd19jbG9zZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS40In19
Timestamp

Bound call context

Receipt schema
0.4
Tool name
workflow_close
Tool version
4.1.4
Permission scope
public
Caller type
session
Caller ID
sha256:25284806c7b041764e7896c92893ede2a1d05103e6fce8b4673e4c8b20afff7b
Declared side effects
state_write
Side-effects schema
zambo-side-effects/1
Declaration hash
sha256:dfb4412aa429d3ac637a05668c435bcc90a251363fcdd49f7b85ae4ab55b5bc9

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
empty
Evidence SHA-256
unavailable
Byte length
unavailable

Neutral Nostr anchor

Event ID
ea7279f88754099d94bfbc7dcf581762db6c72effa423c03fe234def309a1684
Anchor status
published
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-20T10:38:54.970Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:47aaad9b79ce3e9b468507d85557885d9630be746610323e55ef27bc62dc1af0","receipt_uuid":"cae2fe91-b6e0-4b87-9b31-68a1ca2b01ff","schema_version":"zambo-receipt-anchor/1"}

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

Relay publication is separate from receipt integrity. When the original signed event is available, Zambo retries pending, partial, or failed anchors about once a minute. Relay acknowledgements are external, so there is no guaranteed completion time; the receipt remains checkable from its saved bytes and verification link.

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. Open the browser receipt checker. 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/cae2fe91-b6e0-4b87-9b31-68a1ca2b01ff/badge.svg)](https://zambo.dev/run/cae2fe91-b6e0-4b87-9b31-68a1ca2b01ff?ref=badge)

HTML

<a href="https://zambo.dev/run/cae2fe91-b6e0-4b87-9b31-68a1ca2b01ff?ref=badge"><img src="https://zambo.dev/api/receipt/cae2fe91-b6e0-4b87-9b31-68a1ca2b01ff/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

152,825 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

Your AI's work could look like this

Run a first job free in Zambo Chat. No account needed.