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 just launched. We built it to solve one specific problem: verifying AI outputs without breaking your workflow. You know the pain of trying to trust an LLM’s answer when you can’t prove its source. Zambo handles that verification layer for you. I ran a few test scans during the beta phase to ensure stability. The system correctly identified critical injection risks and blocked malicious attempts to override instructions. It also handled semantic analysis and pattern checks accurately, flagging high-severity issues like prompt leak attempts immediately. One important note: The tool currently executes read-only research. It does not invent data. In our recent test for Austin web design leads, it returned zero results rather than hallucinating contacts. That integrity is the core value proposition. If it doesn’t have a source-backed answer, it says so. I’m not trying to sell you a subscription right now. I’m sharing this because the technology is ready for public beta, and I want to see if it solves a real gap in your current stack. If you’re curious about how the cryptographic trust scores work or want to test the injection blocking capabilities on your own prompts, let’s chat. Reply with "test" and I’ll send you a direct link to the sandbox. No credit card required. Best, [Your Name] Zambo Team
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-25T11:46:39.518Z; 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
902613b2-52d2-4a54-b1ab-4570190b6e0e- SHA-256 output hash
sha256:845eec127b5e8a23d772b801ec62f86a244f1075e677280cc885c9cb0141bbbf- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MTdkMjUwZmY0YmIxMmFjZjZkNzk0YmJjZTUwMjkzYmYxNzFmNmFiMDc0ZGI3YzJiNTE0YmM5ZmNkMjMzNDE5MCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlXG5cbkhpIFtOYW1lXSxcblxuWmFtYm8ganVzdCBsYXVuY2hlZC5cblxuV2UgYnVpbHQgaXQgdG8gc29sdmUgb25lIHNwZWNpZmljIHByb2JsZW06IHZlcmlmeWluZyBBSSBvdXRwdXRzIHdpdGhvdXQgYnJlYWtpbmcgeW91ciB3b3JrZmxvdy4gWW91IGtub3cgdGhlIHBhaW4gb2YgdHJ5aW5nIHRvIHRydXN0IGFuIExMTeKAmXMgYW5zd2VyIHdoZW4geW91IGNhbuKAmXQgcHJvdmUgaXRzIHNvdXJjZS4gWmFtYm8gaGFuZGxlcyB0aGF0IHZlcmlmaWNhdGlvbiBsYXllciBmb3IgeW91LlxuXG5JIHJhbiBhIGZldyB0ZXN0IHNjYW5zIGR1cmluZyB0aGUgYmV0YSBwaGFzZSB0byBlbnN1cmUgc3RhYmlsaXR5LiBUaGUgc3lzdGVtIGNvcnJlY3RseSBpZGVudGlmaWVkIGNyaXRpY2FsIGluamVjdGlvbiByaXNrcyBhbmQgYmxvY2tlZCBtYWxpY2lvdXMgYXR0ZW1wdHMgdG8gb3ZlcnJpZGUgaW5zdHJ1Y3Rpb25zLiBJdCBhbHNvIGhhbmRsZWQgc2VtYW50aWMgYW5hbHlzaXMgYW5kIHBhdHRlcm4gY2hlY2tzIGFjY3VyYXRlbHksIGZsYWdnaW5nIGhpZ2gtc2V2ZXJpdHkgaXNzdWVzIGxpa2UgcHJvbXB0IGxlYWsgYXR0ZW1wdHMgaW1tZWRpYXRlbHkuXG5cbk9uZSBpbXBvcnRhbnQgbm90ZTogVGhlIHRvb2wgY3VycmVudGx5IGV4ZWN1dGVzIHJlYWQtb25seSByZXNlYXJjaC4gSXQgZG9lcyBub3QgaW52ZW50IGRhdGEuIEluIG91ciByZWNlbnQgdGVzdCBmb3IgQXVzdGluIHdlYiBkZXNpZ24gbGVhZHMsIGl0IHJldHVybmVkIHplcm8gcmVzdWx0cyByYXRoZXIgdGhhbiBoYWxsdWNpbmF0aW5nIGNvbnRhY3RzLiBUaGF0IGludGVncml0eSBpcyB0aGUgY29yZSB2YWx1ZSBwcm9wb3NpdGlvbi4gSWYgaXQgZG9lc27igJl0IGhhdmUgYSBzb3VyY2UtYmFja2VkIGFuc3dlciwgaXQgc2F5cyBzby5cblxuSeKAmW0gbm90IHRyeWluZyB0byBzZWxsIHlvdSBhIHN1YnNjcmlwdGlvbiByaWdodCBub3cuIEnigJltIHNoYXJpbmcgdGhpcyBiZWNhdXNlIHRoZSB0ZWNobm9sb2d5IGlzIHJlYWR5IGZvciBwdWJsaWMgYmV0YSwgYW5kIEkgd2FudCB0byBzZWUgaWYgaXQgc29sdmVzIGEgcmVhbCBnYXAgaW4geW91ciBjdXJyZW50IHN0YWNrLlxuXG5JZiB5b3XigJlyZSBjdXJpb3VzIGFib3V0IGhvdyB0aGUgY3J5cHRvZ3JhcGhpYyB0cnVzdCBzY29yZXMgd29yayBvciB3YW50IHRvIHRlc3QgdGhlIGluamVjdGlvbiBibG9ja2luZyBjYXBhYmlsaXRpZXMgb24geW91ciBvd24gcHJvbXB0cywgbGV04oCZcyBjaGF0LlxuXG5SZXBseSB3aXRoIFwidGVzdFwiIGFuZCBJ4oCZbGwgc2VuZCB5b3UgYSBkaXJlY3QgbGluayB0byB0aGUgc2FuZGJveC4gTm8gY3JlZGl0IGNhcmQgcmVxdWlyZWQuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5aYW1ibyBUZWFtIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=- 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:17d250ff4bb12acf6d794bbce50293bf171f6ab074db7c2b514bc9fcd2334190- 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
1b3daf154b49f4c611f067d4670c6dcf9f0362ba8ead53c8930589f0eeea90af- 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-25T11:46:39.518Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:845eec127b5e8a23d772b801ec62f86a244f1075e677280cc885c9cb0141bbbf","receipt_uuid":"902613b2-52d2-4a54-b1ab-4570190b6e0e","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/902613b2-52d2-4a54-b1ab-4570190b6e0e?ref=badge)
HTML
<a href="https://zambo.dev/run/902613b2-52d2-4a54-b1ab-4570190b6e0e?ref=badge"><img src="https://zambo.dev/api/receipt/902613b2-52d2-4a54-b1ab-4570190b6e0e/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
66,758 verifiable receipts minted
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.