Write · saved and checkable
✓ This result hasn’t changed since it was saved.
Sent by zambo-home-demo using Zambo
Saved:
What was asked: The request recorded for this receipt.
Zambo is the verifiable work layer for AI.
Observed result
Subject: Zambo is live Hi [Name], You don’t need another AI tool that promises the moon and delivers static text. Zambo is live, and it works differently. We didn’t build a chatbot. We built an execution engine. Zambo scans your environment, identifies specific opportunities, and executes the next step without waiting for you to copy-paste prompts. It handles the research, the outreach logic, and the verification. You just approve the result. Right now, we are running quiet. We aren’t flooding your inbox with hype. We are letting the receipts speak. Every action Zambo takes generates a verifiable receipt. If it works, you see the proof. If it doesn’t, you see exactly where it stopped. No black boxes. No "trust us." We are opening access to a small group of early users who want to see how far an autonomous agent can go before it needs a human hand. **Here is your move:** 1. Click this link: [Insert Link] 2. Run your first scan. 3. Review the receipt. If the output matches your workflow, keep going. If it doesn’t, you lose nothing but two minutes of time. We are not asking for a subscription yet. We are asking for your eyes on the data. Let’s see what Zambo finds for you. Best, [Your Name] [Your Title] Zambo
This is the saved result preview, not proof that the answer was correct.
Check this receipt
This page shows the result and when it was saved. Use the receipt checker to see whether the saved result has changed.
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.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
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-21T20:36:36.377Z; external immutability is not checked
Get proof like this from your own 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
7bd98f8d-a061-499d-9a8b-18cb2497d5c5- SHA-256 output hash
sha256:8fe047a7caec08b3750d9214e1ec953a2ebb6912b529be3668b304da2168d7dc- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OTQ2ZWVkYTNhMDg2ZWM1YmU2NTc4MzMyYTY3ZDdhMjY0ZmQ4MmMxZjIwYjRiOGZkNTliOGI3ODgzNmE2YTUwOCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlXG5cbkhpIFtOYW1lXSxcblxuWW91IGRvbuKAmXQgbmVlZCBhbm90aGVyIEFJIHRvb2wgdGhhdCBwcm9taXNlcyB0aGUgbW9vbiBhbmQgZGVsaXZlcnMgc3RhdGljIHRleHQuIFphbWJvIGlzIGxpdmUsIGFuZCBpdCB3b3JrcyBkaWZmZXJlbnRseS5cblxuV2UgZGlkbuKAmXQgYnVpbGQgYSBjaGF0Ym90LiBXZSBidWlsdCBhbiBleGVjdXRpb24gZW5naW5lLiBaYW1ibyBzY2FucyB5b3VyIGVudmlyb25tZW50LCBpZGVudGlmaWVzIHNwZWNpZmljIG9wcG9ydHVuaXRpZXMsIGFuZCBleGVjdXRlcyB0aGUgbmV4dCBzdGVwIHdpdGhvdXQgd2FpdGluZyBmb3IgeW91IHRvIGNvcHktcGFzdGUgcHJvbXB0cy4gSXQgaGFuZGxlcyB0aGUgcmVzZWFyY2gsIHRoZSBvdXRyZWFjaCBsb2dpYywgYW5kIHRoZSB2ZXJpZmljYXRpb24uIFlvdSBqdXN0IGFwcHJvdmUgdGhlIHJlc3VsdC5cblxuUmlnaHQgbm93LCB3ZSBhcmUgcnVubmluZyBxdWlldC4gV2UgYXJlbuKAmXQgZmxvb2RpbmcgeW91ciBpbmJveCB3aXRoIGh5cGUuIFdlIGFyZSBsZXR0aW5nIHRoZSByZWNlaXB0cyBzcGVhay4gRXZlcnkgYWN0aW9uIFphbWJvIHRha2VzIGdlbmVyYXRlcyBhIHZlcmlmaWFibGUgcmVjZWlwdC4gSWYgaXQgd29ya3MsIHlvdSBzZWUgdGhlIHByb29mLiBJZiBpdCBkb2VzbuKAmXQsIHlvdSBzZWUgZXhhY3RseSB3aGVyZSBpdCBzdG9wcGVkLiBObyBibGFjayBib3hlcy4gTm8gXCJ0cnVzdCB1cy5cIlxuXG5XZSBhcmUgb3BlbmluZyBhY2Nlc3MgdG8gYSBzbWFsbCBncm91cCBvZiBlYXJseSB1c2VycyB3aG8gd2FudCB0byBzZWUgaG93IGZhciBhbiBhdXRvbm9tb3VzIGFnZW50IGNhbiBnbyBiZWZvcmUgaXQgbmVlZHMgYSBodW1hbiBoYW5kLlxuXG4qKkhlcmUgaXMgeW91ciBtb3ZlOioqXG5cbjEuICBDbGljayB0aGlzIGxpbms6IFtJbnNlcnQgTGlua11cbjIuICBSdW4geW91ciBmaXJzdCBzY2FuLlxuMy4gIFJldmlldyB0aGUgcmVjZWlwdC5cblxuSWYgdGhlIG91dHB1dCBtYXRjaGVzIHlvdXIgd29ya2Zsb3csIGtlZXAgZ29pbmcuIElmIGl0IGRvZXNu4oCZdCwgeW91IGxvc2Ugbm90aGluZyBidXQgdHdvIG1pbnV0ZXMgb2YgdGltZS5cblxuV2UgYXJlIG5vdCBhc2tpbmcgZm9yIGEgc3Vic2NyaXB0aW9uIHlldC4gV2UgYXJlIGFza2luZyBmb3IgeW91ciBleWVzIG9uIHRoZSBkYXRhLlxuXG5MZXTigJlzIHNlZSB3aGF0IFphbWJvIGZpbmRzIGZvciB5b3UuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5bWW91ciBUaXRsZV1cblphbWJvIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=- Timestamp
Bound call context
- Receipt schema
0.4- Tool name
write- Tool version
4.0.0- Permission scope
public- Caller type
session- Caller ID
sha256:946eeda3a086ec5be6578332a67d7a264fd82c1f20b4b8fd59b8b78836a6a508- 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
- no_upstream_bytes_captured
- Evidence SHA-256
unavailable- Byte length
- unavailable
Neutral Nostr anchor
- Event ID
886716052364557d48a37d8b2f8858c2b8a22e77ea3e77870ec75e68ffcaede4- 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-21T20:36:36.377Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:8fe047a7caec08b3750d9214e1ec953a2ebb6912b529be3668b304da2168d7dc","receipt_uuid":"7bd98f8d-a061-499d-9a8b-18cb2497d5c5","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
[](https://zambo.dev/run/7bd98f8d-a061-499d-9a8b-18cb2497d5c5?ref=badge)
HTML
<a href="https://zambo.dev/run/7bd98f8d-a061-499d-9a8b-18cb2497d5c5?ref=badge"><img src="https://zambo.dev/api/receipt/7bd98f8d-a061-499d-9a8b-18cb2497d5c5/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
57,455 verifiable receipts minted
Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.