Public work receipt · checkable record

Write · saved and checkable

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

Sent by zambo-home-demo using Zambo

Saved:
What ran: write

Zambo is the verifiable work layer for AI.

Observed result

**Subject: Zambo is live** Hi [Name], You’ve probably seen the noise about AI tools promising to save your team hours. Most deliver complex dashboards that take weeks to master. Zambo is different. It’s built for speed and clarity, designed to get you from idea to execution without the learning curve. We’ve spent the last few months refining the core experience. The goal was simple: remove friction. If you’re ready to test-drive a tool that respects your time, the doors are open. **Try it here: [Link]** No credit card required. No setup calls. Just log in and see how it works for your specific workflow. We want your honest feedback on whether it actually saves you time, not just whether it looks impressive. If it clicks, let us know. If it doesn’t, tell us why. Either way, we’re listening. Best, [Your Name] [Your Title] Zambo

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-20T02:49:14.750Z; 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
8e684bde-2b9f-49be-bd7f-f981a43de8e3
SHA-256 output hash
sha256:99392bff55cdfd8d416c5ab96bdc2e301ed7ccf227a2f85363a14092b3756952
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NWEzYWM2OGU2ZDE0MjM0YjdiODllZjJmZTlkMGFiMTFkM2ZmOWNjODEzZDBjZDc5MmNmNTJmNWUyMTQ2N2EwMCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiIqKlN1YmplY3Q6IFphbWJvIGlzIGxpdmUqKlxuXG5IaSBbTmFtZV0sXG5cbllvdeKAmXZlIHByb2JhYmx5IHNlZW4gdGhlIG5vaXNlIGFib3V0IEFJIHRvb2xzIHByb21pc2luZyB0byBzYXZlIHlvdXIgdGVhbSBob3Vycy4gTW9zdCBkZWxpdmVyIGNvbXBsZXggZGFzaGJvYXJkcyB0aGF0IHRha2Ugd2Vla3MgdG8gbWFzdGVyLiBaYW1ibyBpcyBkaWZmZXJlbnQuIEl04oCZcyBidWlsdCBmb3Igc3BlZWQgYW5kIGNsYXJpdHksIGRlc2lnbmVkIHRvIGdldCB5b3UgZnJvbSBpZGVhIHRvIGV4ZWN1dGlvbiB3aXRob3V0IHRoZSBsZWFybmluZyBjdXJ2ZS5cblxuV2XigJl2ZSBzcGVudCB0aGUgbGFzdCBmZXcgbW9udGhzIHJlZmluaW5nIHRoZSBjb3JlIGV4cGVyaWVuY2UuIFRoZSBnb2FsIHdhcyBzaW1wbGU6IHJlbW92ZSBmcmljdGlvbi4gSWYgeW914oCZcmUgcmVhZHkgdG8gdGVzdC1kcml2ZSBhIHRvb2wgdGhhdCByZXNwZWN0cyB5b3VyIHRpbWUsIHRoZSBkb29ycyBhcmUgb3Blbi5cblxuKipUcnkgaXQgaGVyZTogW0xpbmtdKipcblxuTm8gY3JlZGl0IGNhcmQgcmVxdWlyZWQuIE5vIHNldHVwIGNhbGxzLiBKdXN0IGxvZyBpbiBhbmQgc2VlIGhvdyBpdCB3b3JrcyBmb3IgeW91ciBzcGVjaWZpYyB3b3JrZmxvdy4gV2Ugd2FudCB5b3VyIGhvbmVzdCBmZWVkYmFjayBvbiB3aGV0aGVyIGl0IGFjdHVhbGx5IHNhdmVzIHlvdSB0aW1lLCBub3QganVzdCB3aGV0aGVyIGl0IGxvb2tzIGltcHJlc3NpdmUuXG5cbklmIGl0IGNsaWNrcywgbGV0IHVzIGtub3cuIElmIGl0IGRvZXNu4oCZdCwgdGVsbCB1cyB3aHkuIEVpdGhlciB3YXksIHdl4oCZcmUgbGlzdGVuaW5nLlxuXG5CZXN0LFxuXG5bWW91ciBOYW1lXVxuW1lvdXIgVGl0bGVdXG5aYW1ibyJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS40In19
Timestamp

Bound call context

Receipt schema
0.4
Tool name
write
Tool version
4.1.4
Permission scope
public
Caller type
session
Caller ID
sha256:5a3ac68e6d14234b7b89ef2fe9d0ab11d3ff9cc813d0cd792cf52f5e21467a00
Caller-reported label
zambo-home-demo (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
empty
Evidence SHA-256
unavailable
Byte length
unavailable

Upstream provenance

This receipt is independently auditable against the named upstream source. This is not a mathematical correctness claim.

  • Source: · queried at: · raw response hash:

Neutral Nostr anchor

Event ID
cac27c91d0b80b325bef8c07bae1a96d9d231526da80d940a2bfcff101689a5e
Anchor status
published
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-20T02:49:14.750Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:99392bff55cdfd8d416c5ab96bdc2e301ed7ccf227a2f85363a14092b3756952","receipt_uuid":"8e684bde-2b9f-49be-bd7f-f981a43de8e3","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/8e684bde-2b9f-49be-bd7f-f981a43de8e3/badge.svg)](https://zambo.dev/run/8e684bde-2b9f-49be-bd7f-f981a43de8e3?ref=badge)

HTML

<a href="https://zambo.dev/run/8e684bde-2b9f-49be-bd7f-f981a43de8e3?ref=badge"><img src="https://zambo.dev/api/receipt/8e684bde-2b9f-49be-bd7f-f981a43de8e3/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

151,425 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.