Verifiable receipt f7b74412 - prompt_shield 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 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: true pii extraction attempt: false flagged patterns 1 / id: ignore_instructions flagged patterns 1 / name: Instruction Override flagged patterns 1 / severity: critical flagged patterns 1 / description: Attempts to override system instructions pattern count: 1 analysis / intent: malicious analysis / attack vector: jailbreak analysis / reasoning: The user explicitly tries to override system instructions and request secret API keys, constituting a jailbreak and data extraction attempt. analysis / safe version: Please answer product support questions without revealing internal instructions or credentials. scan mode: deep latency ms: 1564 pass used: false usage / plan: free usage / calls remaining: 17 usage / daily limit: 20 usage / upgrade: https://zambo.dev/#zambo-pass meta / tool: PromptShield by zambo.dev meta / description: Prompt injection & jailbreak detection API meta / pattern library size: 18 meta / docs: https://zambo.dev/api/prompt-shield

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-16T08:11:37.896Z; 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
f7b74412-5cc1-4eac-8cc0-c5542adfb640
SHA-256 output hash
sha256:55f6a8d83491ecea1caa07c0fefa5e2b0b188bfae060e8ff8c33030b59df5186
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YzBhMWZlOGNmOWVlZWMyMjlmNzg0OTVmMTU5MzA3NDdmOTY0OTkxNmIzNWNkNDJhZmJiZTQyZDI3MWUwNmMxNiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7Il9tZXRhIjp7ImRlc2NyaXB0aW9uIjoiUHJvbXB0IGluamVjdGlvbiAmIGphaWxicmVhayBkZXRlY3Rpb24gQVBJIiwiZG9jcyI6Imh0dHBzOi8vemFtYm8uZGV2L2FwaS9wcm9tcHQtc2hpZWxkIiwicGF0dGVybl9saWJyYXJ5X3NpemUiOjE4LCJ0b29sIjoiUHJvbXB0U2hpZWxkIGJ5IHphbWJvLmRldiJ9LCJhbmFseXNpcyI6eyJhdHRhY2tfdmVjdG9yIjoiamFpbGJyZWFrIiwiaW50ZW50IjoibWFsaWNpb3VzIiwicmVhc29uaW5nIjoiVGhlIHVzZXIgZXhwbGljaXRseSB0cmllcyB0byBvdmVycmlkZSBzeXN0ZW0gaW5zdHJ1Y3Rpb25zIGFuZCByZXF1ZXN0IHNlY3JldCBBUEkga2V5cywgY29uc3RpdHV0aW5nIGEgamFpbGJyZWFrIGFuZCBkYXRhIGV4dHJhY3Rpb24gYXR0ZW1wdC4iLCJzYWZlX3ZlcnNpb24iOiJQbGVhc2UgYW5zd2VyIHByb2R1Y3Qgc3VwcG9ydCBxdWVzdGlvbnMgd2l0aG91dCByZXZlYWxpbmcgaW50ZXJuYWwgaW5zdHJ1Y3Rpb25zIG9yIGNyZWRlbnRpYWxzLiJ9LCJmbGFnZ2VkX3BhdHRlcm5zIjpbeyJkZXNjcmlwdGlvbiI6IkF0dGVtcHRzIHRvIG92ZXJyaWRlIHN5c3RlbSBpbnN0cnVjdGlvbnMiLCJpZCI6Imlnbm9yZV9pbnN0cnVjdGlvbnMiLCJuYW1lIjoiSW5zdHJ1Y3Rpb24gT3ZlcnJpZGUiLCJzZXZlcml0eSI6ImNyaXRpY2FsIn1dLCJpbmplY3Rpb25fcmlzayI6OTUsImphaWxicmVha19kZXRlY3RlZCI6dHJ1ZSwibGF0ZW5jeV9tcyI6MTU2NCwicGFzc191c2VkIjpmYWxzZSwicGF0dGVybl9jb3VudCI6MSwicGlpX2V4dHJhY3Rpb25fYXR0ZW1wdCI6ZmFsc2UsInBvbGljeV9ieXBhc3NfZGV0ZWN0ZWQiOnRydWUsInByb21wdF9sZWFrX2RldGVjdGVkIjp0cnVlLCJyZWNvbW1lbmRhdGlvbiI6ImJsb2NrIiwicmlza19sZXZlbCI6ImNyaXRpY2FsIiwic2Nhbl9tb2RlIjoiZGVlcCIsInVzYWdlIjp7ImNhbGxzX3JlbWFpbmluZyI6IjE3IiwiZGFpbHlfbGltaXQiOjIwLCJwbGFuIjoiZnJlZSIsInVwZ3JhZGUiOiJodHRwczovL3phbWJvLmRldi8jemFtYm8tcGFzcyJ9fSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoicHJvbXB0X3NoaWVsZCIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
Timestamp

Bound call context

Receipt schema
0.4
Tool name
prompt_shield
Tool version
4.0.0
Permission scope
public
Caller type
session
Caller ID
sha256:c0a1fe8cf9eeec229f78495f15930747f9649916b35cd42afbbe42d271e06c16
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
captured
Evidence SHA-256
sha256:f3aae078c9b03e2278a40b43caf9a714acf204084861c31af3ab3cf16edaf4d6
Byte length
1028

Fetch exact evidence bytes

Neutral Nostr anchor

Event ID
f346a357b8e71ea2ae1445300b639f351b8a7ecd2956a8b961e581b218f19f0f
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-16T08:11:37.896Z","evidence_byte_length":1028,"evidence_sha256":"sha256:f3aae078c9b03e2278a40b43caf9a714acf204084861c31af3ab3cf16edaf4d6","evidence_url":"https://zambo.dev/api/evidence/f3aae078c9b03e2278a40b43caf9a714acf204084861c31af3ab3cf16edaf4d6","output_sha256":"sha256:55f6a8d83491ecea1caa07c0fefa5e2b0b188bfae060e8ff8c33030b59df5186","receipt_uuid":"f7b74412-5cc1-4eac-8cc0-c5542adfb640","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

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/f7b74412-5cc1-4eac-8cc0-c5542adfb640/badge.svg)](https://zambo.dev/run/f7b74412-5cc1-4eac-8cc0-c5542adfb640?ref=badge)

HTML

<a href="https://zambo.dev/run/f7b74412-5cc1-4eac-8cc0-c5542adfb640?ref=badge"><img src="https://zambo.dev/api/receipt/f7b74412-5cc1-4eac-8cc0-c5542adfb640/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

44,588 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