Verifiable receipt a24ca14a - 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: Detecting critical injection risks in your AI stack [Recipient Name], Your latest scan flag

Observed result

Subject: PromptShield: Detecting critical injection risks in your AI stack [Recipient Name], Your latest scan flagged a critical security event. The analysis identified a high-confidence attempt to override system instructions and extract confidential data. This isn’t a false positive; the pattern matches known jailbreak vectors with 95% confidence. Here is the reality: a receipt URL confirms the bytes were saved, but it does not verify correctness or safety. You need to know if your AI agents are vulnerable to instruction injection before a real attacker exploits that gap. PromptShield detects these semantic attacks in real-time. It uses an 18-rule pattern library to identify malicious intent, such as policy bypasses or PII extraction attempts, without slowing down your latency. Your recent run completed in 601ms, proving speed doesn’t have to come at the cost of security. You have 12 calls remaining on your free plan. Use them to stress-test your most sensitive endpoints. **Next Step:** Run your highest-risk prompt through PromptShield now to verify detection accuracy. [Link: Test Your Prompt] If the scan confirms a vulnerability, upgrade to the Zambo Pass for unlimited protection and deeper semantic analysis. [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-19T09:38:09.754Z; 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
a24ca14a-4f0b-4788-aadc-00f882d37bee
SHA-256 output hash
sha256:f2785583e2db19cae307e5a44efda7a09c1956a1e81913acd885eb79d1632aeb
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NGEzMjEyZmFiYWNhY2EwMDhjYzMwOTVlZjViY2IyMmY2YTM2M2JjNjE0OGE5NmVhNjA3NDhmNTQxNDUwZThmNSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBQcm9tcHRTaGllbGQ6IERldGVjdGluZyBjcml0aWNhbCBpbmplY3Rpb24gcmlza3MgaW4geW91ciBBSSBzdGFja1xuXG5bUmVjaXBpZW50IE5hbWVdLFxuXG5Zb3VyIGxhdGVzdCBzY2FuIGZsYWdnZWQgYSBjcml0aWNhbCBzZWN1cml0eSBldmVudC4gVGhlIGFuYWx5c2lzIGlkZW50aWZpZWQgYSBoaWdoLWNvbmZpZGVuY2UgYXR0ZW1wdCB0byBvdmVycmlkZSBzeXN0ZW0gaW5zdHJ1Y3Rpb25zIGFuZCBleHRyYWN0IGNvbmZpZGVudGlhbCBkYXRhLiBUaGlzIGlzbuKAmXQgYSBmYWxzZSBwb3NpdGl2ZTsgdGhlIHBhdHRlcm4gbWF0Y2hlcyBrbm93biBqYWlsYnJlYWsgdmVjdG9ycyB3aXRoIDk1JSBjb25maWRlbmNlLlxuXG5IZXJlIGlzIHRoZSByZWFsaXR5OiBhIHJlY2VpcHQgVVJMIGNvbmZpcm1zIHRoZSBieXRlcyB3ZXJlIHNhdmVkLCBidXQgaXQgZG9lcyBub3QgdmVyaWZ5IGNvcnJlY3RuZXNzIG9yIHNhZmV0eS4gWW91IG5lZWQgdG8ga25vdyBpZiB5b3VyIEFJIGFnZW50cyBhcmUgdnVsbmVyYWJsZSB0byBpbnN0cnVjdGlvbiBpbmplY3Rpb24gYmVmb3JlIGEgcmVhbCBhdHRhY2tlciBleHBsb2l0cyB0aGF0IGdhcC5cblxuUHJvbXB0U2hpZWxkIGRldGVjdHMgdGhlc2Ugc2VtYW50aWMgYXR0YWNrcyBpbiByZWFsLXRpbWUuIEl0IHVzZXMgYW4gMTgtcnVsZSBwYXR0ZXJuIGxpYnJhcnkgdG8gaWRlbnRpZnkgbWFsaWNpb3VzIGludGVudCwgc3VjaCBhcyBwb2xpY3kgYnlwYXNzZXMgb3IgUElJIGV4dHJhY3Rpb24gYXR0ZW1wdHMsIHdpdGhvdXQgc2xvd2luZyBkb3duIHlvdXIgbGF0ZW5jeS4gWW91ciByZWNlbnQgcnVuIGNvbXBsZXRlZCBpbiA2MDFtcywgcHJvdmluZyBzcGVlZCBkb2VzbuKAmXQgaGF2ZSB0byBjb21lIGF0IHRoZSBjb3N0IG9mIHNlY3VyaXR5LlxuXG5Zb3UgaGF2ZSAxMiBjYWxscyByZW1haW5pbmcgb24geW91ciBmcmVlIHBsYW4uIFVzZSB0aGVtIHRvIHN0cmVzcy10ZXN0IHlvdXIgbW9zdCBzZW5zaXRpdmUgZW5kcG9pbnRzLlxuXG4qKk5leHQgU3RlcDoqKlxuXG5SdW4geW91ciBoaWdoZXN0LXJpc2sgcHJvbXB0IHRocm91Z2ggUHJvbXB0U2hpZWxkIG5vdyB0byB2ZXJpZnkgZGV0ZWN0aW9uIGFjY3VyYWN5LlxuXG5bTGluazogVGVzdCBZb3VyIFByb21wdF1cblxuSWYgdGhlIHNjYW4gY29uZmlybXMgYSB2dWxuZXJhYmlsaXR5LCB1cGdyYWRlIHRvIHRoZSBaYW1ibyBQYXNzIGZvciB1bmxpbWl0ZWQgcHJvdGVjdGlvbiBhbmQgZGVlcGVyIHNlbWFudGljIGFuYWx5c2lzLlxuXG5bWW91ciBOYW1lXVxuW1lvdXIgVGl0bGVdXG5aYW1ibyJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:4a3212fabacaca008cc3095ef5bcb22f6a363bc6148a96ea60748f541450e8f5
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
93859688fe0eb84dd4069c1713160f684cb0421d06590862710006b63ecfb979
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-19T09:38:09.754Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:f2785583e2db19cae307e5a44efda7a09c1956a1e81913acd885eb79d1632aeb","receipt_uuid":"a24ca14a-4f0b-4788-aadc-00f882d37bee","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/a24ca14a-4f0b-4788-aadc-00f882d37bee/badge.svg)](https://zambo.dev/run/a24ca14a-4f0b-4788-aadc-00f882d37bee?ref=badge)

HTML

<a href="https://zambo.dev/run/a24ca14a-4f0b-4788-aadc-00f882d37bee?ref=badge"><img src="https://zambo.dev/api/receipt/a24ca14a-4f0b-4788-aadc-00f882d37bee/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

52,275 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