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 research for local trades** Hi [Name], Zambo is officially live. We built it to solve one specific problem: finding qualified, source-backed prospects for local service businesses without the manual drudgery of scraping directories. We tested the current engine against a live query for web designers in Austin, Texas. The result was zero matches. This is the point. Zambo does not hallucinate leads to fill a quota. It returns only what is verifiable in public sources right now. If the data isn't there, you know immediately, saving you hours of chasing ghost contacts. The platform supports 24 trades across any US city. You enter the trade and location; the system executes a semantic scan against real-time public data. You get a receipt for every run, proving exactly what was saved and when. No hidden logic. No fabricated names. Just a clear status: leads found or no results. This transparency is critical. In a market flooded with AI tools that promise "magic" leads, Zambo offers auditability. You see the execution plan, the tool used, and the specific output. You decide if the prospect is worth a call. We don’t guess; we report. **Next Step** We are currently opening access to early users who want to test the engine on their specific trade and city. Reply with **one trade** and **one city** you want to check. We will run the scan and send you the raw results, including the execution receipt, so you can verify the accuracy yourself. We are not selling you a list. We are giving you a tool that tells the truth about your market. 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-11-16T16:56:43.584Z; 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
ec22e2cb-93a5-4f56-9732-55cb24d62dfc- SHA-256 output hash
sha256:f62e9739a29cccfe3bab15df4bf163d652bea30ff3aaa83d7ea6d939bf91d979- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6N2Q1NzMyYjZkNmY5M2ExMzVjZjQxNzFlN2FlYjVmZmJjZWVkZWM0ZjFmMTFkZmE4YjE1MzVkYjg0ZjRhMjRhYyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiIqKlN1YmplY3Q6IFphbWJvIGlzIGxpdmU6IDYwLXNlY29uZCBsZWFkIHJlc2VhcmNoIGZvciBsb2NhbCB0cmFkZXMqKlxuXG5IaSBbTmFtZV0sXG5cblphbWJvIGlzIG9mZmljaWFsbHkgbGl2ZS4gV2UgYnVpbHQgaXQgdG8gc29sdmUgb25lIHNwZWNpZmljIHByb2JsZW06IGZpbmRpbmcgcXVhbGlmaWVkLCBzb3VyY2UtYmFja2VkIHByb3NwZWN0cyBmb3IgbG9jYWwgc2VydmljZSBidXNpbmVzc2VzIHdpdGhvdXQgdGhlIG1hbnVhbCBkcnVkZ2VyeSBvZiBzY3JhcGluZyBkaXJlY3Rvcmllcy5cblxuV2UgdGVzdGVkIHRoZSBjdXJyZW50IGVuZ2luZSBhZ2FpbnN0IGEgbGl2ZSBxdWVyeSBmb3Igd2ViIGRlc2lnbmVycyBpbiBBdXN0aW4sIFRleGFzLiBUaGUgcmVzdWx0IHdhcyB6ZXJvIG1hdGNoZXMuIFRoaXMgaXMgdGhlIHBvaW50LiBaYW1ibyBkb2VzIG5vdCBoYWxsdWNpbmF0ZSBsZWFkcyB0byBmaWxsIGEgcXVvdGEuIEl0IHJldHVybnMgb25seSB3aGF0IGlzIHZlcmlmaWFibGUgaW4gcHVibGljIHNvdXJjZXMgcmlnaHQgbm93LiBJZiB0aGUgZGF0YSBpc24ndCB0aGVyZSwgeW91IGtub3cgaW1tZWRpYXRlbHksIHNhdmluZyB5b3UgaG91cnMgb2YgY2hhc2luZyBnaG9zdCBjb250YWN0cy5cblxuVGhlIHBsYXRmb3JtIHN1cHBvcnRzIDI0IHRyYWRlcyBhY3Jvc3MgYW55IFVTIGNpdHkuIFlvdSBlbnRlciB0aGUgdHJhZGUgYW5kIGxvY2F0aW9uOyB0aGUgc3lzdGVtIGV4ZWN1dGVzIGEgc2VtYW50aWMgc2NhbiBhZ2FpbnN0IHJlYWwtdGltZSBwdWJsaWMgZGF0YS4gWW91IGdldCBhIHJlY2VpcHQgZm9yIGV2ZXJ5IHJ1biwgcHJvdmluZyBleGFjdGx5IHdoYXQgd2FzIHNhdmVkIGFuZCB3aGVuLiBObyBoaWRkZW4gbG9naWMuIE5vIGZhYnJpY2F0ZWQgbmFtZXMuIEp1c3QgYSBjbGVhciBzdGF0dXM6IGxlYWRzIGZvdW5kIG9yIG5vIHJlc3VsdHMuXG5cblRoaXMgdHJhbnNwYXJlbmN5IGlzIGNyaXRpY2FsLiBJbiBhIG1hcmtldCBmbG9vZGVkIHdpdGggQUkgdG9vbHMgdGhhdCBwcm9taXNlIFwibWFnaWNcIiBsZWFkcywgWmFtYm8gb2ZmZXJzIGF1ZGl0YWJpbGl0eS4gWW91IHNlZSB0aGUgZXhlY3V0aW9uIHBsYW4sIHRoZSB0b29sIHVzZWQsIGFuZCB0aGUgc3BlY2lmaWMgb3V0cHV0LiBZb3UgZGVjaWRlIGlmIHRoZSBwcm9zcGVjdCBpcyB3b3J0aCBhIGNhbGwuIFdlIGRvbuKAmXQgZ3Vlc3M7IHdlIHJlcG9ydC5cblxuKipOZXh0IFN0ZXAqKlxuXG5XZSBhcmUgY3VycmVudGx5IG9wZW5pbmcgYWNjZXNzIHRvIGVhcmx5IHVzZXJzIHdobyB3YW50IHRvIHRlc3QgdGhlIGVuZ2luZSBvbiB0aGVpciBzcGVjaWZpYyB0cmFkZSBhbmQgY2l0eS4gUmVwbHkgd2l0aCAqKm9uZSB0cmFkZSoqIGFuZCAqKm9uZSBjaXR5KiogeW91IHdhbnQgdG8gY2hlY2suIFdlIHdpbGwgcnVuIHRoZSBzY2FuIGFuZCBzZW5kIHlvdSB0aGUgcmF3IHJlc3VsdHMsIGluY2x1ZGluZyB0aGUgZXhlY3V0aW9uIHJlY2VpcHQsIHNvIHlvdSBjYW4gdmVyaWZ5IHRoZSBhY2N1cmFjeSB5b3Vyc2VsZi5cblxuV2UgYXJlIG5vdCBzZWxsaW5nIHlvdSBhIGxpc3QuIFdlIGFyZSBnaXZpbmcgeW91IGEgdG9vbCB0aGF0IHRlbGxzIHRoZSB0cnV0aCBhYm91dCB5b3VyIG1hcmtldC5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cblphbWJvIFRlYW0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjEuNCJ9fQ==- Timestamp
Bound call context
- Receipt schema
0.4- Tool name
write- Tool version
4.1.4- Permission scope
public- Caller type
session- Caller ID
sha256:7d5732b6d6f93a135cf4171e7aeb5ffbceedec4f1f11dfa8b1535db84f4a24ac- 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
95d76a31c418fccb6b7e42e0b5d665f89b3286f0b5ac8320cf305b3424f13879- Anchor status
- published
- Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41
Relay hints: wss://relay.primal.net
Schema: zambo-receipt-anchor/1
Anchor envelope bytes:
{"anchored_at":"2026-11-16T16:56:43.584Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:f62e9739a29cccfe3bab15df4bf163d652bea30ff3aaa83d7ea6d939bf91d979","receipt_uuid":"ec22e2cb-93a5-4f56-9732-55cb24d62dfc","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/ec22e2cb-93a5-4f56-9732-55cb24d62dfc?ref=badge)
HTML
<a href="https://zambo.dev/run/ec22e2cb-93a5-4f56-9732-55cb24d62dfc?ref=badge"><img src="https://zambo.dev/api/receipt/ec22e2cb-93a5-4f56-9732-55cb24d62dfc/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
142,547 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.