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: 60-second lead generation for local trades The wait is over. Zambo is officially live. If you run a local service business, you know the pain of chasing leads. You spend hours cold-calling or scrolling through vague online directories. That ends today. Zambo delivers five qualified, source-backed leads for your specific trade and city in under 60 seconds. No fluff. No guessing. Just verified prospects ready for outreach. We tested this with real data. We queried Austin, TX for web design leads. The system returned zero results because it refuses to hallucinate. It only returns what it can verify from public sources. This accuracy is non-negotiable. A receipt proves the data exists; it does not guarantee a sale, but it guarantees your time isn’t wasted on dead ends. Zambo supports 24 trades across any US city. Whether you are a roofer in Phoenix or a plumber in Seattle, the workflow is the same. Input your trade and location. Receive contact info. Draft your message. The tool handles the heavy lifting of research so you can focus on closing. This is a research-only tool. It does not send emails. It does not scrape private data. It aggregates public information to give you a head start. You keep full control of the conversation. Launch access is open now. You get three free searches per IP per day. That is enough to test the quality of the leads for your specific niche. If the data doesn’t meet your standards, you don’t need it. If it does, you have a repeatable pipeline. Stop wasting hours on manual prospecting. Let the machine find the names. You handle the handshake. [Link to Zambo Dashboard] Best, The 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-11-13T21:27:39.469Z; 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
6265d1f4-04ff-4550-adf7-43e06026504e- SHA-256 output hash
sha256:d472e3ec7a2d56a2156bc966953de8ac2c1998e8ac6ec9e6a103a4c0db58ee0c- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OWJmOTU4MTAyNjU4YjFmMjA0YjdkOWUwNjBjZTJiZDg5MTA1OGM1MjE2YTM4NWMwMDk0ZTQ1NGU4ZGVhMmFkMyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiA2MC1zZWNvbmQgbGVhZCBnZW5lcmF0aW9uIGZvciBsb2NhbCB0cmFkZXNcblxuVGhlIHdhaXQgaXMgb3Zlci4gWmFtYm8gaXMgb2ZmaWNpYWxseSBsaXZlLlxuXG5JZiB5b3UgcnVuIGEgbG9jYWwgc2VydmljZSBidXNpbmVzcywgeW91IGtub3cgdGhlIHBhaW4gb2YgY2hhc2luZyBsZWFkcy4gWW91IHNwZW5kIGhvdXJzIGNvbGQtY2FsbGluZyBvciBzY3JvbGxpbmcgdGhyb3VnaCB2YWd1ZSBvbmxpbmUgZGlyZWN0b3JpZXMuIFRoYXQgZW5kcyB0b2RheS4gWmFtYm8gZGVsaXZlcnMgZml2ZSBxdWFsaWZpZWQsIHNvdXJjZS1iYWNrZWQgbGVhZHMgZm9yIHlvdXIgc3BlY2lmaWMgdHJhZGUgYW5kIGNpdHkgaW4gdW5kZXIgNjAgc2Vjb25kcy4gTm8gZmx1ZmYuIE5vIGd1ZXNzaW5nLiBKdXN0IHZlcmlmaWVkIHByb3NwZWN0cyByZWFkeSBmb3Igb3V0cmVhY2guXG5cbldlIHRlc3RlZCB0aGlzIHdpdGggcmVhbCBkYXRhLiBXZSBxdWVyaWVkIEF1c3RpbiwgVFggZm9yIHdlYiBkZXNpZ24gbGVhZHMuIFRoZSBzeXN0ZW0gcmV0dXJuZWQgemVybyByZXN1bHRzIGJlY2F1c2UgaXQgcmVmdXNlcyB0byBoYWxsdWNpbmF0ZS4gSXQgb25seSByZXR1cm5zIHdoYXQgaXQgY2FuIHZlcmlmeSBmcm9tIHB1YmxpYyBzb3VyY2VzLiBUaGlzIGFjY3VyYWN5IGlzIG5vbi1uZWdvdGlhYmxlLiBBIHJlY2VpcHQgcHJvdmVzIHRoZSBkYXRhIGV4aXN0czsgaXQgZG9lcyBub3QgZ3VhcmFudGVlIGEgc2FsZSwgYnV0IGl0IGd1YXJhbnRlZXMgeW91ciB0aW1lIGlzbuKAmXQgd2FzdGVkIG9uIGRlYWQgZW5kcy5cblxuWmFtYm8gc3VwcG9ydHMgMjQgdHJhZGVzIGFjcm9zcyBhbnkgVVMgY2l0eS4gV2hldGhlciB5b3UgYXJlIGEgcm9vZmVyIGluIFBob2VuaXggb3IgYSBwbHVtYmVyIGluIFNlYXR0bGUsIHRoZSB3b3JrZmxvdyBpcyB0aGUgc2FtZS4gSW5wdXQgeW91ciB0cmFkZSBhbmQgbG9jYXRpb24uIFJlY2VpdmUgY29udGFjdCBpbmZvLiBEcmFmdCB5b3VyIG1lc3NhZ2UuIFRoZSB0b29sIGhhbmRsZXMgdGhlIGhlYXZ5IGxpZnRpbmcgb2YgcmVzZWFyY2ggc28geW91IGNhbiBmb2N1cyBvbiBjbG9zaW5nLlxuXG5UaGlzIGlzIGEgcmVzZWFyY2gtb25seSB0b29sLiBJdCBkb2VzIG5vdCBzZW5kIGVtYWlscy4gSXQgZG9lcyBub3Qgc2NyYXBlIHByaXZhdGUgZGF0YS4gSXQgYWdncmVnYXRlcyBwdWJsaWMgaW5mb3JtYXRpb24gdG8gZ2l2ZSB5b3UgYSBoZWFkIHN0YXJ0LiBZb3Uga2VlcCBmdWxsIGNvbnRyb2wgb2YgdGhlIGNvbnZlcnNhdGlvbi5cblxuTGF1bmNoIGFjY2VzcyBpcyBvcGVuIG5vdy4gWW91IGdldCB0aHJlZSBmcmVlIHNlYXJjaGVzIHBlciBJUCBwZXIgZGF5LiBUaGF0IGlzIGVub3VnaCB0byB0ZXN0IHRoZSBxdWFsaXR5IG9mIHRoZSBsZWFkcyBmb3IgeW91ciBzcGVjaWZpYyBuaWNoZS4gSWYgdGhlIGRhdGEgZG9lc27igJl0IG1lZXQgeW91ciBzdGFuZGFyZHMsIHlvdSBkb27igJl0IG5lZWQgaXQuIElmIGl0IGRvZXMsIHlvdSBoYXZlIGEgcmVwZWF0YWJsZSBwaXBlbGluZS5cblxuU3RvcCB3YXN0aW5nIGhvdXJzIG9uIG1hbnVhbCBwcm9zcGVjdGluZy4gTGV0IHRoZSBtYWNoaW5lIGZpbmQgdGhlIG5hbWVzLiBZb3UgaGFuZGxlIHRoZSBoYW5kc2hha2UuXG5cbltMaW5rIHRvIFphbWJvIERhc2hib2FyZF1cblxuQmVzdCxcblxuVGhlIFphbWJvIFRlYW0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjEuMCJ9fQ==- 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:9bf958102658b1f204b7d9e060ce2bd891058c5216a385c0094e454e8dea2ad3- 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
df4add67c5793d45a659d972963d329f10e6e4abf05f2ab599d9c6d7a76ac2d0- Anchor status
- published
- Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41
Relay hints: wss://relay.primal.net
Schema: zambo-receipt-anchor/1
Anchor envelope bytes:
{"anchored_at":"2026-11-13T21:27:39.469Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:d472e3ec7a2d56a2156bc966953de8ac2c1998e8ac6ec9e6a103a4c0db58ee0c","receipt_uuid":"6265d1f4-04ff-4550-adf7-43e06026504e","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/6265d1f4-04ff-4550-adf7-43e06026504e?ref=badge)
HTML
<a href="https://zambo.dev/run/6265d1f4-04ff-4550-adf7-43e06026504e?ref=badge"><img src="https://zambo.dev/api/receipt/6265d1f4-04ff-4550-adf7-43e06026504e/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
134,879 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.