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], Zambo is officially up and running. We built Zambo to handle the heavy lifting of AI research and verification so you can focus on strategy, not troubleshooting. It’s a workspace that connects your tools and verifies your outputs, ensuring that when you say something is done, the data backs it up. Right now, the platform is live and ready for you to explore. You can start by looking at the **Substrate Breakthroughs** feed, which offers a read-only view of current AI research insights. It’s a clean, low-commitment way to see how Zambo processes and presents information without needing to configure complex workflows first. We also have **VeriAI** integrated for cryptographic trust scoring, though that currently requires a quick manual step in the web flow. For immediate hands-on experience, the Substrate tool is your best entry point. If you want to test the drive home, there’s a live dashboard available today. You can check your specific activity log to see exactly what the system captured during your session. The goal is transparency: you see the receipt, you see the data, and you know exactly what happened. No setup fees. No hidden data requests. Just a clean interface for getting work done. **Next Step:** Go to [Insert Link to Zambo Dashboard] and run your first query using the Substrate tool. It’s free to test and takes under a minute. Let me know if the interface loads correctly on your end. 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-22T04:47:46.273Z; 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
bed61ad5-ccbe-4cb4-b565-861ec0ba69ae- SHA-256 output hash
sha256:4f6581905861bbbb3edea85c03ae3004434421dc1b3122629df8583e3e4ed89e- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6N2E5Yjk0N2ZjYjc3YmJkMjJhOTkwODU5MWQ0ZTQ2OTM4YzUwMDZkNjY5NzY0YTBiZjE2NTQxOTMzYzg0YmE4YyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiIqKlN1YmplY3Q6IFphbWJvIGlzIGxpdmUqKlxuXG5IaSBbTmFtZV0sXG5cblphbWJvIGlzIG9mZmljaWFsbHkgdXAgYW5kIHJ1bm5pbmcuXG5cbldlIGJ1aWx0IFphbWJvIHRvIGhhbmRsZSB0aGUgaGVhdnkgbGlmdGluZyBvZiBBSSByZXNlYXJjaCBhbmQgdmVyaWZpY2F0aW9uIHNvIHlvdSBjYW4gZm9jdXMgb24gc3RyYXRlZ3ksIG5vdCB0cm91Ymxlc2hvb3RpbmcuIEl04oCZcyBhIHdvcmtzcGFjZSB0aGF0IGNvbm5lY3RzIHlvdXIgdG9vbHMgYW5kIHZlcmlmaWVzIHlvdXIgb3V0cHV0cywgZW5zdXJpbmcgdGhhdCB3aGVuIHlvdSBzYXkgc29tZXRoaW5nIGlzIGRvbmUsIHRoZSBkYXRhIGJhY2tzIGl0IHVwLlxuXG5SaWdodCBub3csIHRoZSBwbGF0Zm9ybSBpcyBsaXZlIGFuZCByZWFkeSBmb3IgeW91IHRvIGV4cGxvcmUuIFlvdSBjYW4gc3RhcnQgYnkgbG9va2luZyBhdCB0aGUgKipTdWJzdHJhdGUgQnJlYWt0aHJvdWdocyoqIGZlZWQsIHdoaWNoIG9mZmVycyBhIHJlYWQtb25seSB2aWV3IG9mIGN1cnJlbnQgQUkgcmVzZWFyY2ggaW5zaWdodHMuIEl04oCZcyBhIGNsZWFuLCBsb3ctY29tbWl0bWVudCB3YXkgdG8gc2VlIGhvdyBaYW1ibyBwcm9jZXNzZXMgYW5kIHByZXNlbnRzIGluZm9ybWF0aW9uIHdpdGhvdXQgbmVlZGluZyB0byBjb25maWd1cmUgY29tcGxleCB3b3JrZmxvd3MgZmlyc3QuXG5cbldlIGFsc28gaGF2ZSAqKlZlcmlBSSoqIGludGVncmF0ZWQgZm9yIGNyeXB0b2dyYXBoaWMgdHJ1c3Qgc2NvcmluZywgdGhvdWdoIHRoYXQgY3VycmVudGx5IHJlcXVpcmVzIGEgcXVpY2sgbWFudWFsIHN0ZXAgaW4gdGhlIHdlYiBmbG93LiBGb3IgaW1tZWRpYXRlIGhhbmRzLW9uIGV4cGVyaWVuY2UsIHRoZSBTdWJzdHJhdGUgdG9vbCBpcyB5b3VyIGJlc3QgZW50cnkgcG9pbnQuXG5cbklmIHlvdSB3YW50IHRvIHRlc3QgdGhlIGRyaXZlIGhvbWUsIHRoZXJl4oCZcyBhIGxpdmUgZGFzaGJvYXJkIGF2YWlsYWJsZSB0b2RheS4gWW91IGNhbiBjaGVjayB5b3VyIHNwZWNpZmljIGFjdGl2aXR5IGxvZyB0byBzZWUgZXhhY3RseSB3aGF0IHRoZSBzeXN0ZW0gY2FwdHVyZWQgZHVyaW5nIHlvdXIgc2Vzc2lvbi4gVGhlIGdvYWwgaXMgdHJhbnNwYXJlbmN5OiB5b3Ugc2VlIHRoZSByZWNlaXB0LCB5b3Ugc2VlIHRoZSBkYXRhLCBhbmQgeW91IGtub3cgZXhhY3RseSB3aGF0IGhhcHBlbmVkLlxuXG5ObyBzZXR1cCBmZWVzLiBObyBoaWRkZW4gZGF0YSByZXF1ZXN0cy4gSnVzdCBhIGNsZWFuIGludGVyZmFjZSBmb3IgZ2V0dGluZyB3b3JrIGRvbmUuXG5cbioqTmV4dCBTdGVwOioqXG5cbkdvIHRvIFtJbnNlcnQgTGluayB0byBaYW1ibyBEYXNoYm9hcmRdIGFuZCBydW4geW91ciBmaXJzdCBxdWVyeSB1c2luZyB0aGUgU3Vic3RyYXRlIHRvb2wuIEl04oCZcyBmcmVlIHRvIHRlc3QgYW5kIHRha2VzIHVuZGVyIGEgbWludXRlLiBMZXQgbWUga25vdyBpZiB0aGUgaW50ZXJmYWNlIGxvYWRzIGNvcnJlY3RseSBvbiB5b3VyIGVuZC5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cbltZb3VyIFRpdGxlXVxuWmFtYm8ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==- 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:7a9b947fcb77bbd22a9908591d4e46938c5006d669764a0bf16541933c84ba8c- 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
cb87536976fcb5d6742fae53d9820136021b260f568fc3099d7318dcdc37a03a- 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-22T04:47:46.273Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:4f6581905861bbbb3edea85c03ae3004434421dc1b3122629df8583e3e4ed89e","receipt_uuid":"bed61ad5-ccbe-4cb4-b565-861ec0ba69ae","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
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/bed61ad5-ccbe-4cb4-b565-861ec0ba69ae?ref=badge)
HTML
<a href="https://zambo.dev/run/bed61ad5-ccbe-4cb4-b565-861ec0ba69ae?ref=badge"><img src="https://zambo.dev/api/receipt/bed61ad5-ccbe-4cb4-b565-861ec0ba69ae/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
58,188 verifiable receipts minted
Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.