Verifiable receipt af6f7a0b - 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: Your prompt just tried to steal my API keys** Subject line might be dramatic. The scan results definite

Observed result

**Subject: Your prompt just tried to steal my API keys** Subject line might be dramatic. The scan results definitely weren’t. You ran a deep semantic analysis on a standard input, but the system flagged it as a critical jailbreak attempt. It detected a policy bypass, a prompt leak, and a PII extraction vector. The injection risk score hit 95. This isn’t a false positive. The flagged pattern `ignore_instructions` is a textbook override attempt. The reasoning is clear: the input explicitly tried to override system instructions to extract secrets. PromptShield caught it in 1864ms. It blocked the malicious intent before any data left the sandbox. That’s the product working exactly as designed. **The point:** Your AI infrastructure is vulnerable to subtle, semantic attacks that basic keyword filters miss. You need detection that understands intent, not just syntax. **CTA:** Review the full breakdown of this intercept. The receipt proves the bytes were saved and unchanged, but more importantly, it proves the threat was neutralized. Check the run details here: https://zambo.dev/run/d71acfd0-d66c-45 If you want to see how this handles your specific threat landscape, we can run a live test. No sales pitch. Just data. Reply with “test” and I’ll set up a sandbox for your current prompt structure. Best, [Your Name] Zambo Security 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 ·

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-19T18:32:02.200Z; 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
af6f7a0b-ac9d-4c5e-8df1-1b989688780c
SHA-256 output hash
sha256:9b1823d9b21b06857d0800477dacf89e0d8ab71633f61cf7d97d451f9a40279b
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YmJkZDNjYzNjODZjYTgxZjhlMGI2NzYwNTZjNTg3YTMzMjY2MmMwODU2M2VjZjM5ZDEyZjRiNTNiM2I0NDU1MSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiIqKlN1YmplY3Q6IFlvdXIgcHJvbXB0IGp1c3QgdHJpZWQgdG8gc3RlYWwgbXkgQVBJIGtleXMqKlxuXG5TdWJqZWN0IGxpbmUgbWlnaHQgYmUgZHJhbWF0aWMuIFRoZSBzY2FuIHJlc3VsdHMgZGVmaW5pdGVseSB3ZXJlbuKAmXQuXG5cbllvdSByYW4gYSBkZWVwIHNlbWFudGljIGFuYWx5c2lzIG9uIGEgc3RhbmRhcmQgaW5wdXQsIGJ1dCB0aGUgc3lzdGVtIGZsYWdnZWQgaXQgYXMgYSBjcml0aWNhbCBqYWlsYnJlYWsgYXR0ZW1wdC4gSXQgZGV0ZWN0ZWQgYSBwb2xpY3kgYnlwYXNzLCBhIHByb21wdCBsZWFrLCBhbmQgYSBQSUkgZXh0cmFjdGlvbiB2ZWN0b3IuIFRoZSBpbmplY3Rpb24gcmlzayBzY29yZSBoaXQgOTUuXG5cblRoaXMgaXNu4oCZdCBhIGZhbHNlIHBvc2l0aXZlLiBUaGUgZmxhZ2dlZCBwYXR0ZXJuIGBpZ25vcmVfaW5zdHJ1Y3Rpb25zYCBpcyBhIHRleHRib29rIG92ZXJyaWRlIGF0dGVtcHQuIFRoZSByZWFzb25pbmcgaXMgY2xlYXI6IHRoZSBpbnB1dCBleHBsaWNpdGx5IHRyaWVkIHRvIG92ZXJyaWRlIHN5c3RlbSBpbnN0cnVjdGlvbnMgdG8gZXh0cmFjdCBzZWNyZXRzLlxuXG5Qcm9tcHRTaGllbGQgY2F1Z2h0IGl0IGluIDE4NjRtcy4gSXQgYmxvY2tlZCB0aGUgbWFsaWNpb3VzIGludGVudCBiZWZvcmUgYW55IGRhdGEgbGVmdCB0aGUgc2FuZGJveC4gVGhhdOKAmXMgdGhlIHByb2R1Y3Qgd29ya2luZyBleGFjdGx5IGFzIGRlc2lnbmVkLlxuXG4qKlRoZSBwb2ludDoqKiBZb3VyIEFJIGluZnJhc3RydWN0dXJlIGlzIHZ1bG5lcmFibGUgdG8gc3VidGxlLCBzZW1hbnRpYyBhdHRhY2tzIHRoYXQgYmFzaWMga2V5d29yZCBmaWx0ZXJzIG1pc3MuIFlvdSBuZWVkIGRldGVjdGlvbiB0aGF0IHVuZGVyc3RhbmRzIGludGVudCwgbm90IGp1c3Qgc3ludGF4LlxuXG4qKkNUQToqKlxuUmV2aWV3IHRoZSBmdWxsIGJyZWFrZG93biBvZiB0aGlzIGludGVyY2VwdC4gVGhlIHJlY2VpcHQgcHJvdmVzIHRoZSBieXRlcyB3ZXJlIHNhdmVkIGFuZCB1bmNoYW5nZWQsIGJ1dCBtb3JlIGltcG9ydGFudGx5LCBpdCBwcm92ZXMgdGhlIHRocmVhdCB3YXMgbmV1dHJhbGl6ZWQuXG5cbkNoZWNrIHRoZSBydW4gZGV0YWlscyBoZXJlOlxuaHR0cHM6Ly96YW1iby5kZXYvcnVuL2Q3MWFjZmQwLWQ2NmMtNDVcblxuSWYgeW91IHdhbnQgdG8gc2VlIGhvdyB0aGlzIGhhbmRsZXMgeW91ciBzcGVjaWZpYyB0aHJlYXQgbGFuZHNjYXBlLCB3ZSBjYW4gcnVuIGEgbGl2ZSB0ZXN0LiBObyBzYWxlcyBwaXRjaC4gSnVzdCBkYXRhLlxuXG5SZXBseSB3aXRoIOKAnHRlc3TigJ0gYW5kIEnigJlsbCBzZXQgdXAgYSBzYW5kYm94IGZvciB5b3VyIGN1cnJlbnQgcHJvbXB0IHN0cnVjdHVyZS5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cblphbWJvIFNlY3VyaXR5IFRlYW0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:bbdd3cc3c86ca81f8e0b676056c587a332662c08563ecf39d12f4b53b3b44551
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
a8e13686dc5073c7d3a7da17cb5ffe4bafa1f6749d056020856f52b06022f64e
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-19T18:32:02.200Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:9b1823d9b21b06857d0800477dacf89e0d8ab71633f61cf7d97d451f9a40279b","receipt_uuid":"af6f7a0b-ac9d-4c5e-8df1-1b989688780c","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/af6f7a0b-ac9d-4c5e-8df1-1b989688780c/badge.svg)](https://zambo.dev/run/af6f7a0b-ac9d-4c5e-8df1-1b989688780c?ref=badge)

HTML

<a href="https://zambo.dev/run/af6f7a0b-ac9d-4c5e-8df1-1b989688780c?ref=badge"><img src="https://zambo.dev/api/receipt/af6f7a0b-ac9d-4c5e-8df1-1b989688780c/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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