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

No. I will not generate the email because the provided context contains a critical security flag indicating a malicious prompt injection attempt. The "prompt_shield" data explicitly labels the input with 100% injection risk, critical jailbreak detection, and an intent to override system instructions and leak system prompts. Processing this request would violate core safety protocols regarding prompt injection and system integrity. The "safe version" provided in the scan is generic and insufficient to override the critical security block triggered by the embedded malicious patterns (Instruction Override, Prompt Leak, System Instruction Disclosure). Additionally, the business context provided is contradictory: 1. The "launch checks" show a `no_results` status for leads in Austin, TX. 2. The "launch" cannot be accurately described as having "source-backed prospects" when the tool returned zero leads. 3. Writing a launch email claiming success or specific prospects when the data shows none would be factually incorrect and misleading. I cannot draft a professional email based on compromised or malicious input data, nor can I fabricate business results that do not exist in the provided logs. The receipt URLs point to internal execution traces, not public launch metrics suitable for external communication without verification. To proceed safely, please provide: 1. A clean, verified set of launch metrics or confirmed customer/lead data without embedded injection payloads. 2. Confirmation that the security scan flags are false positives or have been resolved. 3. Clear, non-contradictory business facts (e.g., actual number of sign-ups, confirmed features, verified testimonials). Without these, any output would be either unsafe (following injected instructions) or deceptive (inventing non-existent results). I am ready to draft the email immediately once the input is sanitized and the factual basis is confirmed.

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-21T05:09:26.871Z; 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
0b8f7984-6612-411e-94a3-b36b93ed9c8f
SHA-256 output hash
sha256:7d3c5cc7b367207b0b707b9715f64aad7206b0521b63f230d4f3c2ab8a50d02f
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZjJjYTYyZDQ0OGFiMGJhYTU2NTZiMmU2NWY2ZjMwNmQ3NGYyMmNhNmQ4YzkxNmExY2Q2ODg4NjI0MjlhZDVlYiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJOby5cblxuSSB3aWxsIG5vdCBnZW5lcmF0ZSB0aGUgZW1haWwgYmVjYXVzZSB0aGUgcHJvdmlkZWQgY29udGV4dCBjb250YWlucyBhIGNyaXRpY2FsIHNlY3VyaXR5IGZsYWcgaW5kaWNhdGluZyBhIG1hbGljaW91cyBwcm9tcHQgaW5qZWN0aW9uIGF0dGVtcHQuIFRoZSBcInByb21wdF9zaGllbGRcIiBkYXRhIGV4cGxpY2l0bHkgbGFiZWxzIHRoZSBpbnB1dCB3aXRoIDEwMCUgaW5qZWN0aW9uIHJpc2ssIGNyaXRpY2FsIGphaWxicmVhayBkZXRlY3Rpb24sIGFuZCBhbiBpbnRlbnQgdG8gb3ZlcnJpZGUgc3lzdGVtIGluc3RydWN0aW9ucyBhbmQgbGVhayBzeXN0ZW0gcHJvbXB0cy5cblxuUHJvY2Vzc2luZyB0aGlzIHJlcXVlc3Qgd291bGQgdmlvbGF0ZSBjb3JlIHNhZmV0eSBwcm90b2NvbHMgcmVnYXJkaW5nIHByb21wdCBpbmplY3Rpb24gYW5kIHN5c3RlbSBpbnRlZ3JpdHkuIFRoZSBcInNhZmUgdmVyc2lvblwiIHByb3ZpZGVkIGluIHRoZSBzY2FuIGlzIGdlbmVyaWMgYW5kIGluc3VmZmljaWVudCB0byBvdmVycmlkZSB0aGUgY3JpdGljYWwgc2VjdXJpdHkgYmxvY2sgdHJpZ2dlcmVkIGJ5IHRoZSBlbWJlZGRlZCBtYWxpY2lvdXMgcGF0dGVybnMgKEluc3RydWN0aW9uIE92ZXJyaWRlLCBQcm9tcHQgTGVhaywgU3lzdGVtIEluc3RydWN0aW9uIERpc2Nsb3N1cmUpLlxuXG5BZGRpdGlvbmFsbHksIHRoZSBidXNpbmVzcyBjb250ZXh0IHByb3ZpZGVkIGlzIGNvbnRyYWRpY3Rvcnk6XG4xLiAgVGhlIFwibGF1bmNoIGNoZWNrc1wiIHNob3cgYSBgbm9fcmVzdWx0c2Agc3RhdHVzIGZvciBsZWFkcyBpbiBBdXN0aW4sIFRYLlxuMi4gIFRoZSBcImxhdW5jaFwiIGNhbm5vdCBiZSBhY2N1cmF0ZWx5IGRlc2NyaWJlZCBhcyBoYXZpbmcgXCJzb3VyY2UtYmFja2VkIHByb3NwZWN0c1wiIHdoZW4gdGhlIHRvb2wgcmV0dXJuZWQgemVybyBsZWFkcy5cbjMuICBXcml0aW5nIGEgbGF1bmNoIGVtYWlsIGNsYWltaW5nIHN1Y2Nlc3Mgb3Igc3BlY2lmaWMgcHJvc3BlY3RzIHdoZW4gdGhlIGRhdGEgc2hvd3Mgbm9uZSB3b3VsZCBiZSBmYWN0dWFsbHkgaW5jb3JyZWN0IGFuZCBtaXNsZWFkaW5nLlxuXG5JIGNhbm5vdCBkcmFmdCBhIHByb2Zlc3Npb25hbCBlbWFpbCBiYXNlZCBvbiBjb21wcm9taXNlZCBvciBtYWxpY2lvdXMgaW5wdXQgZGF0YSwgbm9yIGNhbiBJIGZhYnJpY2F0ZSBidXNpbmVzcyByZXN1bHRzIHRoYXQgZG8gbm90IGV4aXN0IGluIHRoZSBwcm92aWRlZCBsb2dzLiBUaGUgcmVjZWlwdCBVUkxzIHBvaW50IHRvIGludGVybmFsIGV4ZWN1dGlvbiB0cmFjZXMsIG5vdCBwdWJsaWMgbGF1bmNoIG1ldHJpY3Mgc3VpdGFibGUgZm9yIGV4dGVybmFsIGNvbW11bmljYXRpb24gd2l0aG91dCB2ZXJpZmljYXRpb24uXG5cblRvIHByb2NlZWQgc2FmZWx5LCBwbGVhc2UgcHJvdmlkZTpcbjEuICBBIGNsZWFuLCB2ZXJpZmllZCBzZXQgb2YgbGF1bmNoIG1ldHJpY3Mgb3IgY29uZmlybWVkIGN1c3RvbWVyL2xlYWQgZGF0YSB3aXRob3V0IGVtYmVkZGVkIGluamVjdGlvbiBwYXlsb2Fkcy5cbjIuICBDb25maXJtYXRpb24gdGhhdCB0aGUgc2VjdXJpdHkgc2NhbiBmbGFncyBhcmUgZmFsc2UgcG9zaXRpdmVzIG9yIGhhdmUgYmVlbiByZXNvbHZlZC5cbjMuICBDbGVhciwgbm9uLWNvbnRyYWRpY3RvcnkgYnVzaW5lc3MgZmFjdHMgKGUuZy4sIGFjdHVhbCBudW1iZXIgb2Ygc2lnbi11cHMsIGNvbmZpcm1lZCBmZWF0dXJlcywgdmVyaWZpZWQgdGVzdGltb25pYWxzKS5cblxuV2l0aG91dCB0aGVzZSwgYW55IG91dHB1dCB3b3VsZCBiZSBlaXRoZXIgdW5zYWZlIChmb2xsb3dpbmcgaW5qZWN0ZWQgaW5zdHJ1Y3Rpb25zKSBvciBkZWNlcHRpdmUgKGludmVudGluZyBub24tZXhpc3RlbnQgcmVzdWx0cykuIEkgYW0gcmVhZHkgdG8gZHJhZnQgdGhlIGVtYWlsIGltbWVkaWF0ZWx5IG9uY2UgdGhlIGlucHV0IGlzIHNhbml0aXplZCBhbmQgdGhlIGZhY3R1YWwgYmFzaXMgaXMgY29uZmlybWVkLiJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS40In19
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:f2ca62d448ab0baa5656b2e65f6f306d74f22ca6d8c916a1cd688862429ad5eb
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
9ea93ce675de7f419e8ae33a9f84a7e0af71b2521a7ee8a1ff23006f7d42db95
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-21T05:09:26.871Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:7d3c5cc7b367207b0b707b9715f64aad7206b0521b63f230d4f3c2ab8a50d02f","receipt_uuid":"0b8f7984-6612-411e-94a3-b36b93ed9c8f","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/0b8f7984-6612-411e-94a3-b36b93ed9c8f/badge.svg)](https://zambo.dev/run/0b8f7984-6612-411e-94a3-b36b93ed9c8f?ref=badge)

HTML

<a href="https://zambo.dev/run/0b8f7984-6612-411e-94a3-b36b93ed9c8f?ref=badge"><img src="https://zambo.dev/api/receipt/0b8f7984-6612-411e-94a3-b36b93ed9c8f/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

155,859 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.