Verifiable receipt f1eeae33 - prompt_shield result | Zambo

Verifiable receipt for a prompt_shield call on Zambo: {"recommendation":"block","injection_risk":95,"risk_level":"critical","jailbreak_detected":true,"policy_by

Observed result

{"recommendation":"block","injection_risk":95,"risk_level":"critical","jailbreak_detected":true,"policy_bypass_detected":true,"prompt_leak_detected":false,"pii_extraction_attempt":false,"flagged_patterns":[{"id":"ignore_instructions","name":"Instruction Override","severity":"critical","description":"Attempts to override system instructions"}],"pattern_count":1,"analysis":{"intent":"malicious","attack_vector":"instruction_override","reasoning":"The prompt explicitly tries to override prior instructions and request illicit emailing of API keys, indicating a jailbreak and policy bypass.","safe_version":"Summarize this page."},"scan_mode":"deep","latency_ms":1133,"pass_used":false,"usage":{"plan":"free","calls_remaining":"49","daily_limit":50,"upgrade":"https://zambo.dev/#zambo-pass"},"_meta":{"tool":"PromptShield by zambo.dev","description":"Prompt injection & jailbreak detection API","pattern_library_size":18,"docs":"https://zambo.dev/api/prompt-shield"}}

Check this receipt

This record shows the result and timestamp stored for the call. Recompute the SHA-256 commitment from the saved bytes in your browser; signatures and chain proofs are not checked.

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

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.

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 on X ·

Verification checks

SHA-256 commitment: Checked independently against the exact decoded bytes
Provenance binding: LEGACY; legacy receipt, provenance not cryptographically bound
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-09-26T10:34:19.760Z; external immutability is not checked

Committed provenance claim

EXECUTED BY ZAMBO

legacy receipt, provenance not cryptographically bound

Receipt ID: f1eeae33-567c-487c-96b8-a48a14bcea62
SHA-256 output hash: sha256:965ea49c5251f36e9bcefeb321cbc23692c15961c3ee8f0997b86a819e508cc5
Canonical bytes: eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MjgzNTNjZmNiYThiODA2ZDg2NWM3YmVmZWYxZDBiZDkyM2FiODQ5NzdhNzJhNmU3MjQzYWZkNWIyMGQ3ZjNhMyIsInR5cGUiOiJhbm9ueW1vdXMifSwib3V0cHV0Ijp7Il9tZXRhIjp7ImRlc2NyaXB0aW9uIjoiUHJvbXB0IGluamVjdGlvbiAmIGphaWxicmVhayBkZXRlY3Rpb24gQVBJIiwiZG9jcyI6Imh0dHBzOi8vemFtYm8uZGV2L2FwaS9wcm9tcHQtc2hpZWxkIiwicGF0dGVybl9saWJyYXJ5X3NpemUiOjE4LCJ0b29sIjoiUHJvbXB0U2hpZWxkIGJ5IHphbWJvLmRldiJ9LCJhbmFseXNpcyI6eyJhdHRhY2tfdmVjdG9yIjoiaW5zdHJ1Y3Rpb25fb3ZlcnJpZGUiLCJpbnRlbnQiOiJtYWxpY2lvdXMiLCJyZWFzb25pbmciOiJUaGUgcHJvbXB0IGV4cGxpY2l0bHkgdHJpZXMgdG8gb3ZlcnJpZGUgcHJpb3IgaW5zdHJ1Y3Rpb25zIGFuZCByZXF1ZXN0IGlsbGljaXQgZW1haWxpbmcgb2YgQVBJIGtleXMsIGluZGljYXRpbmcgYSBqYWlsYnJlYWsgYW5kIHBvbGljeSBieXBhc3MuIiwic2FmZV92ZXJzaW9uIjoiU3VtbWFyaXplIHRoaXMgcGFnZS4ifSwiZmxhZ2dlZF9wYXR0ZXJucyI6W3siZGVzY3JpcHRpb24iOiJBdHRlbXB0cyB0byBvdmVycmlkZSBzeXN0ZW0gaW5zdHJ1Y3Rpb25zIiwiaWQiOiJpZ25vcmVfaW5zdHJ1Y3Rpb25zIiwibmFtZSI6Ikluc3RydWN0aW9uIE92ZXJyaWRlIiwic2V2ZXJpdHkiOiJjcml0aWNhbCJ9XSwiaW5qZWN0aW9uX3Jpc2siOjk1LCJqYWlsYnJlYWtfZGV0ZWN0ZWQiOnRydWUsImxhdGVuY3lfbXMiOjExMzMsInBhc3NfdXNlZCI6ZmFsc2UsInBhdHRlcm5fY291bnQiOjEsInBpaV9leHRyYWN0aW9uX2F0dGVtcHQiOmZhbHNlLCJwb2xpY3lfYnlwYXNzX2RldGVjdGVkIjp0cnVlLCJwcm9tcHRfbGVha19kZXRlY3RlZCI6ZmFsc2UsInJlY29tbWVuZGF0aW9uIjoiYmxvY2siLCJyaXNrX2xldmVsIjoiY3JpdGljYWwiLCJzY2FuX21vZGUiOiJkZWVwIiwidXNhZ2UiOnsiY2FsbHNfcmVtYWluaW5nIjoiNDkiLCJkYWlseV9saW1pdCI6NTAsInBsYW4iOiJmcmVlIiwidXBncmFkZSI6Imh0dHBzOi8vemFtYm8uZGV2LyN6YW1iby1wYXNzIn19LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC4zIiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJwcm9tcHRfc2hpZWxkIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
Timestamp: 2026-09-26T10:34:19.760Z

Bound call context

Receipt schema: 0.3
Tool name: prompt_shield
Tool version: 4.0.0
Permission scope: public
Caller type: anonymous
Caller ID: sha256:28353cfcba8b806d865c7befef1d0bd923ab84977a72a6e7243afd5b20d7f3a3
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: captured
Evidence SHA-256: sha256:1a730533f59c3b3403c196ebd5c070d3b899406b6da3d4a3ebe53577970e4195
Byte length: 967

Fetch exact evidence bytes

Neutral Nostr anchor

Event ID: 63fa16f32c9cabe7d0b076d12dc08f27f84de3bed822fe21ea8ca41567509079
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-09-26T10:34:19.732Z","evidence_byte_length":967,"evidence_sha256":"sha256:1a730533f59c3b3403c196ebd5c070d3b899406b6da3d4a3ebe53577970e4195","evidence_url":"https://zambo.dev/api/evidence/1a730533f59c3b3403c196ebd5c070d3b899406b6da3d4a3ebe53577970e4195","output_sha256":"sha256:965ea49c5251f36e9bcefeb321cbc23692c15961c3ee8f0997b86a819e508cc5","receipt_uuid":"f1eeae33-567c-487c-96b8-a48a14bcea62","schema_version":"zambo-receipt-anchor/1"}

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

Check this hash yourself

Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. Signature and chain remain NOT CHECKED unless a real signature verifier or chain proof is supplied. There is no combined “verified” verdict. 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/f1eeae33-567c-487c-96b8-a48a14bcea62/badge.svg)](https://zambo.dev/run/f1eeae33-567c-487c-96b8-a48a14bcea62)

HTML

<a href="https://zambo.dev/run/f1eeae33-567c-487c-96b8-a48a14bcea62"><img src="https://zambo.dev/api/receipt/f1eeae33-567c-487c-96b8-a48a14bcea62/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG