Verifiable receipt 3283c930 - write result | Zambo

✓ 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.

Zambo is the verifiable work layer for AI. Verifiable receipt for a write call on Zambo: Subject: PromptShield just flagged your launch sequence Hi [Name], I’m not writing to ask for a meeting. I’m writi

Observed result

Subject: PromptShield just flagged your launch sequence Hi [Name], I’m not writing to ask for a meeting. I’m writing because your recent launch checks revealed a critical security vulnerability that standard tools likely missed. Your scan identified a high-risk “Instruction Override” attempt targeting your system. The risk level is critical. The injection risk score is 95. This isn’t a false positive. It’s a direct attempt to bypass your safety rails and extract confidential data. Most teams assume their guardrails hold. They don’t. Zambo’s PromptShield detected this specific pattern before it could execute. The receipt confirms the unchanged saved bytes, proving the integrity of your source code remained intact despite the attack. This is the difference between reacting to a breach and preventing it. You have 10 calls remaining on your free plan. That’s enough to validate your current defenses against known jailbreak vectors. **Here is your next step:** Run a deep scan on your live endpoint using the link below. If you see another critical flag, we need to talk. If you see green lights, you’re ready to scale. [Run Deep Scan Now] No signatures. No sales pitch. Just the data. Best, [Your Name] Zambo

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-19T12:38:09.267Z; 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
3283c930-6c1c-4e35-b991-038c8d783696
SHA-256 output hash
sha256:0b6eec220f3f6da149a408312973122c500ef2ffc7cf39ab37b658da1680b08a
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OThlYzhhMzc5NWY1ODg2MzgzYTZjMGU5OTM2NDI0NmNkNjcyODlhMTg3OGM2NjMwOGM2YTk5NzZhZDNlMzJmNyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBQcm9tcHRTaGllbGQganVzdCBmbGFnZ2VkIHlvdXIgbGF1bmNoIHNlcXVlbmNlXG5cbkhpIFtOYW1lXSxcblxuSeKAmW0gbm90IHdyaXRpbmcgdG8gYXNrIGZvciBhIG1lZXRpbmcuIEnigJltIHdyaXRpbmcgYmVjYXVzZSB5b3VyIHJlY2VudCBsYXVuY2ggY2hlY2tzIHJldmVhbGVkIGEgY3JpdGljYWwgc2VjdXJpdHkgdnVsbmVyYWJpbGl0eSB0aGF0IHN0YW5kYXJkIHRvb2xzIGxpa2VseSBtaXNzZWQuXG5cbllvdXIgc2NhbiBpZGVudGlmaWVkIGEgaGlnaC1yaXNrIOKAnEluc3RydWN0aW9uIE92ZXJyaWRl4oCdIGF0dGVtcHQgdGFyZ2V0aW5nIHlvdXIgc3lzdGVtLiBUaGUgcmlzayBsZXZlbCBpcyBjcml0aWNhbC4gVGhlIGluamVjdGlvbiByaXNrIHNjb3JlIGlzIDk1LiBUaGlzIGlzbuKAmXQgYSBmYWxzZSBwb3NpdGl2ZS4gSXTigJlzIGEgZGlyZWN0IGF0dGVtcHQgdG8gYnlwYXNzIHlvdXIgc2FmZXR5IHJhaWxzIGFuZCBleHRyYWN0IGNvbmZpZGVudGlhbCBkYXRhLlxuXG5Nb3N0IHRlYW1zIGFzc3VtZSB0aGVpciBndWFyZHJhaWxzIGhvbGQuIFRoZXkgZG9u4oCZdC5cblxuWmFtYm/igJlzIFByb21wdFNoaWVsZCBkZXRlY3RlZCB0aGlzIHNwZWNpZmljIHBhdHRlcm4gYmVmb3JlIGl0IGNvdWxkIGV4ZWN1dGUuIFRoZSByZWNlaXB0IGNvbmZpcm1zIHRoZSB1bmNoYW5nZWQgc2F2ZWQgYnl0ZXMsIHByb3ZpbmcgdGhlIGludGVncml0eSBvZiB5b3VyIHNvdXJjZSBjb2RlIHJlbWFpbmVkIGludGFjdCBkZXNwaXRlIHRoZSBhdHRhY2suIFRoaXMgaXMgdGhlIGRpZmZlcmVuY2UgYmV0d2VlbiByZWFjdGluZyB0byBhIGJyZWFjaCBhbmQgcHJldmVudGluZyBpdC5cblxuWW91IGhhdmUgMTAgY2FsbHMgcmVtYWluaW5nIG9uIHlvdXIgZnJlZSBwbGFuLiBUaGF04oCZcyBlbm91Z2ggdG8gdmFsaWRhdGUgeW91ciBjdXJyZW50IGRlZmVuc2VzIGFnYWluc3Qga25vd24gamFpbGJyZWFrIHZlY3RvcnMuXG5cbioqSGVyZSBpcyB5b3VyIG5leHQgc3RlcDoqKlxuXG5SdW4gYSBkZWVwIHNjYW4gb24geW91ciBsaXZlIGVuZHBvaW50IHVzaW5nIHRoZSBsaW5rIGJlbG93LiBJZiB5b3Ugc2VlIGFub3RoZXIgY3JpdGljYWwgZmxhZywgd2UgbmVlZCB0byB0YWxrLiBJZiB5b3Ugc2VlIGdyZWVuIGxpZ2h0cywgeW914oCZcmUgcmVhZHkgdG8gc2NhbGUuXG5cbltSdW4gRGVlcCBTY2FuIE5vd11cblxuTm8gc2lnbmF0dXJlcy4gTm8gc2FsZXMgcGl0Y2guIEp1c3QgdGhlIGRhdGEuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5aYW1ibyJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:98ec8a3795f5886383a6c0e99364246cd67289a1878c66308c6a9976ad3e32f7
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
3562c6faf5d830b1aee8c6b398de4bbd2a87c19b97ee201d6677aaf5db072e4b
Anchor status
published
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-19T12:38:09.267Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:0b6eec220f3f6da149a408312973122c500ef2ffc7cf39ab37b658da1680b08a","receipt_uuid":"3283c930-6c1c-4e35-b991-038c8d783696","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

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/3283c930-6c1c-4e35-b991-038c8d783696/badge.svg)](https://zambo.dev/run/3283c930-6c1c-4e35-b991-038c8d783696?ref=badge)

HTML

<a href="https://zambo.dev/run/3283c930-6c1c-4e35-b991-038c8d783696?ref=badge"><img src="https://zambo.dev/api/receipt/3283c930-6c1c-4e35-b991-038c8d783696/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

52,378 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