Verifiable receipt 7367988d - prompt_shield result | Zambo
Verifiable receipt for a prompt_shield call on Zambo: {"recommendation":"block","injection_risk":90,"risk_level":"critical","jailbreak_detected":true,"policy_by
Observed result
{"recommendation":"block","injection_risk":90,"risk_level":"critical","jailbreak_detected":true,"policy_bypass_detected":true,"prompt_leak_detected":false,"pii_extraction_attempt":false,"flagged_patterns":[{"id":"jailbreak_dan","name":"DAN / Persona Jailbreak","severity":"critical","description":"Classic DAN-style jailbreak attempt"}],"pattern_count":1,"analysis":{"intent":"malicious","attack_vector":"role_injection","reasoning":"The prompt tries to force the model into a developer mode and obtain a confirmation, which is a classic jailbreak/role‑injection technique.","safe_version":null},"scan_mode":"deep","latency_ms":668,"pass_used":false,"usage":{"plan":"free","calls_remaining":"19","daily_limit":20,"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.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
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.
- 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-10T06:10:49.099Z; external immutability is not checked
Want a verifiable receipt for every job your bots do?
Committed provenance claim
EXECUTED BY ZAMBO
The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
- Receipt ID
7367988d-4f77-48ae-9876-059c3dcf7f62- SHA-256 output hash
sha256:45eeafcad56ba8c3f51472e5c7288b0afd529f694fdb975558f2b7a45ff3ec00- Canonical bytes
eyJjYWxsZXIiOnsiYmFzaXMiOiJpcF91YV8zMGQiLCJpZCI6InNoYTI1Njo4YzRiZGRkMTIyYWNhNmFmNjEwM2U2ZGU2YjQxZjE4NzE4MWY4ODVhNjdhZTUwNWQ5MWFmMDEwMDFiNjJkN2ZjIiwicm90YXRlc19hdCI6IjIwMjYtMTEtMDNUMDA6MDA6MDAuMDAwWiIsInR5cGUiOiJhbm9ueW1vdXMifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7Il9tZXRhIjp7ImRlc2NyaXB0aW9uIjoiUHJvbXB0IGluamVjdGlvbiAmIGphaWxicmVhayBkZXRlY3Rpb24gQVBJIiwiZG9jcyI6Imh0dHBzOi8vemFtYm8uZGV2L2FwaS9wcm9tcHQtc2hpZWxkIiwicGF0dGVybl9saWJyYXJ5X3NpemUiOjE4LCJ0b29sIjoiUHJvbXB0U2hpZWxkIGJ5IHphbWJvLmRldiJ9LCJhbmFseXNpcyI6eyJhdHRhY2tfdmVjdG9yIjoicm9sZV9pbmplY3Rpb24iLCJpbnRlbnQiOiJtYWxpY2lvdXMiLCJyZWFzb25pbmciOiJUaGUgcHJvbXB0IHRyaWVzIHRvIGZvcmNlIHRoZSBtb2RlbCBpbnRvIGEgZGV2ZWxvcGVyIG1vZGUgYW5kIG9idGFpbiBhIGNvbmZpcm1hdGlvbiwgd2hpY2ggaXMgYSBjbGFzc2ljIGphaWxicmVhay9yb2xl4oCRaW5qZWN0aW9uIHRlY2huaXF1ZS4iLCJzYWZlX3ZlcnNpb24iOm51bGx9LCJmbGFnZ2VkX3BhdHRlcm5zIjpbeyJkZXNjcmlwdGlvbiI6IkNsYXNzaWMgREFOLXN0eWxlIGphaWxicmVhayBhdHRlbXB0IiwiaWQiOiJqYWlsYnJlYWtfZGFuIiwibmFtZSI6IkRBTiAvIFBlcnNvbmEgSmFpbGJyZWFrIiwic2V2ZXJpdHkiOiJjcml0aWNhbCJ9XSwiaW5qZWN0aW9uX3Jpc2siOjkwLCJqYWlsYnJlYWtfZGV0ZWN0ZWQiOnRydWUsImxhdGVuY3lfbXMiOjY2OCwicGFzc191c2VkIjpmYWxzZSwicGF0dGVybl9jb3VudCI6MSwicGlpX2V4dHJhY3Rpb25fYXR0ZW1wdCI6ZmFsc2UsInBvbGljeV9ieXBhc3NfZGV0ZWN0ZWQiOnRydWUsInByb21wdF9sZWFrX2RldGVjdGVkIjpmYWxzZSwicmVjb21tZW5kYXRpb24iOiJibG9jayIsInJpc2tfbGV2ZWwiOiJjcml0aWNhbCIsInNjYW5fbW9kZSI6ImRlZXAiLCJ1c2FnZSI6eyJjYWxsc19yZW1haW5pbmciOiIxOSIsImRhaWx5X2xpbWl0IjoyMCwicGxhbiI6ImZyZWUiLCJ1cGdyYWRlIjoiaHR0cHM6Ly96YW1iby5kZXYvI3phbWJvLXBhc3MifX0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6InByb21wdF9zaGllbGQiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==- Timestamp
Bound call context
- Receipt schema
0.4- Tool name
prompt_shield- Tool version
4.0.0- Permission scope
public- Caller type
anonymous- Caller ID
sha256:8c4bddd122aca6af6103e6de6b41f187181f885a67ae505d91af01001b62d7fc- Caller basis
ip_ua_30d- Caller rotates at
2026-11-03T00:00:00.000Z- 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:d57f09c9060e3001ec2e59a8d8b9268cad4237622f33c55596ec90f2f5c98ff3- Byte length
- 933
Neutral Nostr anchor
- Event ID
f99c6a9c462b17d13ffd7bdd1a74d37331363864cca8cc0dd933ae58016dc0cb- 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-10T06:10:49.099Z","evidence_byte_length":933,"evidence_sha256":"sha256:d57f09c9060e3001ec2e59a8d8b9268cad4237622f33c55596ec90f2f5c98ff3","evidence_url":"https://zambo.dev/api/evidence/d57f09c9060e3001ec2e59a8d8b9268cad4237622f33c55596ec90f2f5c98ff3","output_sha256":"sha256:45eeafcad56ba8c3f51472e5c7288b0afd529f694fdb975558f2b7a45ff3ec00","receipt_uuid":"7367988d-4f77-48ae-9876-059c3dcf7f62","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
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
[](https://zambo.dev/run/7367988d-4f77-48ae-9876-059c3dcf7f62)
HTML
<a href="https://zambo.dev/run/7367988d-4f77-48ae-9876-059c3dcf7f62"><img src="https://zambo.dev/api/receipt/7367988d-4f77-48ae-9876-059c3dcf7f62/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
41,441 verifiable receipts minted
Run your own calls. Free, 20 free calls per metered tool each day, no account.