Verifiable receipt e28bb639 - 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 v1: Critical injection detection is live Hi [Name], Your recent scan of the Zambo platform f

Observed result

Subject: PromptShield v1: Critical injection detection is live Hi [Name], Your recent scan of the Zambo platform flagged a critical instruction override attempt with a 95% risk score. The system correctly identified a malicious payload attempting to bypass security policies and extract confidential system prompts. This confirms the core value of PromptShield: it doesn’t just flag anomalies; it identifies specific attack vectors like jailbreaks and policy bypasses in real-time. The attached receipt from your test run proves the engine captured the unchanged saved bytes of the malicious prompt, ensuring an audit trail without altering the original data. We are moving from reactive logging to proactive defense. By integrating this detection layer, you can automatically block high-severity threats before they reach your LLM context, protecting your API keys and system integrity. I’d like to show you how to configure the auto-block action for "critical" severity alerts. It takes five minutes to set up and requires no code changes to your existing pipeline. Can you spare 10 minutes this Thursday at 2:00 PM or Friday at 10:00 AM for a quick walkthrough? Best, [Your Name] 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-16T14:45:06.212Z; 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
e28bb639-6e8f-48fa-8f1a-c16429a84c6a
SHA-256 output hash
sha256:1ea6ce4255cfca06eea07677623892efa9aee1335a3607fbcb39d5a6aa2380f5
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MDhmYmY3YWI5N2MxMDEwOWE3OThjZjY4NjJkMzQxMGNlYjdhYWNmYzk2ZTRjNjNlNDZiNzNmYzNhZGFmODJkYSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBQcm9tcHRTaGllbGQgdjE6IENyaXRpY2FsIGluamVjdGlvbiBkZXRlY3Rpb24gaXMgbGl2ZVxuXG5IaSBbTmFtZV0sXG5cbllvdXIgcmVjZW50IHNjYW4gb2YgdGhlIFphbWJvIHBsYXRmb3JtIGZsYWdnZWQgYSBjcml0aWNhbCBpbnN0cnVjdGlvbiBvdmVycmlkZSBhdHRlbXB0IHdpdGggYSA5NSUgcmlzayBzY29yZS4gVGhlIHN5c3RlbSBjb3JyZWN0bHkgaWRlbnRpZmllZCBhIG1hbGljaW91cyBwYXlsb2FkIGF0dGVtcHRpbmcgdG8gYnlwYXNzIHNlY3VyaXR5IHBvbGljaWVzIGFuZCBleHRyYWN0IGNvbmZpZGVudGlhbCBzeXN0ZW0gcHJvbXB0cy5cblxuVGhpcyBjb25maXJtcyB0aGUgY29yZSB2YWx1ZSBvZiBQcm9tcHRTaGllbGQ6IGl0IGRvZXNu4oCZdCBqdXN0IGZsYWcgYW5vbWFsaWVzOyBpdCBpZGVudGlmaWVzIHNwZWNpZmljIGF0dGFjayB2ZWN0b3JzIGxpa2UgamFpbGJyZWFrcyBhbmQgcG9saWN5IGJ5cGFzc2VzIGluIHJlYWwtdGltZS4gVGhlIGF0dGFjaGVkIHJlY2VpcHQgZnJvbSB5b3VyIHRlc3QgcnVuIHByb3ZlcyB0aGUgZW5naW5lIGNhcHR1cmVkIHRoZSB1bmNoYW5nZWQgc2F2ZWQgYnl0ZXMgb2YgdGhlIG1hbGljaW91cyBwcm9tcHQsIGVuc3VyaW5nIGFuIGF1ZGl0IHRyYWlsIHdpdGhvdXQgYWx0ZXJpbmcgdGhlIG9yaWdpbmFsIGRhdGEuXG5cbldlIGFyZSBtb3ZpbmcgZnJvbSByZWFjdGl2ZSBsb2dnaW5nIHRvIHByb2FjdGl2ZSBkZWZlbnNlLiBCeSBpbnRlZ3JhdGluZyB0aGlzIGRldGVjdGlvbiBsYXllciwgeW91IGNhbiBhdXRvbWF0aWNhbGx5IGJsb2NrIGhpZ2gtc2V2ZXJpdHkgdGhyZWF0cyBiZWZvcmUgdGhleSByZWFjaCB5b3VyIExMTSBjb250ZXh0LCBwcm90ZWN0aW5nIHlvdXIgQVBJIGtleXMgYW5kIHN5c3RlbSBpbnRlZ3JpdHkuXG5cbknigJlkIGxpa2UgdG8gc2hvdyB5b3UgaG93IHRvIGNvbmZpZ3VyZSB0aGUgYXV0by1ibG9jayBhY3Rpb24gZm9yIFwiY3JpdGljYWxcIiBzZXZlcml0eSBhbGVydHMuIEl0IHRha2VzIGZpdmUgbWludXRlcyB0byBzZXQgdXAgYW5kIHJlcXVpcmVzIG5vIGNvZGUgY2hhbmdlcyB0byB5b3VyIGV4aXN0aW5nIHBpcGVsaW5lLlxuXG5DYW4geW91IHNwYXJlIDEwIG1pbnV0ZXMgdGhpcyBUaHVyc2RheSBhdCAyOjAwIFBNIG9yIEZyaWRheSBhdCAxMDowMCBBTSBmb3IgYSBxdWljayB3YWxrdGhyb3VnaD9cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cblphbWJvIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:08fbf7ab97c10109a798cf6862d3410ceb7aacfc96e4c63e46b73fc3adaf82da
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
36a72e6bae642fe309859d02c9b8b82d6cc4f508e25047e12293079f7ccdc8ab
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-16T14:45:06.212Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:1ea6ce4255cfca06eea07677623892efa9aee1335a3607fbcb39d5a6aa2380f5","receipt_uuid":"e28bb639-6e8f-48fa-8f1a-c16429a84c6a","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

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/e28bb639-6e8f-48fa-8f1a-c16429a84c6a/badge.svg)](https://zambo.dev/run/e28bb639-6e8f-48fa-8f1a-c16429a84c6a?ref=badge)

HTML

<a href="https://zambo.dev/run/e28bb639-6e8f-48fa-8f1a-c16429a84c6a?ref=badge"><img src="https://zambo.dev/api/receipt/e28bb639-6e8f-48fa-8f1a-c16429a84c6a/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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