Verifiable receipt c500c060 - 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: Zambo PromptShield: Critical Threat Detection in Production Hi [Name], Your latest scan flagged a critica

Observed result

Subject: Zambo PromptShield: Critical Threat Detection in Production Hi [Name], Your latest scan flagged a critical injection attempt. The system detected a jailbreak vector attempting to override core instructions and extract system prompts. PromptShield caught it. The semantic analysis identified the malicious intent with 95% confidence. It blocked the payload before it reached your LLM, preventing any data leakage or policy bypass. This isn’t just filtering; it’s a hard stop on adversarial attacks designed to break your guardrails. Right now, your API is protected against these specific patterns. You’re seeing real-time defense against the most common AI security threats: prompt leaks, PII extraction attempts, and instruction overrides. **Next Step:** Review the full breakdown of the blocked attack here: [Link to Receipt] Check the "Analysis" section to see exactly how the 18-rule pattern library identified the threat. Understand the mechanism, then integrate the API into your production pipeline to ensure every incoming prompt is vetted before processing. This is the baseline security layer every AI product needs. 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-17T22:56:29.718Z; 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
c500c060-ea96-4c34-a114-35db5323b3b8
SHA-256 output hash
sha256:45f6a73a5e06109850a1767714b1b94e89bb253c685d094dcdb43ff8e91d3ffa
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YjU4MDNjOTU1ZjE1ZjZiNDkzMzk2MDA1ODk2OTg5NDAyNzBhMDZkZjlhZWU4NWQyNzg5Y2ZiYmUwY2FlMWM0MyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBQcm9tcHRTaGllbGQ6IENyaXRpY2FsIFRocmVhdCBEZXRlY3Rpb24gaW4gUHJvZHVjdGlvblxuXG5IaSBbTmFtZV0sXG5cbllvdXIgbGF0ZXN0IHNjYW4gZmxhZ2dlZCBhIGNyaXRpY2FsIGluamVjdGlvbiBhdHRlbXB0LiBUaGUgc3lzdGVtIGRldGVjdGVkIGEgamFpbGJyZWFrIHZlY3RvciBhdHRlbXB0aW5nIHRvIG92ZXJyaWRlIGNvcmUgaW5zdHJ1Y3Rpb25zIGFuZCBleHRyYWN0IHN5c3RlbSBwcm9tcHRzLlxuXG5Qcm9tcHRTaGllbGQgY2F1Z2h0IGl0LlxuXG5UaGUgc2VtYW50aWMgYW5hbHlzaXMgaWRlbnRpZmllZCB0aGUgbWFsaWNpb3VzIGludGVudCB3aXRoIDk1JSBjb25maWRlbmNlLiBJdCBibG9ja2VkIHRoZSBwYXlsb2FkIGJlZm9yZSBpdCByZWFjaGVkIHlvdXIgTExNLCBwcmV2ZW50aW5nIGFueSBkYXRhIGxlYWthZ2Ugb3IgcG9saWN5IGJ5cGFzcy4gVGhpcyBpc27igJl0IGp1c3QgZmlsdGVyaW5nOyBpdOKAmXMgYSBoYXJkIHN0b3Agb24gYWR2ZXJzYXJpYWwgYXR0YWNrcyBkZXNpZ25lZCB0byBicmVhayB5b3VyIGd1YXJkcmFpbHMuXG5cblJpZ2h0IG5vdywgeW91ciBBUEkgaXMgcHJvdGVjdGVkIGFnYWluc3QgdGhlc2Ugc3BlY2lmaWMgcGF0dGVybnMuIFlvdeKAmXJlIHNlZWluZyByZWFsLXRpbWUgZGVmZW5zZSBhZ2FpbnN0IHRoZSBtb3N0IGNvbW1vbiBBSSBzZWN1cml0eSB0aHJlYXRzOiBwcm9tcHQgbGVha3MsIFBJSSBleHRyYWN0aW9uIGF0dGVtcHRzLCBhbmQgaW5zdHJ1Y3Rpb24gb3ZlcnJpZGVzLlxuXG4qKk5leHQgU3RlcDoqKlxuUmV2aWV3IHRoZSBmdWxsIGJyZWFrZG93biBvZiB0aGUgYmxvY2tlZCBhdHRhY2sgaGVyZTogW0xpbmsgdG8gUmVjZWlwdF1cblxuQ2hlY2sgdGhlIFwiQW5hbHlzaXNcIiBzZWN0aW9uIHRvIHNlZSBleGFjdGx5IGhvdyB0aGUgMTgtcnVsZSBwYXR0ZXJuIGxpYnJhcnkgaWRlbnRpZmllZCB0aGUgdGhyZWF0LiBVbmRlcnN0YW5kIHRoZSBtZWNoYW5pc20sIHRoZW4gaW50ZWdyYXRlIHRoZSBBUEkgaW50byB5b3VyIHByb2R1Y3Rpb24gcGlwZWxpbmUgdG8gZW5zdXJlIGV2ZXJ5IGluY29taW5nIHByb21wdCBpcyB2ZXR0ZWQgYmVmb3JlIHByb2Nlc3NpbmcuXG5cblRoaXMgaXMgdGhlIGJhc2VsaW5lIHNlY3VyaXR5IGxheWVyIGV2ZXJ5IEFJIHByb2R1Y3QgbmVlZHMuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5bWW91ciBUaXRsZV1cblphbWJvIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:b5803c955f15f6b49339600589698940270a06df9aee85d2789cfbbe0cae1c43
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
103f1bff3e15b3eb848aa46c4ba504facb322967e79331e82c161ce18428d174
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-17T22:56:29.718Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:45f6a73a5e06109850a1767714b1b94e89bb253c685d094dcdb43ff8e91d3ffa","receipt_uuid":"c500c060-ea96-4c34-a114-35db5323b3b8","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/c500c060-ea96-4c34-a114-35db5323b3b8/badge.svg)](https://zambo.dev/run/c500c060-ea96-4c34-a114-35db5323b3b8?ref=badge)

HTML

<a href="https://zambo.dev/run/c500c060-ea96-4c34-a114-35db5323b3b8?ref=badge"><img src="https://zambo.dev/api/receipt/c500c060-ea96-4c34-a114-35db5323b3b8/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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