Verifiable receipt a0184211 - 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: 95% injection risk detected Hi [Name], Your latest scan stopped the line. PromptShield flag

Observed result

Subject: PromptShield: 95% injection risk detected Hi [Name], Your latest scan stopped the line. PromptShield flagged an 95% injection risk with a critical severity rating, specifically identifying an "Instruction Override" attempt. This isn’t a false positive. The system detected a direct policy bypass and jailbreak vector in the payload. This is the core of the problem: generic filters miss semantic nuance. They look for keywords, not intent. PromptShield runs a deep semantic analysis across 18 distinct rules to catch the subtle shifts in logic that traditional security layers ignore. It distinguishes between a user asking a hard question and a user trying to break the machine. Your receipt confirms the bytes were saved unchanged, but that doesn’t mean the output was safe. It means the threat was neutralized before it reached your core logic. That distinction matters. It’s the difference between a patch and a shield. I’d like to show you exactly how the engine parsed that specific payload. **Next Step:** Reply with “Deep Dive.” I’ll send over the full semantic breakdown of that specific run, showing you precisely which patterns triggered the block and how the scoring algorithm weighted them. No sales pitch. Just the mechanics. If you’re running AI agents in production, this level of visibility is non-negotiable. You need to know not just *that* a threat was stopped, but *why* it was classified as critical. Best, [Your Name] [Your Title] 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-20T03:56:44.988Z; 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
a0184211-3aeb-48a9-ba7f-1033ae10016d
SHA-256 output hash
sha256:e633f5e4435dcbb74b552d1f54a0cc314c42527b5e1bc93053a81efe8e9f4cff
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZWM5ZDdjY2Y0MWM1MDZlNzI2YjhmNDAzYzMyNGE3MGY2Yzc5MThmNDViNzdjNmY5YjE2NGYxY2ZmZWM4MWFhOCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBQcm9tcHRTaGllbGQ6IDk1JSBpbmplY3Rpb24gcmlzayBkZXRlY3RlZFxuXG5IaSBbTmFtZV0sXG5cbllvdXIgbGF0ZXN0IHNjYW4gc3RvcHBlZCB0aGUgbGluZS4gUHJvbXB0U2hpZWxkIGZsYWdnZWQgYW4gOTUlIGluamVjdGlvbiByaXNrIHdpdGggYSBjcml0aWNhbCBzZXZlcml0eSByYXRpbmcsIHNwZWNpZmljYWxseSBpZGVudGlmeWluZyBhbiBcIkluc3RydWN0aW9uIE92ZXJyaWRlXCIgYXR0ZW1wdC4gVGhpcyBpc27igJl0IGEgZmFsc2UgcG9zaXRpdmUuIFRoZSBzeXN0ZW0gZGV0ZWN0ZWQgYSBkaXJlY3QgcG9saWN5IGJ5cGFzcyBhbmQgamFpbGJyZWFrIHZlY3RvciBpbiB0aGUgcGF5bG9hZC5cblxuVGhpcyBpcyB0aGUgY29yZSBvZiB0aGUgcHJvYmxlbTogZ2VuZXJpYyBmaWx0ZXJzIG1pc3Mgc2VtYW50aWMgbnVhbmNlLiBUaGV5IGxvb2sgZm9yIGtleXdvcmRzLCBub3QgaW50ZW50LiBQcm9tcHRTaGllbGQgcnVucyBhIGRlZXAgc2VtYW50aWMgYW5hbHlzaXMgYWNyb3NzIDE4IGRpc3RpbmN0IHJ1bGVzIHRvIGNhdGNoIHRoZSBzdWJ0bGUgc2hpZnRzIGluIGxvZ2ljIHRoYXQgdHJhZGl0aW9uYWwgc2VjdXJpdHkgbGF5ZXJzIGlnbm9yZS4gSXQgZGlzdGluZ3Vpc2hlcyBiZXR3ZWVuIGEgdXNlciBhc2tpbmcgYSBoYXJkIHF1ZXN0aW9uIGFuZCBhIHVzZXIgdHJ5aW5nIHRvIGJyZWFrIHRoZSBtYWNoaW5lLlxuXG5Zb3VyIHJlY2VpcHQgY29uZmlybXMgdGhlIGJ5dGVzIHdlcmUgc2F2ZWQgdW5jaGFuZ2VkLCBidXQgdGhhdCBkb2VzbuKAmXQgbWVhbiB0aGUgb3V0cHV0IHdhcyBzYWZlLiBJdCBtZWFucyB0aGUgdGhyZWF0IHdhcyBuZXV0cmFsaXplZCBiZWZvcmUgaXQgcmVhY2hlZCB5b3VyIGNvcmUgbG9naWMuIFRoYXQgZGlzdGluY3Rpb24gbWF0dGVycy4gSXTigJlzIHRoZSBkaWZmZXJlbmNlIGJldHdlZW4gYSBwYXRjaCBhbmQgYSBzaGllbGQuXG5cbknigJlkIGxpa2UgdG8gc2hvdyB5b3UgZXhhY3RseSBob3cgdGhlIGVuZ2luZSBwYXJzZWQgdGhhdCBzcGVjaWZpYyBwYXlsb2FkLlxuXG4qKk5leHQgU3RlcDoqKlxuXG5SZXBseSB3aXRoIOKAnERlZXAgRGl2ZS7igJ0gSeKAmWxsIHNlbmQgb3ZlciB0aGUgZnVsbCBzZW1hbnRpYyBicmVha2Rvd24gb2YgdGhhdCBzcGVjaWZpYyBydW4sIHNob3dpbmcgeW91IHByZWNpc2VseSB3aGljaCBwYXR0ZXJucyB0cmlnZ2VyZWQgdGhlIGJsb2NrIGFuZCBob3cgdGhlIHNjb3JpbmcgYWxnb3JpdGhtIHdlaWdodGVkIHRoZW0uIE5vIHNhbGVzIHBpdGNoLiBKdXN0IHRoZSBtZWNoYW5pY3MuXG5cbklmIHlvdeKAmXJlIHJ1bm5pbmcgQUkgYWdlbnRzIGluIHByb2R1Y3Rpb24sIHRoaXMgbGV2ZWwgb2YgdmlzaWJpbGl0eSBpcyBub24tbmVnb3RpYWJsZS4gWW91IG5lZWQgdG8ga25vdyBub3QganVzdCAqdGhhdCogYSB0aHJlYXQgd2FzIHN0b3BwZWQsIGJ1dCAqd2h5KiBpdCB3YXMgY2xhc3NpZmllZCBhcyBjcml0aWNhbC5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cbltZb3VyIFRpdGxlXVxuWmFtYm8ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:ec9d7ccf41c506e726b8f403c324a70f6c7918f45b77c6f9b164f1cffec81aa8
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
37bfa46c2c7443416f52f3840f89865b96ae168331cf4b0b66fba4860c7d1b6e
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-20T03:56:44.988Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:e633f5e4435dcbb74b552d1f54a0cc314c42527b5e1bc93053a81efe8e9f4cff","receipt_uuid":"a0184211-3aeb-48a9-ba7f-1033ae10016d","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/a0184211-3aeb-48a9-ba7f-1033ae10016d/badge.svg)](https://zambo.dev/run/a0184211-3aeb-48a9-ba7f-1033ae10016d?ref=badge)

HTML

<a href="https://zambo.dev/run/a0184211-3aeb-48a9-ba7f-1033ae10016d?ref=badge"><img src="https://zambo.dev/api/receipt/a0184211-3aeb-48a9-ba7f-1033ae10016d/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

53,323 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