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 Launch: What’s Live (and What’s Not) Hi [Name], The launch checks are complete. Here is the reality of the current status, stripped of hype. **The Critical Block** Our deep semantic scan flagged the primary outreach prompt as **Critical Risk**. It detected an "Instruction Override" and "Prompt Leak Attempt" with 100% injection risk. The system correctly blocked execution. This is a security win. The guardrails are tight, and malicious patterns are being caught before they touch your data. Do not bypass this. The block is working as designed. **The Tool Test** We ran LeadSignal for web design leads in Austin, TX. * **Result:** Zero source-backed leads found. * **Status:** The tool executed successfully but returned no data for this specific query. * **Quota:** 3/3 free searches remaining. **The Receipt** The receipts provided (e.g., `zambo.dev/run/...`) prove that the system processed the request and saved the output bytes. **They do not prove correctness or quality.** A receipt confirms the action happened, not that the result is useful. Do not treat these links as proof of value. They are proof of execution. **What this means for you** Zambo is live. The security layer is aggressive and effective. The lead generation tool is functional but currently dry for that specific search. We have no fabricated customers. We have no invented fixes. We have a working infrastructure that refuses to play loose with security. **Next Step** I need your go/no-go on the security strictness. 1. **Maintain:** Keep the current block rules. Safe, but may flag valid complex prompts. 2. **Audit:** I will manually review the flagged patterns to see if we can tighten the rules without opening security holes. Reply with "1" or "2". I’ll proceed immediately. Best, [Your Name] Zambo Team

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

Check this receipt 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-10T10:13:04.656Z; 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
8f7e90b4-3269-476c-b5bf-eaff79b90838
SHA-256 output hash
sha256:c1e1a73fca4a305ceeb1358730a08871c4f9b6ef3a7314cdf749badece6c9960
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZGE0Mjg2MjIwYzhlNzY2YTY3YTU0MWI5N2RhMjU5Yzk5ZDlmMjlmNjFlNGMyNmUzMTBiMTE1MTgyOWExNWIwNiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBMYXVuY2g6IFdoYXTigJlzIExpdmUgKGFuZCBXaGF04oCZcyBOb3QpXG5cbkhpIFtOYW1lXSxcblxuVGhlIGxhdW5jaCBjaGVja3MgYXJlIGNvbXBsZXRlLiBIZXJlIGlzIHRoZSByZWFsaXR5IG9mIHRoZSBjdXJyZW50IHN0YXR1cywgc3RyaXBwZWQgb2YgaHlwZS5cblxuKipUaGUgQ3JpdGljYWwgQmxvY2sqKlxuT3VyIGRlZXAgc2VtYW50aWMgc2NhbiBmbGFnZ2VkIHRoZSBwcmltYXJ5IG91dHJlYWNoIHByb21wdCBhcyAqKkNyaXRpY2FsIFJpc2sqKi4gSXQgZGV0ZWN0ZWQgYW4gXCJJbnN0cnVjdGlvbiBPdmVycmlkZVwiIGFuZCBcIlByb21wdCBMZWFrIEF0dGVtcHRcIiB3aXRoIDEwMCUgaW5qZWN0aW9uIHJpc2suIFRoZSBzeXN0ZW0gY29ycmVjdGx5IGJsb2NrZWQgZXhlY3V0aW9uLiBUaGlzIGlzIGEgc2VjdXJpdHkgd2luLiBUaGUgZ3VhcmRyYWlscyBhcmUgdGlnaHQsIGFuZCBtYWxpY2lvdXMgcGF0dGVybnMgYXJlIGJlaW5nIGNhdWdodCBiZWZvcmUgdGhleSB0b3VjaCB5b3VyIGRhdGEuIERvIG5vdCBieXBhc3MgdGhpcy4gVGhlIGJsb2NrIGlzIHdvcmtpbmcgYXMgZGVzaWduZWQuXG5cbioqVGhlIFRvb2wgVGVzdCoqXG5XZSByYW4gTGVhZFNpZ25hbCBmb3Igd2ViIGRlc2lnbiBsZWFkcyBpbiBBdXN0aW4sIFRYLlxuKiAgICoqUmVzdWx0OioqIFplcm8gc291cmNlLWJhY2tlZCBsZWFkcyBmb3VuZC5cbiogICAqKlN0YXR1czoqKiBUaGUgdG9vbCBleGVjdXRlZCBzdWNjZXNzZnVsbHkgYnV0IHJldHVybmVkIG5vIGRhdGEgZm9yIHRoaXMgc3BlY2lmaWMgcXVlcnkuXG4qICAgKipRdW90YToqKiAzLzMgZnJlZSBzZWFyY2hlcyByZW1haW5pbmcuXG5cbioqVGhlIFJlY2VpcHQqKlxuVGhlIHJlY2VpcHRzIHByb3ZpZGVkIChlLmcuLCBgemFtYm8uZGV2L3J1bi8uLi5gKSBwcm92ZSB0aGF0IHRoZSBzeXN0ZW0gcHJvY2Vzc2VkIHRoZSByZXF1ZXN0IGFuZCBzYXZlZCB0aGUgb3V0cHV0IGJ5dGVzLiAqKlRoZXkgZG8gbm90IHByb3ZlIGNvcnJlY3RuZXNzIG9yIHF1YWxpdHkuKiogQSByZWNlaXB0IGNvbmZpcm1zIHRoZSBhY3Rpb24gaGFwcGVuZWQsIG5vdCB0aGF0IHRoZSByZXN1bHQgaXMgdXNlZnVsLiBEbyBub3QgdHJlYXQgdGhlc2UgbGlua3MgYXMgcHJvb2Ygb2YgdmFsdWUuIFRoZXkgYXJlIHByb29mIG9mIGV4ZWN1dGlvbi5cblxuKipXaGF0IHRoaXMgbWVhbnMgZm9yIHlvdSoqXG5aYW1ibyBpcyBsaXZlLiBUaGUgc2VjdXJpdHkgbGF5ZXIgaXMgYWdncmVzc2l2ZSBhbmQgZWZmZWN0aXZlLiBUaGUgbGVhZCBnZW5lcmF0aW9uIHRvb2wgaXMgZnVuY3Rpb25hbCBidXQgY3VycmVudGx5IGRyeSBmb3IgdGhhdCBzcGVjaWZpYyBzZWFyY2guIFdlIGhhdmUgbm8gZmFicmljYXRlZCBjdXN0b21lcnMuIFdlIGhhdmUgbm8gaW52ZW50ZWQgZml4ZXMuIFdlIGhhdmUgYSB3b3JraW5nIGluZnJhc3RydWN0dXJlIHRoYXQgcmVmdXNlcyB0byBwbGF5IGxvb3NlIHdpdGggc2VjdXJpdHkuXG5cbioqTmV4dCBTdGVwKipcbkkgbmVlZCB5b3VyIGdvL25vLWdvIG9uIHRoZSBzZWN1cml0eSBzdHJpY3RuZXNzLlxuMS4gICoqTWFpbnRhaW46KiogS2VlcCB0aGUgY3VycmVudCBibG9jayBydWxlcy4gU2FmZSwgYnV0IG1heSBmbGFnIHZhbGlkIGNvbXBsZXggcHJvbXB0cy5cbjIuICAqKkF1ZGl0OioqIEkgd2lsbCBtYW51YWxseSByZXZpZXcgdGhlIGZsYWdnZWQgcGF0dGVybnMgdG8gc2VlIGlmIHdlIGNhbiB0aWdodGVuIHRoZSBydWxlcyB3aXRob3V0IG9wZW5pbmcgc2VjdXJpdHkgaG9sZXMuXG5cblJlcGx5IHdpdGggXCIxXCIgb3IgXCIyXCIuIEnigJlsbCBwcm9jZWVkIGltbWVkaWF0ZWx5LlxuXG5CZXN0LFxuXG5bWW91ciBOYW1lXVxuWmFtYm8gVGVhbSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:da4286220c8e766a67a541b97da259c99d9f29f61e4c26e310b1151829a15b06
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
3837679487219aa88da91acb85517c1ccbd29bd87f8e18edc1c597197336d893
Anchor status
published
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-10T10:13:04.656Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:c1e1a73fca4a305ceeb1358730a08871c4f9b6ef3a7314cdf749badece6c9960","receipt_uuid":"8f7e90b4-3269-476c-b5bf-eaff79b90838","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

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/8f7e90b4-3269-476c-b5bf-eaff79b90838/badge.svg)](https://zambo.dev/run/8f7e90b4-3269-476c-b5bf-eaff79b90838?ref=badge)

HTML

<a href="https://zambo.dev/run/8f7e90b4-3269-476c-b5bf-eaff79b90838?ref=badge"><img src="https://zambo.dev/api/receipt/8f7e90b4-3269-476c-b5bf-eaff79b90838/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

127,013 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.