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 Hi [Name], Zambo is officially live. The core function is simple: enter a trade type and a US city. Within 60 seconds, the system returns five qualified leads with contact information. It supports 24 trades. This is not a theoretical demo. Today, I tested the search for web design leads in Austin, TX. The engine processed the query and confirmed zero matches for that specific moment. That result is accurate. It proves the system is checking real-time source data, not just returning pre-canned lists. The platform also includes a monitoring feature. If a search returns no results, you can set a watch. The system will notify you via email or Telegram the instant new, matching opportunities appear in that market. The value proposition is speed and precision for local service businesses. You stop guessing where the demand is. You see exactly where it is, right now. If you want to test a specific trade in your city, here is what to do: 1. Go to the Zambo dashboard. 2. Select your trade (e.g., roofer, plumber, electrician). 3. Enter your target city. 4. Run the search. You will know within one minute if there are five qualified prospects waiting for you. If not, set the watch and wait for the alert. No credit card required for the initial check. Let me know if you want to test a specific market. Best, [Your Name] [Your Title] Zambo
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-22T02:14:12.953Z; 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
b84ee80a-8b48-4919-98e1-58ebaf3a40a4- SHA-256 output hash
sha256:e1b9f7a91cd0d10fe1a5ce75b9999b69ee4b2b26661833f5529c6d1202c37a01- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YzQ3YmQ5YjIyMDk5NzE4MDUxMDBkZWI0NmQ1YmJiMTdjZmU2MGQzNGZhZWM4YjM2ZGE3YmVhMTM3MDgxMGVhZiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlXG5cbkhpIFtOYW1lXSxcblxuWmFtYm8gaXMgb2ZmaWNpYWxseSBsaXZlLlxuXG5UaGUgY29yZSBmdW5jdGlvbiBpcyBzaW1wbGU6IGVudGVyIGEgdHJhZGUgdHlwZSBhbmQgYSBVUyBjaXR5LiBXaXRoaW4gNjAgc2Vjb25kcywgdGhlIHN5c3RlbSByZXR1cm5zIGZpdmUgcXVhbGlmaWVkIGxlYWRzIHdpdGggY29udGFjdCBpbmZvcm1hdGlvbi4gSXQgc3VwcG9ydHMgMjQgdHJhZGVzLlxuXG5UaGlzIGlzIG5vdCBhIHRoZW9yZXRpY2FsIGRlbW8uIFRvZGF5LCBJIHRlc3RlZCB0aGUgc2VhcmNoIGZvciB3ZWIgZGVzaWduIGxlYWRzIGluIEF1c3RpbiwgVFguIFRoZSBlbmdpbmUgcHJvY2Vzc2VkIHRoZSBxdWVyeSBhbmQgY29uZmlybWVkIHplcm8gbWF0Y2hlcyBmb3IgdGhhdCBzcGVjaWZpYyBtb21lbnQuIFRoYXQgcmVzdWx0IGlzIGFjY3VyYXRlLiBJdCBwcm92ZXMgdGhlIHN5c3RlbSBpcyBjaGVja2luZyByZWFsLXRpbWUgc291cmNlIGRhdGEsIG5vdCBqdXN0IHJldHVybmluZyBwcmUtY2FubmVkIGxpc3RzLlxuXG5UaGUgcGxhdGZvcm0gYWxzbyBpbmNsdWRlcyBhIG1vbml0b3JpbmcgZmVhdHVyZS4gSWYgYSBzZWFyY2ggcmV0dXJucyBubyByZXN1bHRzLCB5b3UgY2FuIHNldCBhIHdhdGNoLiBUaGUgc3lzdGVtIHdpbGwgbm90aWZ5IHlvdSB2aWEgZW1haWwgb3IgVGVsZWdyYW0gdGhlIGluc3RhbnQgbmV3LCBtYXRjaGluZyBvcHBvcnR1bml0aWVzIGFwcGVhciBpbiB0aGF0IG1hcmtldC5cblxuVGhlIHZhbHVlIHByb3Bvc2l0aW9uIGlzIHNwZWVkIGFuZCBwcmVjaXNpb24gZm9yIGxvY2FsIHNlcnZpY2UgYnVzaW5lc3Nlcy4gWW91IHN0b3AgZ3Vlc3Npbmcgd2hlcmUgdGhlIGRlbWFuZCBpcy4gWW91IHNlZSBleGFjdGx5IHdoZXJlIGl0IGlzLCByaWdodCBub3cuXG5cbklmIHlvdSB3YW50IHRvIHRlc3QgYSBzcGVjaWZpYyB0cmFkZSBpbiB5b3VyIGNpdHksIGhlcmUgaXMgd2hhdCB0byBkbzpcblxuMS4gIEdvIHRvIHRoZSBaYW1ibyBkYXNoYm9hcmQuXG4yLiAgU2VsZWN0IHlvdXIgdHJhZGUgKGUuZy4sIHJvb2ZlciwgcGx1bWJlciwgZWxlY3RyaWNpYW4pLlxuMy4gIEVudGVyIHlvdXIgdGFyZ2V0IGNpdHkuXG40LiAgUnVuIHRoZSBzZWFyY2guXG5cbllvdSB3aWxsIGtub3cgd2l0aGluIG9uZSBtaW51dGUgaWYgdGhlcmUgYXJlIGZpdmUgcXVhbGlmaWVkIHByb3NwZWN0cyB3YWl0aW5nIGZvciB5b3UuIElmIG5vdCwgc2V0IHRoZSB3YXRjaCBhbmQgd2FpdCBmb3IgdGhlIGFsZXJ0LlxuXG5ObyBjcmVkaXQgY2FyZCByZXF1aXJlZCBmb3IgdGhlIGluaXRpYWwgY2hlY2suXG5cbkxldCBtZSBrbm93IGlmIHlvdSB3YW50IHRvIHRlc3QgYSBzcGVjaWZpYyBtYXJrZXQuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5bWW91ciBUaXRsZV1cblphbWJvIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4xLjQifX0=- 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:c47bd9b2209971805100deb46d5bbb17cfe60d34faec8b36da7bea1370810eaf- 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
b090d23ba5aebaf4c87c8ed5688c49b412549317f37b0b7825053bd7d8b16aeb- Anchor status
- published
- Public key
e13475107d30c918ec664adf2ab•••••24a22fb35190f82c9e933704fa49af41
Relay hints: wss://relay.primal.net
Schema: zambo-receipt-anchor/1
Anchor envelope bytes:
{"anchored_at":"2026-11-22T02:14:12.953Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:e1b9f7a91cd0d10fe1a5ce75b9999b69ee4b2b26661833f5529c6d1202c37a01","receipt_uuid":"b84ee80a-8b48-4919-98e1-58ebaf3a40a4","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. Open the browser receipt checker. 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/b84ee80a-8b48-4919-98e1-58ebaf3a40a4?ref=badge)
HTML
<a href="https://zambo.dev/run/b84ee80a-8b48-4919-98e1-58ebaf3a40a4?ref=badge"><img src="https://zambo.dev/api/receipt/b84ee80a-8b48-4919-98e1-58ebaf3a40a4/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
158,345 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.