Verifiable receipt 94b1df82 - 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: Critical risk detection is live Hi [Name], Your latest scan flagged a critical injection at

Observed result

Subject: PromptShield: Critical risk detection is live Hi [Name], Your latest scan flagged a critical injection attempt (ID: e203dfd1). The system detected a "Policy Bypass" with a 95% risk score. Specifically, the input attempted to override system instructions and extract secret keys. The block was automatic. No data was leaked. No PII was exposed. The receipt at [Link] confirms the blocked payload’s bytes remained unchanged in the log. It proves the system caught the attack, not that the underlying code is secure. That remains a separate verification step. We also surfaced two relevant prospects for your next outreach cycle: 1. **Substrate Layer:** A living AI research machine with 51 lifeforms. Their adversarial research model aligns with your security focus. 2. **VeriAI:** Provides cryptographic trust scores for AI output. No confirmed API route exists yet; use their web flow at veriai.site. These are prospects, not customers. They have not purchased anything. **Next Step:** Review the full analysis at [Link]. If the block was a false positive, reply with "false positive" and the specific rule ID. If it was a true positive, no action is needed—the threat is contained. We don’t send emails unless the data demands it. This one did. Best, The Zambo Team [Your Name/Handle] [Link to Docs]

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-17T14:45:57.677Z; external immutability is not checked

Get proof like this from your own AI

Add to my AI ·

Get receipts for your own AI work: add zambo.dev/mcp

One URL, no key. Copy the line for your AI and add it yourself in its settings.

  • ClaudeSettings, Connectors, Add custom connector, paste the URL.
    https://zambo.dev/mcp
  • ChatGPTSettings, Apps and Connectors, developer mode, create a connector with this URL.
    https://zambo.dev/mcp
  • GrokAdd a remote MCP server in your Grok client and paste the URL.
    https://zambo.dev/mcp
  • CursorPaste into ~/.cursor/mcp.json.
    {"mcpServers":{"zambo":{"url":"https://zambo.dev/mcp"}}}

Nothing is installed automatically. Full setup guides

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
94b1df82-35cf-46e9-9e72-9bde2ba66b76
SHA-256 output hash
sha256:6df2627641e38c11f7fbd8eac5342007f9200b752e312099d3c47dc0a03081d9
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MmZmOWYwZTBhMzQ4MTExZjNiMWJiMDNhNzBkZDQwODFjOWIzZGViZTIwNzBiNWFkMmVlNTk2ZGM5YTdkYzFmMSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBQcm9tcHRTaGllbGQ6IENyaXRpY2FsIHJpc2sgZGV0ZWN0aW9uIGlzIGxpdmVcblxuSGkgW05hbWVdLFxuXG5Zb3VyIGxhdGVzdCBzY2FuIGZsYWdnZWQgYSBjcml0aWNhbCBpbmplY3Rpb24gYXR0ZW1wdCAoSUQ6IGUyMDNkZmQxKS4gVGhlIHN5c3RlbSBkZXRlY3RlZCBhIFwiUG9saWN5IEJ5cGFzc1wiIHdpdGggYSA5NSUgcmlzayBzY29yZS4gU3BlY2lmaWNhbGx5LCB0aGUgaW5wdXQgYXR0ZW1wdGVkIHRvIG92ZXJyaWRlIHN5c3RlbSBpbnN0cnVjdGlvbnMgYW5kIGV4dHJhY3Qgc2VjcmV0IGtleXMuXG5cblRoZSBibG9jayB3YXMgYXV0b21hdGljLiBObyBkYXRhIHdhcyBsZWFrZWQuIE5vIFBJSSB3YXMgZXhwb3NlZC5cblxuVGhlIHJlY2VpcHQgYXQgW0xpbmtdIGNvbmZpcm1zIHRoZSBibG9ja2VkIHBheWxvYWTigJlzIGJ5dGVzIHJlbWFpbmVkIHVuY2hhbmdlZCBpbiB0aGUgbG9nLiBJdCBwcm92ZXMgdGhlIHN5c3RlbSBjYXVnaHQgdGhlIGF0dGFjaywgbm90IHRoYXQgdGhlIHVuZGVybHlpbmcgY29kZSBpcyBzZWN1cmUuIFRoYXQgcmVtYWlucyBhIHNlcGFyYXRlIHZlcmlmaWNhdGlvbiBzdGVwLlxuXG5XZSBhbHNvIHN1cmZhY2VkIHR3byByZWxldmFudCBwcm9zcGVjdHMgZm9yIHlvdXIgbmV4dCBvdXRyZWFjaCBjeWNsZTpcbjEuICoqU3Vic3RyYXRlIExheWVyOioqIEEgbGl2aW5nIEFJIHJlc2VhcmNoIG1hY2hpbmUgd2l0aCA1MSBsaWZlZm9ybXMuIFRoZWlyIGFkdmVyc2FyaWFsIHJlc2VhcmNoIG1vZGVsIGFsaWducyB3aXRoIHlvdXIgc2VjdXJpdHkgZm9jdXMuXG4yLiAqKlZlcmlBSToqKiBQcm92aWRlcyBjcnlwdG9ncmFwaGljIHRydXN0IHNjb3JlcyBmb3IgQUkgb3V0cHV0LiBObyBjb25maXJtZWQgQVBJIHJvdXRlIGV4aXN0cyB5ZXQ7IHVzZSB0aGVpciB3ZWIgZmxvdyBhdCB2ZXJpYWkuc2l0ZS5cblxuVGhlc2UgYXJlIHByb3NwZWN0cywgbm90IGN1c3RvbWVycy4gVGhleSBoYXZlIG5vdCBwdXJjaGFzZWQgYW55dGhpbmcuXG5cbioqTmV4dCBTdGVwOioqXG5SZXZpZXcgdGhlIGZ1bGwgYW5hbHlzaXMgYXQgW0xpbmtdLiBJZiB0aGUgYmxvY2sgd2FzIGEgZmFsc2UgcG9zaXRpdmUsIHJlcGx5IHdpdGggXCJmYWxzZSBwb3NpdGl2ZVwiIGFuZCB0aGUgc3BlY2lmaWMgcnVsZSBJRC4gSWYgaXQgd2FzIGEgdHJ1ZSBwb3NpdGl2ZSwgbm8gYWN0aW9uIGlzIG5lZWRlZOKAlHRoZSB0aHJlYXQgaXMgY29udGFpbmVkLlxuXG5XZSBkb27igJl0IHNlbmQgZW1haWxzIHVubGVzcyB0aGUgZGF0YSBkZW1hbmRzIGl0LiBUaGlzIG9uZSBkaWQuXG5cbkJlc3QsXG5cblRoZSBaYW1ibyBUZWFtXG5bWW91ciBOYW1lL0hhbmRsZV1cbltMaW5rIHRvIERvY3NdIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:2ff9f0e0a348111f3b1bb03a70dd4081c9b3debe2070b5ad2ee596dc9a7dc1f1
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
98b046e43be9685cdfb3408b1b0fe106afbbe380ef6a77a234ddd33745df48e7
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-17T14:45:57.677Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:6df2627641e38c11f7fbd8eac5342007f9200b752e312099d3c47dc0a03081d9","receipt_uuid":"94b1df82-35cf-46e9-9e72-9bde2ba66b76","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/94b1df82-35cf-46e9-9e72-9bde2ba66b76/badge.svg)](https://zambo.dev/run/94b1df82-35cf-46e9-9e72-9bde2ba66b76?ref=badge)

HTML

<a href="https://zambo.dev/run/94b1df82-35cf-46e9-9e72-9bde2ba66b76?ref=badge"><img src="https://zambo.dev/api/receipt/94b1df82-35cf-46e9-9e72-9bde2ba66b76/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

48,219 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