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: 5 qualified leads in 60 seconds Hi [Name], Stop guessing who to call. Zambo identifies source-backed prospects for your trade and city in under a minute. We just launched. The system scans public data to find businesses actively needing services. For example, when we queried "web design" in Austin, TX, the tool returned zero results. That is the point. It saves you from cold-calling dead ends. You only get names that match your criteria based on current public signals. These are prospects, not customers. The receipt confirms the data was retrieved, not that the lead is ready to buy. You still have to execute. But you start with verified data, not a scraped list of unknowns. The platform supports 24 trades across all US cities. You get five qualified leads per search. No manual filtering. No blind dials. Just a clear path from search to contact. Try it now. Pick your trade and city. If the tool finds no matches, it tells you immediately. If it finds five, you have your week’s outreach list. [Button: Search My Trade] This is the start. We are building the stack for local service businesses who refuse to waste time on bad data. Best, [Your Name] Zambo Team

This is the saved result preview, not proof that the answer was correct.

Verify saved bytes Run your own
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.

UNLOCK 24H DAY PASS ($0.99) →

See all plans on the pricing page →

RUN YOUR OWN FREE CALL →

Or re-run this exact call, using the same tool and arguments.

Share this receipt

Share on X · Share on LinkedIn ·

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-20T05:39:34.336Z; external immutability is not checked

Get proof like this from your own AI

Add to my 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
e8e2a49a-4fbf-4392-ba32-6002409257b9
SHA-256 output hash
sha256:bfd0092208bcf29dbc035fd4d8f93486d27bde1ef5529b689ef5bdb5407756a7
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MjFiMmM1YmNlY2VmNmMyNGNjYWUwYTNjNGRkZmY3OTdmZTU3YjdmYzI3MzYxYTQ2MzZkZjFlOWRhNWM4OTVmYiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiA1IHF1YWxpZmllZCBsZWFkcyBpbiA2MCBzZWNvbmRzXG5cbkhpIFtOYW1lXSxcblxuU3RvcCBndWVzc2luZyB3aG8gdG8gY2FsbC4gWmFtYm8gaWRlbnRpZmllcyBzb3VyY2UtYmFja2VkIHByb3NwZWN0cyBmb3IgeW91ciB0cmFkZSBhbmQgY2l0eSBpbiB1bmRlciBhIG1pbnV0ZS5cblxuV2UganVzdCBsYXVuY2hlZC4gVGhlIHN5c3RlbSBzY2FucyBwdWJsaWMgZGF0YSB0byBmaW5kIGJ1c2luZXNzZXMgYWN0aXZlbHkgbmVlZGluZyBzZXJ2aWNlcy4gRm9yIGV4YW1wbGUsIHdoZW4gd2UgcXVlcmllZCBcIndlYiBkZXNpZ25cIiBpbiBBdXN0aW4sIFRYLCB0aGUgdG9vbCByZXR1cm5lZCB6ZXJvIHJlc3VsdHMuIFRoYXQgaXMgdGhlIHBvaW50LiBJdCBzYXZlcyB5b3UgZnJvbSBjb2xkLWNhbGxpbmcgZGVhZCBlbmRzLiBZb3Ugb25seSBnZXQgbmFtZXMgdGhhdCBtYXRjaCB5b3VyIGNyaXRlcmlhIGJhc2VkIG9uIGN1cnJlbnQgcHVibGljIHNpZ25hbHMuXG5cblRoZXNlIGFyZSBwcm9zcGVjdHMsIG5vdCBjdXN0b21lcnMuIFRoZSByZWNlaXB0IGNvbmZpcm1zIHRoZSBkYXRhIHdhcyByZXRyaWV2ZWQsIG5vdCB0aGF0IHRoZSBsZWFkIGlzIHJlYWR5IHRvIGJ1eS4gWW91IHN0aWxsIGhhdmUgdG8gZXhlY3V0ZS4gQnV0IHlvdSBzdGFydCB3aXRoIHZlcmlmaWVkIGRhdGEsIG5vdCBhIHNjcmFwZWQgbGlzdCBvZiB1bmtub3ducy5cblxuVGhlIHBsYXRmb3JtIHN1cHBvcnRzIDI0IHRyYWRlcyBhY3Jvc3MgYWxsIFVTIGNpdGllcy4gWW91IGdldCBmaXZlIHF1YWxpZmllZCBsZWFkcyBwZXIgc2VhcmNoLiBObyBtYW51YWwgZmlsdGVyaW5nLiBObyBibGluZCBkaWFscy4gSnVzdCBhIGNsZWFyIHBhdGggZnJvbSBzZWFyY2ggdG8gY29udGFjdC5cblxuVHJ5IGl0IG5vdy4gUGljayB5b3VyIHRyYWRlIGFuZCBjaXR5LiBJZiB0aGUgdG9vbCBmaW5kcyBubyBtYXRjaGVzLCBpdCB0ZWxscyB5b3UgaW1tZWRpYXRlbHkuIElmIGl0IGZpbmRzIGZpdmUsIHlvdSBoYXZlIHlvdXIgd2Vla+KAmXMgb3V0cmVhY2ggbGlzdC5cblxuW0J1dHRvbjogU2VhcmNoIE15IFRyYWRlXVxuXG5UaGlzIGlzIHRoZSBzdGFydC4gV2UgYXJlIGJ1aWxkaW5nIHRoZSBzdGFjayBmb3IgbG9jYWwgc2VydmljZSBidXNpbmVzc2VzIHdobyByZWZ1c2UgdG8gd2FzdGUgdGltZSBvbiBiYWQgZGF0YS5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cblphbWJvIFRlYW0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjEuNCJ9fQ==
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:21b2c5bcecef6c24ccae0a3c4ddff797fe57b7fc27361a4636df1e9da5c895fb
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
91a13ac86a0af2af34c829c3c9c235a2405b566a61ba37f87d9b2fe9cee3a406
Anchor status
published
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-20T05:39:34.336Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:bfd0092208bcf29dbc035fd4d8f93486d27bde1ef5529b689ef5bdb5407756a7","receipt_uuid":"e8e2a49a-4fbf-4392-ba32-6002409257b9","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

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/e8e2a49a-4fbf-4392-ba32-6002409257b9/badge.svg)](https://zambo.dev/run/e8e2a49a-4fbf-4392-ba32-6002409257b9?ref=badge)

HTML

<a href="https://zambo.dev/run/e8e2a49a-4fbf-4392-ba32-6002409257b9?ref=badge"><img src="https://zambo.dev/api/receipt/e8e2a49a-4fbf-4392-ba32-6002409257b9/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

151,692 verifiable receipts minted

RUN YOUR OWN FREE CALL →

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.