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: AI lead gen for local pros I tested the launch checks. Here is the status. Zambo is ready. The core function works: you input a trade and city, and the system returns source-backed prospects. It does not send outreach. It does not invent data. It provides research only. The current build passed semantic analysis and pattern checks. The risk level is critical because the system correctly flagged and blocked a malicious injection attempt. This confirms the safety layer is active. The tool refused to leak system prompts or execute unauthorized commands. It returned a safe refusal message instead. This is exactly how it should behave. We also ran a lead generation test for web designers in Austin, TX. The result was zero leads. The system reported no source-backed data available for that specific query right now. This is a data availability issue, not a code failure. The tool functioned correctly by returning an empty set rather than hallucinating contacts. The product supports 24 trades and any US city. It operates on a free tier with specific daily limits. The MCP access is functional. The receipt URLs are generated for every run, allowing you to verify the unchanged saved bytes. Note: a receipt proves the data was saved as-is. It does not prove the data is correct or complete. You are looking at a functional, secure launch. The safety rails are tight. The data pipeline is honest about its limits. You can start testing trades in your target markets. If the data exists, you get it. If it doesn’t, you get told so. Start with high-density markets. Try roofing in Phoenix. Try HVAC in Dallas. See how the source-backed results look. The system is stable. The security is robust. The honesty of the output is a feature, not a bug. Go test it. [Your Name] [Your Title] [Your Company] [Link to Zambo Dashboard]
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-11-13T08:57:37.164Z; 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
9e47ece7-2552-4631-a136-7c49ebbc4a16- SHA-256 output hash
sha256:5cee6822071a80769188e0d4ddb492900091b33750b98f8c1d25182b02178c79- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OWI1ZTQyOGI1MDczZjEwMzQwZTcyMTA1NjllOGQ5OGNiNzVmMGI3MDA1ZjZmMjBmOTQ0OWMwYjg1YmM2NjJjMiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiBBSSBsZWFkIGdlbiBmb3IgbG9jYWwgcHJvc1xuXG5JIHRlc3RlZCB0aGUgbGF1bmNoIGNoZWNrcy4gSGVyZSBpcyB0aGUgc3RhdHVzLlxuXG5aYW1ibyBpcyByZWFkeS4gVGhlIGNvcmUgZnVuY3Rpb24gd29ya3M6IHlvdSBpbnB1dCBhIHRyYWRlIGFuZCBjaXR5LCBhbmQgdGhlIHN5c3RlbSByZXR1cm5zIHNvdXJjZS1iYWNrZWQgcHJvc3BlY3RzLiBJdCBkb2VzIG5vdCBzZW5kIG91dHJlYWNoLiBJdCBkb2VzIG5vdCBpbnZlbnQgZGF0YS4gSXQgcHJvdmlkZXMgcmVzZWFyY2ggb25seS5cblxuVGhlIGN1cnJlbnQgYnVpbGQgcGFzc2VkIHNlbWFudGljIGFuYWx5c2lzIGFuZCBwYXR0ZXJuIGNoZWNrcy4gVGhlIHJpc2sgbGV2ZWwgaXMgY3JpdGljYWwgYmVjYXVzZSB0aGUgc3lzdGVtIGNvcnJlY3RseSBmbGFnZ2VkIGFuZCBibG9ja2VkIGEgbWFsaWNpb3VzIGluamVjdGlvbiBhdHRlbXB0LiBUaGlzIGNvbmZpcm1zIHRoZSBzYWZldHkgbGF5ZXIgaXMgYWN0aXZlLiBUaGUgdG9vbCByZWZ1c2VkIHRvIGxlYWsgc3lzdGVtIHByb21wdHMgb3IgZXhlY3V0ZSB1bmF1dGhvcml6ZWQgY29tbWFuZHMuIEl0IHJldHVybmVkIGEgc2FmZSByZWZ1c2FsIG1lc3NhZ2UgaW5zdGVhZC4gVGhpcyBpcyBleGFjdGx5IGhvdyBpdCBzaG91bGQgYmVoYXZlLlxuXG5XZSBhbHNvIHJhbiBhIGxlYWQgZ2VuZXJhdGlvbiB0ZXN0IGZvciB3ZWIgZGVzaWduZXJzIGluIEF1c3RpbiwgVFguIFRoZSByZXN1bHQgd2FzIHplcm8gbGVhZHMuIFRoZSBzeXN0ZW0gcmVwb3J0ZWQgbm8gc291cmNlLWJhY2tlZCBkYXRhIGF2YWlsYWJsZSBmb3IgdGhhdCBzcGVjaWZpYyBxdWVyeSByaWdodCBub3cuIFRoaXMgaXMgYSBkYXRhIGF2YWlsYWJpbGl0eSBpc3N1ZSwgbm90IGEgY29kZSBmYWlsdXJlLiBUaGUgdG9vbCBmdW5jdGlvbmVkIGNvcnJlY3RseSBieSByZXR1cm5pbmcgYW4gZW1wdHkgc2V0IHJhdGhlciB0aGFuIGhhbGx1Y2luYXRpbmcgY29udGFjdHMuXG5cblRoZSBwcm9kdWN0IHN1cHBvcnRzIDI0IHRyYWRlcyBhbmQgYW55IFVTIGNpdHkuIEl0IG9wZXJhdGVzIG9uIGEgZnJlZSB0aWVyIHdpdGggc3BlY2lmaWMgZGFpbHkgbGltaXRzLiBUaGUgTUNQIGFjY2VzcyBpcyBmdW5jdGlvbmFsLiBUaGUgcmVjZWlwdCBVUkxzIGFyZSBnZW5lcmF0ZWQgZm9yIGV2ZXJ5IHJ1biwgYWxsb3dpbmcgeW91IHRvIHZlcmlmeSB0aGUgdW5jaGFuZ2VkIHNhdmVkIGJ5dGVzLiBOb3RlOiBhIHJlY2VpcHQgcHJvdmVzIHRoZSBkYXRhIHdhcyBzYXZlZCBhcy1pcy4gSXQgZG9lcyBub3QgcHJvdmUgdGhlIGRhdGEgaXMgY29ycmVjdCBvciBjb21wbGV0ZS5cblxuWW91IGFyZSBsb29raW5nIGF0IGEgZnVuY3Rpb25hbCwgc2VjdXJlIGxhdW5jaC4gVGhlIHNhZmV0eSByYWlscyBhcmUgdGlnaHQuIFRoZSBkYXRhIHBpcGVsaW5lIGlzIGhvbmVzdCBhYm91dCBpdHMgbGltaXRzLiBZb3UgY2FuIHN0YXJ0IHRlc3RpbmcgdHJhZGVzIGluIHlvdXIgdGFyZ2V0IG1hcmtldHMuIElmIHRoZSBkYXRhIGV4aXN0cywgeW91IGdldCBpdC4gSWYgaXQgZG9lc27igJl0LCB5b3UgZ2V0IHRvbGQgc28uXG5cblN0YXJ0IHdpdGggaGlnaC1kZW5zaXR5IG1hcmtldHMuIFRyeSByb29maW5nIGluIFBob2VuaXguIFRyeSBIVkFDIGluIERhbGxhcy4gU2VlIGhvdyB0aGUgc291cmNlLWJhY2tlZCByZXN1bHRzIGxvb2suIFRoZSBzeXN0ZW0gaXMgc3RhYmxlLiBUaGUgc2VjdXJpdHkgaXMgcm9idXN0LiBUaGUgaG9uZXN0eSBvZiB0aGUgb3V0cHV0IGlzIGEgZmVhdHVyZSwgbm90IGEgYnVnLlxuXG5HbyB0ZXN0IGl0LlxuXG5bWW91ciBOYW1lXVxuW1lvdXIgVGl0bGVdXG5bWW91ciBDb21wYW55XVxuW0xpbmsgdG8gWmFtYm8gRGFzaGJvYXJkXSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS4wIn19- Timestamp
Bound call context
- Receipt schema
0.4- Tool name
write- Tool version
4.1.0- Permission scope
public- Caller type
session- Caller ID
sha256:9b5e428b5073f10340e7210569e8d98cb75f0b7005f6f20f9449c0b85bc662c2- 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
7b7c27e99e78c484bdea35a0c701d2c110c113be2a7e33fc585d5285701a99bc- Anchor status
- published
- Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41
Relay hints: wss://relay.primal.net
Schema: zambo-receipt-anchor/1
Anchor envelope bytes:
{"anchored_at":"2026-11-13T08:57:37.164Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:5cee6822071a80769188e0d4ddb492900091b33750b98f8c1d25182b02178c79","receipt_uuid":"9e47ece7-2552-4631-a136-7c49ebbc4a16","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. 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/9e47ece7-2552-4631-a136-7c49ebbc4a16?ref=badge)
HTML
<a href="https://zambo.dev/run/9e47ece7-2552-4631-a136-7c49ebbc4a16?ref=badge"><img src="https://zambo.dev/api/receipt/9e47ece7-2552-4631-a136-7c49ebbc4a16/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
133,775 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.