Verifiable receipt d77acab0 - 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 is live: Stop jailbreaks before they start [Name], You are likely already managing the risk

Observed result

Subject: PromptShield is live: Stop jailbreaks before they start [Name], You are likely already managing the risk of malicious input in your AI workflows. The threat landscape has shifted from simple data leakage to complex instruction overrides and policy bypasses. Zambo PromptShield is now available to detect and block these attacks in real time. It is a deep-scan API that identifies jailbreak attempts, prompt leaks, and instruction overrides with critical severity ratings. It does not just flag anomalies; it provides a structured analysis of the attack vector, including specific flagged patterns and reasoning behind the detection. For example, a recent scan identified a "critical" injection risk (95%) where a user attempted to override system instructions to extract secret keys. The tool flagged the "Instruction Override" pattern, classified the intent as malicious, and recommended a block action. This happens in under 1.1 seconds, ensuring your application remains secure without adding significant latency to the user experience. The service is built for developers who need verifiable security logs. Every detection comes with a receipt URL, proving that the saved bytes were analyzed and the decision was made based on the observed threat level, not just a heuristic guess. Start with the free tier, which includes 20 calls per day. This allows you to test the detection accuracy against your specific use cases before committing to the Zambo Pass for unlimited access. [Link to Zambo PromptShield Docs] 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-16T05:01:41.006Z; 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
d77acab0-e159-4d02-bced-a66c1f025292
SHA-256 output hash
sha256:d6288491c315470a4adf3c6c2b291ddc0c604c456f5532760ad23079cbc6e7bc
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NzIxNjUyMWE3YjlhMDg3MDE4MDgwZTFmNmI1NmE4N2Q4MmM1ZjZjYTJkNjBmOGM1OGJmOWU1OWEzMWJkMThlNiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBQcm9tcHRTaGllbGQgaXMgbGl2ZTogU3RvcCBqYWlsYnJlYWtzIGJlZm9yZSB0aGV5IHN0YXJ0XG5cbltOYW1lXSxcblxuWW91IGFyZSBsaWtlbHkgYWxyZWFkeSBtYW5hZ2luZyB0aGUgcmlzayBvZiBtYWxpY2lvdXMgaW5wdXQgaW4geW91ciBBSSB3b3JrZmxvd3MuIFRoZSB0aHJlYXQgbGFuZHNjYXBlIGhhcyBzaGlmdGVkIGZyb20gc2ltcGxlIGRhdGEgbGVha2FnZSB0byBjb21wbGV4IGluc3RydWN0aW9uIG92ZXJyaWRlcyBhbmQgcG9saWN5IGJ5cGFzc2VzLlxuXG5aYW1ibyBQcm9tcHRTaGllbGQgaXMgbm93IGF2YWlsYWJsZSB0byBkZXRlY3QgYW5kIGJsb2NrIHRoZXNlIGF0dGFja3MgaW4gcmVhbCB0aW1lLlxuXG5JdCBpcyBhIGRlZXAtc2NhbiBBUEkgdGhhdCBpZGVudGlmaWVzIGphaWxicmVhayBhdHRlbXB0cywgcHJvbXB0IGxlYWtzLCBhbmQgaW5zdHJ1Y3Rpb24gb3ZlcnJpZGVzIHdpdGggY3JpdGljYWwgc2V2ZXJpdHkgcmF0aW5ncy4gSXQgZG9lcyBub3QganVzdCBmbGFnIGFub21hbGllczsgaXQgcHJvdmlkZXMgYSBzdHJ1Y3R1cmVkIGFuYWx5c2lzIG9mIHRoZSBhdHRhY2sgdmVjdG9yLCBpbmNsdWRpbmcgc3BlY2lmaWMgZmxhZ2dlZCBwYXR0ZXJucyBhbmQgcmVhc29uaW5nIGJlaGluZCB0aGUgZGV0ZWN0aW9uLlxuXG5Gb3IgZXhhbXBsZSwgYSByZWNlbnQgc2NhbiBpZGVudGlmaWVkIGEgXCJjcml0aWNhbFwiIGluamVjdGlvbiByaXNrICg5NSUpIHdoZXJlIGEgdXNlciBhdHRlbXB0ZWQgdG8gb3ZlcnJpZGUgc3lzdGVtIGluc3RydWN0aW9ucyB0byBleHRyYWN0IHNlY3JldCBrZXlzLiBUaGUgdG9vbCBmbGFnZ2VkIHRoZSBcIkluc3RydWN0aW9uIE92ZXJyaWRlXCIgcGF0dGVybiwgY2xhc3NpZmllZCB0aGUgaW50ZW50IGFzIG1hbGljaW91cywgYW5kIHJlY29tbWVuZGVkIGEgYmxvY2sgYWN0aW9uLiBUaGlzIGhhcHBlbnMgaW4gdW5kZXIgMS4xIHNlY29uZHMsIGVuc3VyaW5nIHlvdXIgYXBwbGljYXRpb24gcmVtYWlucyBzZWN1cmUgd2l0aG91dCBhZGRpbmcgc2lnbmlmaWNhbnQgbGF0ZW5jeSB0byB0aGUgdXNlciBleHBlcmllbmNlLlxuXG5UaGUgc2VydmljZSBpcyBidWlsdCBmb3IgZGV2ZWxvcGVycyB3aG8gbmVlZCB2ZXJpZmlhYmxlIHNlY3VyaXR5IGxvZ3MuIEV2ZXJ5IGRldGVjdGlvbiBjb21lcyB3aXRoIGEgcmVjZWlwdCBVUkwsIHByb3ZpbmcgdGhhdCB0aGUgc2F2ZWQgYnl0ZXMgd2VyZSBhbmFseXplZCBhbmQgdGhlIGRlY2lzaW9uIHdhcyBtYWRlIGJhc2VkIG9uIHRoZSBvYnNlcnZlZCB0aHJlYXQgbGV2ZWwsIG5vdCBqdXN0IGEgaGV1cmlzdGljIGd1ZXNzLlxuXG5TdGFydCB3aXRoIHRoZSBmcmVlIHRpZXIsIHdoaWNoIGluY2x1ZGVzIDIwIGNhbGxzIHBlciBkYXkuIFRoaXMgYWxsb3dzIHlvdSB0byB0ZXN0IHRoZSBkZXRlY3Rpb24gYWNjdXJhY3kgYWdhaW5zdCB5b3VyIHNwZWNpZmljIHVzZSBjYXNlcyBiZWZvcmUgY29tbWl0dGluZyB0byB0aGUgWmFtYm8gUGFzcyBmb3IgdW5saW1pdGVkIGFjY2Vzcy5cblxuW0xpbmsgdG8gWmFtYm8gUHJvbXB0U2hpZWxkIERvY3NdXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5bWW91ciBUaXRsZV1cblphbWJvIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:7216521a7b9a087018080e1f6b56a87d82c5f6ca2d60f8c58bf9e59a31bd18e6
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
5f8b527ca8ce3f92d1a45603b79798f5f65ca30acaba03053d114593770c6a3b
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-16T05:01:41.006Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:d6288491c315470a4adf3c6c2b291ddc0c604c456f5532760ad23079cbc6e7bc","receipt_uuid":"d77acab0-e159-4d02-bced-a66c1f025292","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/d77acab0-e159-4d02-bced-a66c1f025292/badge.svg)](https://zambo.dev/run/d77acab0-e159-4d02-bced-a66c1f025292?ref=badge)

HTML

<a href="https://zambo.dev/run/d77acab0-e159-4d02-bced-a66c1f025292?ref=badge"><img src="https://zambo.dev/api/receipt/d77acab0-e159-4d02-bced-a66c1f025292/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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