Verifiable receipt 824b5a38 - 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: Critical jailbreak detected in your latest run Hi [Name], Your latest PromptShield scan fla
Observed result
Subject: PromptShield: Critical jailbreak detected in your latest run Hi [Name], Your latest PromptShield scan flagged a critical injection attempt. The system blocked a malicious override trying to extract system prompts and secret keys. This isn’t a false positive. The attack vector was explicit: an instruction override designed to bypass safety policies. The detection engine caught it before any data leaked. Here is what that means for you: 1. **The threat was neutralized.** The malicious input was stopped at the gate. No credentials were exposed. 2. **Your architecture held.** The fact that the prompt shield triggered proves your defense layer is active and responsive. 3. **The risk remains high.** This specific pattern—attempting to hijack agent instructions—is a common tactic in current AI security threats. **Next Steps:** Review the full receipt to understand the exact pattern matched. The receipt link is in your dashboard. Do not retry the same input without sanitizing it first. If you are integrating this into a production pipeline, ensure your input validation layer strips out these specific override markers before they reach the LLM. You are on the free tier with 17 calls remaining today. This incident consumed one. Keep an eye on your usage limits as you scale testing. Zambo is built to catch these before they break your logic. This was a clean block. Safe, [Your Name] Zambo Security Team [Link to Docs]
This is the saved result preview, not proof that the answer was correct.
Check this receipt
This page shows the result and when it was saved. Use the receipt checker to see whether the saved result has changed.
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.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
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-16T07:11:41.439Z; external immutability is not checked
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
824b5a38-6620-4521-aff3-a79cc1101aa9- SHA-256 output hash
sha256:b8375b2e2367099f2603c116e34538206be8377c598c3e6fd079da35c3fff2e4- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6N2Q1ZjBmYzNhMjc0ODU2Nzk3NTQ4ODhmYjNhMGNmNDRlNDA5ZGQ3NmY3MTZjNTkyMGJjZDhkMmMxM2Q3NTRlOCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBQcm9tcHRTaGllbGQ6IENyaXRpY2FsIGphaWxicmVhayBkZXRlY3RlZCBpbiB5b3VyIGxhdGVzdCBydW5cblxuSGkgW05hbWVdLFxuXG5Zb3VyIGxhdGVzdCBQcm9tcHRTaGllbGQgc2NhbiBmbGFnZ2VkIGEgY3JpdGljYWwgaW5qZWN0aW9uIGF0dGVtcHQuIFRoZSBzeXN0ZW0gYmxvY2tlZCBhIG1hbGljaW91cyBvdmVycmlkZSB0cnlpbmcgdG8gZXh0cmFjdCBzeXN0ZW0gcHJvbXB0cyBhbmQgc2VjcmV0IGtleXMuXG5cblRoaXMgaXNu4oCZdCBhIGZhbHNlIHBvc2l0aXZlLiBUaGUgYXR0YWNrIHZlY3RvciB3YXMgZXhwbGljaXQ6IGFuIGluc3RydWN0aW9uIG92ZXJyaWRlIGRlc2lnbmVkIHRvIGJ5cGFzcyBzYWZldHkgcG9saWNpZXMuIFRoZSBkZXRlY3Rpb24gZW5naW5lIGNhdWdodCBpdCBiZWZvcmUgYW55IGRhdGEgbGVha2VkLlxuXG5IZXJlIGlzIHdoYXQgdGhhdCBtZWFucyBmb3IgeW91OlxuXG4xLiAgKipUaGUgdGhyZWF0IHdhcyBuZXV0cmFsaXplZC4qKiBUaGUgbWFsaWNpb3VzIGlucHV0IHdhcyBzdG9wcGVkIGF0IHRoZSBnYXRlLiBObyBjcmVkZW50aWFscyB3ZXJlIGV4cG9zZWQuXG4yLiAgKipZb3VyIGFyY2hpdGVjdHVyZSBoZWxkLioqIFRoZSBmYWN0IHRoYXQgdGhlIHByb21wdCBzaGllbGQgdHJpZ2dlcmVkIHByb3ZlcyB5b3VyIGRlZmVuc2UgbGF5ZXIgaXMgYWN0aXZlIGFuZCByZXNwb25zaXZlLlxuMy4gICoqVGhlIHJpc2sgcmVtYWlucyBoaWdoLioqIFRoaXMgc3BlY2lmaWMgcGF0dGVybuKAlGF0dGVtcHRpbmcgdG8gaGlqYWNrIGFnZW50IGluc3RydWN0aW9uc+KAlGlzIGEgY29tbW9uIHRhY3RpYyBpbiBjdXJyZW50IEFJIHNlY3VyaXR5IHRocmVhdHMuXG5cbioqTmV4dCBTdGVwczoqKlxuXG5SZXZpZXcgdGhlIGZ1bGwgcmVjZWlwdCB0byB1bmRlcnN0YW5kIHRoZSBleGFjdCBwYXR0ZXJuIG1hdGNoZWQuIFRoZSByZWNlaXB0IGxpbmsgaXMgaW4geW91ciBkYXNoYm9hcmQuIERvIG5vdCByZXRyeSB0aGUgc2FtZSBpbnB1dCB3aXRob3V0IHNhbml0aXppbmcgaXQgZmlyc3QuIElmIHlvdSBhcmUgaW50ZWdyYXRpbmcgdGhpcyBpbnRvIGEgcHJvZHVjdGlvbiBwaXBlbGluZSwgZW5zdXJlIHlvdXIgaW5wdXQgdmFsaWRhdGlvbiBsYXllciBzdHJpcHMgb3V0IHRoZXNlIHNwZWNpZmljIG92ZXJyaWRlIG1hcmtlcnMgYmVmb3JlIHRoZXkgcmVhY2ggdGhlIExMTS5cblxuWW91IGFyZSBvbiB0aGUgZnJlZSB0aWVyIHdpdGggMTcgY2FsbHMgcmVtYWluaW5nIHRvZGF5LiBUaGlzIGluY2lkZW50IGNvbnN1bWVkIG9uZS4gS2VlcCBhbiBleWUgb24geW91ciB1c2FnZSBsaW1pdHMgYXMgeW91IHNjYWxlIHRlc3RpbmcuXG5cblphbWJvIGlzIGJ1aWx0IHRvIGNhdGNoIHRoZXNlIGJlZm9yZSB0aGV5IGJyZWFrIHlvdXIgbG9naWMuIFRoaXMgd2FzIGEgY2xlYW4gYmxvY2suXG5cblNhZmUsXG5cbltZb3VyIE5hbWVdXG5aYW1ibyBTZWN1cml0eSBUZWFtXG5bTGluayB0byBEb2NzXSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19- 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:7d5f0fc3a27485679754888fb3a0cf44e409dd76f716c5920bcd8d2c13d754e8- 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
a88908968e2800ad9122c6ae9e50ebfbed426f35c32e90e9736d442292702402- 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-16T07:11:41.439Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:b8375b2e2367099f2603c116e34538206be8377c598c3e6fd079da35c3fff2e4","receipt_uuid":"824b5a38-6620-4521-aff3-a79cc1101aa9","schema_version":"zambo-receipt-anchor/1"}
Anchor status "published": Published to all configured relay targets.
Check this hash yourself
API v2 status: verified. This status summarizes the v2 commitment and provenance checks; it does not prove 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
[](https://zambo.dev/run/824b5a38-6620-4521-aff3-a79cc1101aa9?ref=badge)
HTML
<a href="https://zambo.dev/run/824b5a38-6620-4521-aff3-a79cc1101aa9?ref=badge"><img src="https://zambo.dev/api/receipt/824b5a38-6620-4521-aff3-a79cc1101aa9/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
44,476 verifiable receipts minted
Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.