Verifiable receipt dfde0d1a - 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 detection results for your launch Hi [Name], Your recent scan revealed a critical

Observed result

Subject: PromptShield: Critical detection results for your launch Hi [Name], Your recent scan revealed a critical security posture that requires immediate attention before you go live. The analysis flagged a high-risk injection attempt with a 95% risk score. Specifically, the system detected a "Instruction Override" pattern where the input attempted to bypass core safety policies and extract confidential system prompts. This is not a false positive; the semantic analysis confirmed malicious intent targeting data extraction and jailbreak execution. While the detection engine successfully blocked the malicious payload, the presence of such sophisticated attack vectors in your test suite indicates a vulnerability in your input validation layer. You cannot rely solely on the detector to scrub your inputs; your application logic must also be hardened against these manipulation tactics. Note that the receipt generated by this scan proves the bytes saved to the log, but it does not validate the correctness of your underlying model logic. Treat this as a signal to stress-test your defensive layers, not as a certificate of safety. Your account currently has 16 calls remaining on the free tier. To ensure your launch is secure, I recommend you review the flagged patterns in the dashboard immediately. [Link to Dashboard] Best, [Your Name] Zambo Team

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-20T04:36:45.032Z; 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
dfde0d1a-f232-441c-8b5f-494732b7a711
SHA-256 output hash
sha256:a65964c93ff9518a114de31cfdaff6707bbcf2ed27177987c33bae099ed2f6c7
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6Mzg4NmI3MzNjYjMxZWI3YjM1MDhiYWQ2ZDgzNzBiNmNiZTkwOGEzMjZmODkwMDEzNDY4M2Q3YTkzYjkyZmVhZCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBQcm9tcHRTaGllbGQ6IENyaXRpY2FsIGRldGVjdGlvbiByZXN1bHRzIGZvciB5b3VyIGxhdW5jaFxuXG5IaSBbTmFtZV0sXG5cbllvdXIgcmVjZW50IHNjYW4gcmV2ZWFsZWQgYSBjcml0aWNhbCBzZWN1cml0eSBwb3N0dXJlIHRoYXQgcmVxdWlyZXMgaW1tZWRpYXRlIGF0dGVudGlvbiBiZWZvcmUgeW91IGdvIGxpdmUuXG5cblRoZSBhbmFseXNpcyBmbGFnZ2VkIGEgaGlnaC1yaXNrIGluamVjdGlvbiBhdHRlbXB0IHdpdGggYSA5NSUgcmlzayBzY29yZS4gU3BlY2lmaWNhbGx5LCB0aGUgc3lzdGVtIGRldGVjdGVkIGEgXCJJbnN0cnVjdGlvbiBPdmVycmlkZVwiIHBhdHRlcm4gd2hlcmUgdGhlIGlucHV0IGF0dGVtcHRlZCB0byBieXBhc3MgY29yZSBzYWZldHkgcG9saWNpZXMgYW5kIGV4dHJhY3QgY29uZmlkZW50aWFsIHN5c3RlbSBwcm9tcHRzLiBUaGlzIGlzIG5vdCBhIGZhbHNlIHBvc2l0aXZlOyB0aGUgc2VtYW50aWMgYW5hbHlzaXMgY29uZmlybWVkIG1hbGljaW91cyBpbnRlbnQgdGFyZ2V0aW5nIGRhdGEgZXh0cmFjdGlvbiBhbmQgamFpbGJyZWFrIGV4ZWN1dGlvbi5cblxuV2hpbGUgdGhlIGRldGVjdGlvbiBlbmdpbmUgc3VjY2Vzc2Z1bGx5IGJsb2NrZWQgdGhlIG1hbGljaW91cyBwYXlsb2FkLCB0aGUgcHJlc2VuY2Ugb2Ygc3VjaCBzb3BoaXN0aWNhdGVkIGF0dGFjayB2ZWN0b3JzIGluIHlvdXIgdGVzdCBzdWl0ZSBpbmRpY2F0ZXMgYSB2dWxuZXJhYmlsaXR5IGluIHlvdXIgaW5wdXQgdmFsaWRhdGlvbiBsYXllci4gWW91IGNhbm5vdCByZWx5IHNvbGVseSBvbiB0aGUgZGV0ZWN0b3IgdG8gc2NydWIgeW91ciBpbnB1dHM7IHlvdXIgYXBwbGljYXRpb24gbG9naWMgbXVzdCBhbHNvIGJlIGhhcmRlbmVkIGFnYWluc3QgdGhlc2UgbWFuaXB1bGF0aW9uIHRhY3RpY3MuXG5cbk5vdGUgdGhhdCB0aGUgcmVjZWlwdCBnZW5lcmF0ZWQgYnkgdGhpcyBzY2FuIHByb3ZlcyB0aGUgYnl0ZXMgc2F2ZWQgdG8gdGhlIGxvZywgYnV0IGl0IGRvZXMgbm90IHZhbGlkYXRlIHRoZSBjb3JyZWN0bmVzcyBvZiB5b3VyIHVuZGVybHlpbmcgbW9kZWwgbG9naWMuIFRyZWF0IHRoaXMgYXMgYSBzaWduYWwgdG8gc3RyZXNzLXRlc3QgeW91ciBkZWZlbnNpdmUgbGF5ZXJzLCBub3QgYXMgYSBjZXJ0aWZpY2F0ZSBvZiBzYWZldHkuXG5cbllvdXIgYWNjb3VudCBjdXJyZW50bHkgaGFzIDE2IGNhbGxzIHJlbWFpbmluZyBvbiB0aGUgZnJlZSB0aWVyLiBUbyBlbnN1cmUgeW91ciBsYXVuY2ggaXMgc2VjdXJlLCBJIHJlY29tbWVuZCB5b3UgcmV2aWV3IHRoZSBmbGFnZ2VkIHBhdHRlcm5zIGluIHRoZSBkYXNoYm9hcmQgaW1tZWRpYXRlbHkuXG5cbltMaW5rIHRvIERhc2hib2FyZF1cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cblphbWJvIFRlYW0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:3886b733cb31eb7b3508bad6d8370b6cbe908a326f8900134683d7a93b92fead
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
4ea66dc544909871bfaaedbcc08f62062c108ec2eb99c39038c8317ed7d454e5
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-20T04:36:45.032Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:a65964c93ff9518a114de31cfdaff6707bbcf2ed27177987c33bae099ed2f6c7","receipt_uuid":"dfde0d1a-f232-441c-8b5f-494732b7a711","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

Check this hash yourself

Receipt commitment: commitment matched; issuer, signature and chain not checked. This checks the saved bytes, not whether 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/dfde0d1a-f232-441c-8b5f-494732b7a711/badge.svg)](https://zambo.dev/run/dfde0d1a-f232-441c-8b5f-494732b7a711?ref=badge)

HTML

<a href="https://zambo.dev/run/dfde0d1a-f232-441c-8b5f-494732b7a711?ref=badge"><img src="https://zambo.dev/api/receipt/dfde0d1a-f232-441c-8b5f-494732b7a711/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

53,353 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