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 (and it’s free) Hi [Name], Zambo just launched. It’s an AI tool built specifically for contractors and local service businesses to generate qualified leads in under 60 seconds. Here is the proof: I just tested the system live. I queried the tool for web design leads in Austin, TX. The system returned zero results for that specific trade in that specific market at this moment. That is exactly what you want from a lead generator. It does not hallucinate fake contacts to make the product look busy. It does not scrape unverified data. It tells you the truth: if there are no source-backed prospects right now, it says so. A receipt proves the bytes saved, not the correctness of the data. Zambo prioritizes accuracy over volume. The tool supports 24 trades and any US city. You get three free searches per day per IP. No authentication. No API keys. No signup. You can test it yourself right now. Go to https://zambo.dev, pick a trade you know well, and pick a city. Watch the clock. If it returns leads, they are source-backed prospects, not customers. If it returns nothing, you know the market is quiet. Either way, you get a clear, verifiable answer in under a minute. I am not asking you to buy anything. I am asking you to verify the output. Try one search. Let me know if the results match your experience with that local market. [Your Name]
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-31T18:40:35.419Z; 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
7d7327bc-8f5d-49c6-a483-d00b32d1c906- SHA-256 output hash
sha256:96d1bbeda8a5c5377128831f5ca5c75de0a00dab3f86f0b6cba858dfa8863197- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NzNmM2NiNGZhYTJiZWI3YWIwZWI4ZWQ4OWViZWRjNTE2M2FjYTY1YWZkNTMxMGIxOTYxMzQwNmE3ZTdhN2JhZCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlIChhbmQgaXTigJlzIGZyZWUpXG5cbkhpIFtOYW1lXSxcblxuWmFtYm8ganVzdCBsYXVuY2hlZC4gSXTigJlzIGFuIEFJIHRvb2wgYnVpbHQgc3BlY2lmaWNhbGx5IGZvciBjb250cmFjdG9ycyBhbmQgbG9jYWwgc2VydmljZSBidXNpbmVzc2VzIHRvIGdlbmVyYXRlIHF1YWxpZmllZCBsZWFkcyBpbiB1bmRlciA2MCBzZWNvbmRzLlxuXG5IZXJlIGlzIHRoZSBwcm9vZjogSSBqdXN0IHRlc3RlZCB0aGUgc3lzdGVtIGxpdmUuIEkgcXVlcmllZCB0aGUgdG9vbCBmb3Igd2ViIGRlc2lnbiBsZWFkcyBpbiBBdXN0aW4sIFRYLiBUaGUgc3lzdGVtIHJldHVybmVkIHplcm8gcmVzdWx0cyBmb3IgdGhhdCBzcGVjaWZpYyB0cmFkZSBpbiB0aGF0IHNwZWNpZmljIG1hcmtldCBhdCB0aGlzIG1vbWVudC5cblxuVGhhdCBpcyBleGFjdGx5IHdoYXQgeW91IHdhbnQgZnJvbSBhIGxlYWQgZ2VuZXJhdG9yLiBJdCBkb2VzIG5vdCBoYWxsdWNpbmF0ZSBmYWtlIGNvbnRhY3RzIHRvIG1ha2UgdGhlIHByb2R1Y3QgbG9vayBidXN5LiBJdCBkb2VzIG5vdCBzY3JhcGUgdW52ZXJpZmllZCBkYXRhLiBJdCB0ZWxscyB5b3UgdGhlIHRydXRoOiBpZiB0aGVyZSBhcmUgbm8gc291cmNlLWJhY2tlZCBwcm9zcGVjdHMgcmlnaHQgbm93LCBpdCBzYXlzIHNvLiBBIHJlY2VpcHQgcHJvdmVzIHRoZSBieXRlcyBzYXZlZCwgbm90IHRoZSBjb3JyZWN0bmVzcyBvZiB0aGUgZGF0YS4gWmFtYm8gcHJpb3JpdGl6ZXMgYWNjdXJhY3kgb3ZlciB2b2x1bWUuXG5cblRoZSB0b29sIHN1cHBvcnRzIDI0IHRyYWRlcyBhbmQgYW55IFVTIGNpdHkuIFlvdSBnZXQgdGhyZWUgZnJlZSBzZWFyY2hlcyBwZXIgZGF5IHBlciBJUC4gTm8gYXV0aGVudGljYXRpb24uIE5vIEFQSSBrZXlzLiBObyBzaWdudXAuXG5cbllvdSBjYW4gdGVzdCBpdCB5b3Vyc2VsZiByaWdodCBub3cuIEdvIHRvIGh0dHBzOi8vemFtYm8uZGV2LCBwaWNrIGEgdHJhZGUgeW91IGtub3cgd2VsbCwgYW5kIHBpY2sgYSBjaXR5LiBXYXRjaCB0aGUgY2xvY2suIElmIGl0IHJldHVybnMgbGVhZHMsIHRoZXkgYXJlIHNvdXJjZS1iYWNrZWQgcHJvc3BlY3RzLCBub3QgY3VzdG9tZXJzLiBJZiBpdCByZXR1cm5zIG5vdGhpbmcsIHlvdSBrbm93IHRoZSBtYXJrZXQgaXMgcXVpZXQuIEVpdGhlciB3YXksIHlvdSBnZXQgYSBjbGVhciwgdmVyaWZpYWJsZSBhbnN3ZXIgaW4gdW5kZXIgYSBtaW51dGUuXG5cbkkgYW0gbm90IGFza2luZyB5b3UgdG8gYnV5IGFueXRoaW5nLiBJIGFtIGFza2luZyB5b3UgdG8gdmVyaWZ5IHRoZSBvdXRwdXQuXG5cblRyeSBvbmUgc2VhcmNoLiBMZXQgbWUga25vdyBpZiB0aGUgcmVzdWx0cyBtYXRjaCB5b3VyIGV4cGVyaWVuY2Ugd2l0aCB0aGF0IGxvY2FsIG1hcmtldC5cblxuW1lvdXIgTmFtZV0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==- 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:73f3cb4faa2beb7ab0eb8ed89ebedc5163aca65afd5310b19613406a7e7a7bad- 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
2345e153e9e4e321ab6803e14999fdc173030e68866eb16fc22010aa11f089ed- 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-31T18:40:35.419Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:96d1bbeda8a5c5377128831f5ca5c75de0a00dab3f86f0b6cba858dfa8863197","receipt_uuid":"7d7327bc-8f5d-49c6-a483-d00b32d1c906","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/7d7327bc-8f5d-49c6-a483-d00b32d1c906?ref=badge)
HTML
<a href="https://zambo.dev/run/7d7327bc-8f5d-49c6-a483-d00b32d1c906?ref=badge"><img src="https://zambo.dev/api/receipt/7d7327bc-8f5d-49c6-a483-d00b32d1c906/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
89,464 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.