Verifiable receipt 0379a657 - 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: Launching prompt_shield: Critical detection, zero noise Hi [Name], Stop guessing if your AI is safe. Star

Observed result

Subject: Launching prompt_shield: Critical detection, zero noise Hi [Name], Stop guessing if your AI is safe. Start knowing. We just launched **prompt_shield**, a deep-scan API that detects prompt injection, jailbreaks, and policy bypasses in real-time. It’s not just a filter; it’s a forensic engine. When a malicious query hits your endpoint, prompt_shield flags the specific attack vector—like `instruction_override`—and provides a reasoned analysis of why it’s dangerous. You get a clear verdict: block, allow, or escalate. The metadata includes latency metrics, risk levels, and a direct link to the full run receipt for audit trails. No black boxes. No vague "suspicious activity" alerts. Just precise, actionable intelligence. **Why it matters now:** * **Deep Scan Mode:** Goes beyond surface-level pattern matching to analyze intent. * **Actionable Reports:** Every flag comes with a breakdown of the attack vector and reasoning. * **Simple Integration:** Drop-in API with free tier access and unlimited calls for research. We’ve tested this against 18 known injection patterns. The system correctly identified a critical `instruction_override` attempt in under 1.3 seconds, providing a safe version of the query and a detailed receipt for verification. **Next Step:** Run your first deep scan. 1. Visit [zambo.dev/api/prompt-shield](https://zambo.dev/api/prompt-shield). 2. Use the free tier to test a live endpoint. 3. Check the receipt to see the forensic breakdown. No credit card required for the initial deep scan. 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-16T12:50:39.732Z; 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
0379a657-c4b7-414c-a22f-9f52f2bd22ee
SHA-256 output hash
sha256:52545c8592e27a5dec875819f46cf562fafae73fbc1c2d94701c936c9c20fc1f
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZTE3NTUyMzRlNzAxMjgzNTg0NTU1MjkzMjlhZTY5ZmY0YjhiMjRmZmRhNGE3NjU3ZmE2ZWE0OWFkM2ZhMGFlNyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBMYXVuY2hpbmcgcHJvbXB0X3NoaWVsZDogQ3JpdGljYWwgZGV0ZWN0aW9uLCB6ZXJvIG5vaXNlXG5cbkhpIFtOYW1lXSxcblxuU3RvcCBndWVzc2luZyBpZiB5b3VyIEFJIGlzIHNhZmUuIFN0YXJ0IGtub3dpbmcuXG5cbldlIGp1c3QgbGF1bmNoZWQgKipwcm9tcHRfc2hpZWxkKiosIGEgZGVlcC1zY2FuIEFQSSB0aGF0IGRldGVjdHMgcHJvbXB0IGluamVjdGlvbiwgamFpbGJyZWFrcywgYW5kIHBvbGljeSBieXBhc3NlcyBpbiByZWFsLXRpbWUuIEl04oCZcyBub3QganVzdCBhIGZpbHRlcjsgaXTigJlzIGEgZm9yZW5zaWMgZW5naW5lLiBXaGVuIGEgbWFsaWNpb3VzIHF1ZXJ5IGhpdHMgeW91ciBlbmRwb2ludCwgcHJvbXB0X3NoaWVsZCBmbGFncyB0aGUgc3BlY2lmaWMgYXR0YWNrIHZlY3RvcuKAlGxpa2UgYGluc3RydWN0aW9uX292ZXJyaWRlYOKAlGFuZCBwcm92aWRlcyBhIHJlYXNvbmVkIGFuYWx5c2lzIG9mIHdoeSBpdOKAmXMgZGFuZ2Vyb3VzLlxuXG5Zb3UgZ2V0IGEgY2xlYXIgdmVyZGljdDogYmxvY2ssIGFsbG93LCBvciBlc2NhbGF0ZS4gVGhlIG1ldGFkYXRhIGluY2x1ZGVzIGxhdGVuY3kgbWV0cmljcywgcmlzayBsZXZlbHMsIGFuZCBhIGRpcmVjdCBsaW5rIHRvIHRoZSBmdWxsIHJ1biByZWNlaXB0IGZvciBhdWRpdCB0cmFpbHMuIE5vIGJsYWNrIGJveGVzLiBObyB2YWd1ZSBcInN1c3BpY2lvdXMgYWN0aXZpdHlcIiBhbGVydHMuIEp1c3QgcHJlY2lzZSwgYWN0aW9uYWJsZSBpbnRlbGxpZ2VuY2UuXG5cbioqV2h5IGl0IG1hdHRlcnMgbm93OioqXG4qICAgKipEZWVwIFNjYW4gTW9kZToqKiBHb2VzIGJleW9uZCBzdXJmYWNlLWxldmVsIHBhdHRlcm4gbWF0Y2hpbmcgdG8gYW5hbHl6ZSBpbnRlbnQuXG4qICAgKipBY3Rpb25hYmxlIFJlcG9ydHM6KiogRXZlcnkgZmxhZyBjb21lcyB3aXRoIGEgYnJlYWtkb3duIG9mIHRoZSBhdHRhY2sgdmVjdG9yIGFuZCByZWFzb25pbmcuXG4qICAgKipTaW1wbGUgSW50ZWdyYXRpb246KiogRHJvcC1pbiBBUEkgd2l0aCBmcmVlIHRpZXIgYWNjZXNzIGFuZCB1bmxpbWl0ZWQgY2FsbHMgZm9yIHJlc2VhcmNoLlxuXG5XZeKAmXZlIHRlc3RlZCB0aGlzIGFnYWluc3QgMTgga25vd24gaW5qZWN0aW9uIHBhdHRlcm5zLiBUaGUgc3lzdGVtIGNvcnJlY3RseSBpZGVudGlmaWVkIGEgY3JpdGljYWwgYGluc3RydWN0aW9uX292ZXJyaWRlYCBhdHRlbXB0IGluIHVuZGVyIDEuMyBzZWNvbmRzLCBwcm92aWRpbmcgYSBzYWZlIHZlcnNpb24gb2YgdGhlIHF1ZXJ5IGFuZCBhIGRldGFpbGVkIHJlY2VpcHQgZm9yIHZlcmlmaWNhdGlvbi5cblxuKipOZXh0IFN0ZXA6KipcblJ1biB5b3VyIGZpcnN0IGRlZXAgc2Nhbi5cblxuMS4gIFZpc2l0IFt6YW1iby5kZXYvYXBpL3Byb21wdC1zaGllbGRdKGh0dHBzOi8vemFtYm8uZGV2L2FwaS9wcm9tcHQtc2hpZWxkKS5cbjIuICBVc2UgdGhlIGZyZWUgdGllciB0byB0ZXN0IGEgbGl2ZSBlbmRwb2ludC5cbjMuICBDaGVjayB0aGUgcmVjZWlwdCB0byBzZWUgdGhlIGZvcmVuc2ljIGJyZWFrZG93bi5cblxuTm8gY3JlZGl0IGNhcmQgcmVxdWlyZWQgZm9yIHRoZSBpbml0aWFsIGRlZXAgc2Nhbi5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cbltZb3VyIFRpdGxlXVxuWmFtYm8ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:e1755234e70128358455529329ae69ff4b8b24ffda4a7657fa6ea49ad3fa0ae7
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
00116b5eac588b3041304543c770c8a327e86206f9225f4e0a90ec8919a6ed01
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-16T12:50:39.732Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:52545c8592e27a5dec875819f46cf562fafae73fbc1c2d94701c936c9c20fc1f","receipt_uuid":"0379a657-c4b7-414c-a22f-9f52f2bd22ee","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/0379a657-c4b7-414c-a22f-9f52f2bd22ee/badge.svg)](https://zambo.dev/run/0379a657-c4b7-414c-a22f-9f52f2bd22ee?ref=badge)

HTML

<a href="https://zambo.dev/run/0379a657-c4b7-414c-a22f-9f52f2bd22ee?ref=badge"><img src="https://zambo.dev/api/receipt/0379a657-c4b7-414c-a22f-9f52f2bd22ee/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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