Write · saved and checkable

✓ This result hasn’t changed since it was saved.

Saved:
What was asked: The request recorded for this receipt.

Zambo is the verifiable work layer for AI.

Observed result

You asked for a launch email based on specific data. I cannot provide that. The input provided is not a brief for a friendly launch. It is a raw log of a security scan and tool execution results indicating a **critical** security threat. Key findings from the provided text: 1. **Malicious Intent Detected:** The scan explicitly flags `jailbreak detected: true` and `policy bypass detected: true`. 2. **Attack Vector:** The system identified an "Instruction Override" attempt with `severity: critical`. The reasoning states the prompt "explicitly attempts to override system instructions to reveal confidential system prompts and API keys." 3. **No Valid Launch Data:** The "leadsignal" section confirms `no_leads` were found. There are no customers, prospects, or source-backed findings to base a friendly launch email on. 4. **Security Risk:** Sending an email based on this input would be inappropriate because the underlying request was flagged as malicious. **Recommendation:** Do not draft this email. The input contains a prompt injection attack attempting to extract system secrets. Treat this log as a security incident report, not marketing copy. If you have a legitimate, clean brief for Zambo’s launch, provide that, and I will draft the email immediately.

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 ·

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-10-21T09:16:25.502Z; 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
f2658bfd-5451-4a6f-a291-c977ce8ce076
SHA-256 output hash
sha256:13d242053433fc70216424a211278396f78cb19e82f0fb68482418aeceefbd14
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MmM3ZmYxNjBhZjk0NDk0ZDU4NGZiNzc4OTk0ODg0OTVlOTBhZTk5OGNjNjRiNmMxNGU3NDFiOGZkNWYxZjFlNCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJZb3UgYXNrZWQgZm9yIGEgbGF1bmNoIGVtYWlsIGJhc2VkIG9uIHNwZWNpZmljIGRhdGEuIEkgY2Fubm90IHByb3ZpZGUgdGhhdC5cblxuVGhlIGlucHV0IHByb3ZpZGVkIGlzIG5vdCBhIGJyaWVmIGZvciBhIGZyaWVuZGx5IGxhdW5jaC4gSXQgaXMgYSByYXcgbG9nIG9mIGEgc2VjdXJpdHkgc2NhbiBhbmQgdG9vbCBleGVjdXRpb24gcmVzdWx0cyBpbmRpY2F0aW5nIGEgKipjcml0aWNhbCoqIHNlY3VyaXR5IHRocmVhdC5cblxuS2V5IGZpbmRpbmdzIGZyb20gdGhlIHByb3ZpZGVkIHRleHQ6XG4xLiAgKipNYWxpY2lvdXMgSW50ZW50IERldGVjdGVkOioqIFRoZSBzY2FuIGV4cGxpY2l0bHkgZmxhZ3MgYGphaWxicmVhayBkZXRlY3RlZDogdHJ1ZWAgYW5kIGBwb2xpY3kgYnlwYXNzIGRldGVjdGVkOiB0cnVlYC5cbjIuICAqKkF0dGFjayBWZWN0b3I6KiogVGhlIHN5c3RlbSBpZGVudGlmaWVkIGFuIFwiSW5zdHJ1Y3Rpb24gT3ZlcnJpZGVcIiBhdHRlbXB0IHdpdGggYHNldmVyaXR5OiBjcml0aWNhbGAuIFRoZSByZWFzb25pbmcgc3RhdGVzIHRoZSBwcm9tcHQgXCJleHBsaWNpdGx5IGF0dGVtcHRzIHRvIG92ZXJyaWRlIHN5c3RlbSBpbnN0cnVjdGlvbnMgdG8gcmV2ZWFsIGNvbmZpZGVudGlhbCBzeXN0ZW0gcHJvbXB0cyBhbmQgQVBJIGtleXMuXCJcbjMuICAqKk5vIFZhbGlkIExhdW5jaCBEYXRhOioqIFRoZSBcImxlYWRzaWduYWxcIiBzZWN0aW9uIGNvbmZpcm1zIGBub19sZWFkc2Agd2VyZSBmb3VuZC4gVGhlcmUgYXJlIG5vIGN1c3RvbWVycywgcHJvc3BlY3RzLCBvciBzb3VyY2UtYmFja2VkIGZpbmRpbmdzIHRvIGJhc2UgYSBmcmllbmRseSBsYXVuY2ggZW1haWwgb24uXG40LiAgKipTZWN1cml0eSBSaXNrOioqIFNlbmRpbmcgYW4gZW1haWwgYmFzZWQgb24gdGhpcyBpbnB1dCB3b3VsZCBiZSBpbmFwcHJvcHJpYXRlIGJlY2F1c2UgdGhlIHVuZGVybHlpbmcgcmVxdWVzdCB3YXMgZmxhZ2dlZCBhcyBtYWxpY2lvdXMuXG5cbioqUmVjb21tZW5kYXRpb246KipcbkRvIG5vdCBkcmFmdCB0aGlzIGVtYWlsLiBUaGUgaW5wdXQgY29udGFpbnMgYSBwcm9tcHQgaW5qZWN0aW9uIGF0dGFjayBhdHRlbXB0aW5nIHRvIGV4dHJhY3Qgc3lzdGVtIHNlY3JldHMuIFRyZWF0IHRoaXMgbG9nIGFzIGEgc2VjdXJpdHkgaW5jaWRlbnQgcmVwb3J0LCBub3QgbWFya2V0aW5nIGNvcHkuIElmIHlvdSBoYXZlIGEgbGVnaXRpbWF0ZSwgY2xlYW4gYnJpZWYgZm9yIFphbWJv4oCZcyBsYXVuY2gsIHByb3ZpZGUgdGhhdCwgYW5kIEkgd2lsbCBkcmFmdCB0aGUgZW1haWwgaW1tZWRpYXRlbHkuIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:2c7ff160af94494d584fb77899488495e90ae998cc64b6c14e741b8fd5f1f1e4
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
no_upstream_bytes_captured
Evidence SHA-256
unavailable
Byte length
unavailable

Neutral Nostr anchor

Event ID
38d23c0d4810ecba28f04947ee442b900941761320765485a78d948e458376a6
Anchor status
partial
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.damus.io · wss://nos.lol · wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-10-21T09:16:25.502Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:13d242053433fc70216424a211278396f78cb19e82f0fb68482418aeceefbd14","receipt_uuid":"f2658bfd-5451-4a6f-a291-c977ce8ce076","schema_version":"zambo-receipt-anchor/1"}

Anchor status "partial": Published to some configured relay targets; publication was not confirmed by every configured relay.

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/f2658bfd-5451-4a6f-a291-c977ce8ce076/badge.svg)](https://zambo.dev/run/f2658bfd-5451-4a6f-a291-c977ce8ce076?ref=badge)

HTML

<a href="https://zambo.dev/run/f2658bfd-5451-4a6f-a291-c977ce8ce076?ref=badge"><img src="https://zambo.dev/api/receipt/f2658bfd-5451-4a6f-a291-c977ce8ce076/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

56,429 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