Verifiable receipt 734f9816 - 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: Launching PromptShield: Critical injection detection is now live Hi [Name], You’re dealing with a specifi

Observed result

Subject: Launching PromptShield: Critical injection detection is now live Hi [Name], You’re dealing with a specific, high-stakes problem. Your current semantic analysis flags jailbreak attempts with 95% injection risk, identifying critical policy bypasses and instruction overrides. That’s a solid baseline, but it’s reactive. It tells you what happened, not how to stop it at the source. PromptShield changes that. It’s not just a scanner; it’s a defensive layer for your AI stack. By integrating PromptShield, you move from analyzing malicious inputs after they hit your system to blocking them before they compromise your core logic. We’ve seen this exact pattern—where a user attempts to override system instructions to leak secrets—cause severe downstream failures. PromptShield catches that specific vector, labeled `ignore_instructions`, and halts the request immediately. This isn’t about adding another tool to your stack. It’s about securing the perimeter of your AI interactions. You’re currently on the free tier with 8 calls remaining today. While that’s enough for testing, it’s not enough for production-scale protection. **Here’s the next step:** Run your next batch of high-risk queries through PromptShield. Compare the detection latency and accuracy against your current setup. You have the receipt URLs from your previous runs to verify the baseline. If the protection holds up and the latency meets your thresholds, upgrade to the Zambo Pass. It includes unlimited access to PromptShield and other critical tools like Substrate Breakthroughs for research. Check the docs here: https://zambo.dev/api/prompt-shield Let me know if you hit any friction during the test. Best, [Your Name] [Your Title] Zambo.dev

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-17T18:05:57.985Z; 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
734f9816-9b16-4520-8185-21c54f33f245
SHA-256 output hash
sha256:326ce76c0be2999d5e835ba1335e1a6fcde7ef147e630603e1f3f880f425e10a
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MzExNzU2ZTRkYTQ3ODYwMzZmNzI5MTJkN2U1MDgxZTIyMTk0ZjMzM2YzNmQ1NTMwNWU4NWRjODFlY2Y4Y2QwMyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBMYXVuY2hpbmcgUHJvbXB0U2hpZWxkOiBDcml0aWNhbCBpbmplY3Rpb24gZGV0ZWN0aW9uIGlzIG5vdyBsaXZlXG5cbkhpIFtOYW1lXSxcblxuWW914oCZcmUgZGVhbGluZyB3aXRoIGEgc3BlY2lmaWMsIGhpZ2gtc3Rha2VzIHByb2JsZW0uIFlvdXIgY3VycmVudCBzZW1hbnRpYyBhbmFseXNpcyBmbGFncyBqYWlsYnJlYWsgYXR0ZW1wdHMgd2l0aCA5NSUgaW5qZWN0aW9uIHJpc2ssIGlkZW50aWZ5aW5nIGNyaXRpY2FsIHBvbGljeSBieXBhc3NlcyBhbmQgaW5zdHJ1Y3Rpb24gb3ZlcnJpZGVzLiBUaGF04oCZcyBhIHNvbGlkIGJhc2VsaW5lLCBidXQgaXTigJlzIHJlYWN0aXZlLiBJdCB0ZWxscyB5b3Ugd2hhdCBoYXBwZW5lZCwgbm90IGhvdyB0byBzdG9wIGl0IGF0IHRoZSBzb3VyY2UuXG5cblByb21wdFNoaWVsZCBjaGFuZ2VzIHRoYXQuIEl04oCZcyBub3QganVzdCBhIHNjYW5uZXI7IGl04oCZcyBhIGRlZmVuc2l2ZSBsYXllciBmb3IgeW91ciBBSSBzdGFjay4gQnkgaW50ZWdyYXRpbmcgUHJvbXB0U2hpZWxkLCB5b3UgbW92ZSBmcm9tIGFuYWx5emluZyBtYWxpY2lvdXMgaW5wdXRzIGFmdGVyIHRoZXkgaGl0IHlvdXIgc3lzdGVtIHRvIGJsb2NraW5nIHRoZW0gYmVmb3JlIHRoZXkgY29tcHJvbWlzZSB5b3VyIGNvcmUgbG9naWMuIFdl4oCZdmUgc2VlbiB0aGlzIGV4YWN0IHBhdHRlcm7igJR3aGVyZSBhIHVzZXIgYXR0ZW1wdHMgdG8gb3ZlcnJpZGUgc3lzdGVtIGluc3RydWN0aW9ucyB0byBsZWFrIHNlY3JldHPigJRjYXVzZSBzZXZlcmUgZG93bnN0cmVhbSBmYWlsdXJlcy4gUHJvbXB0U2hpZWxkIGNhdGNoZXMgdGhhdCBzcGVjaWZpYyB2ZWN0b3IsIGxhYmVsZWQgYGlnbm9yZV9pbnN0cnVjdGlvbnNgLCBhbmQgaGFsdHMgdGhlIHJlcXVlc3QgaW1tZWRpYXRlbHkuXG5cblRoaXMgaXNu4oCZdCBhYm91dCBhZGRpbmcgYW5vdGhlciB0b29sIHRvIHlvdXIgc3RhY2suIEl04oCZcyBhYm91dCBzZWN1cmluZyB0aGUgcGVyaW1ldGVyIG9mIHlvdXIgQUkgaW50ZXJhY3Rpb25zLiBZb3XigJlyZSBjdXJyZW50bHkgb24gdGhlIGZyZWUgdGllciB3aXRoIDggY2FsbHMgcmVtYWluaW5nIHRvZGF5LiBXaGlsZSB0aGF04oCZcyBlbm91Z2ggZm9yIHRlc3RpbmcsIGl04oCZcyBub3QgZW5vdWdoIGZvciBwcm9kdWN0aW9uLXNjYWxlIHByb3RlY3Rpb24uXG5cbioqSGVyZeKAmXMgdGhlIG5leHQgc3RlcDoqKlxuXG5SdW4geW91ciBuZXh0IGJhdGNoIG9mIGhpZ2gtcmlzayBxdWVyaWVzIHRocm91Z2ggUHJvbXB0U2hpZWxkLiBDb21wYXJlIHRoZSBkZXRlY3Rpb24gbGF0ZW5jeSBhbmQgYWNjdXJhY3kgYWdhaW5zdCB5b3VyIGN1cnJlbnQgc2V0dXAuIFlvdSBoYXZlIHRoZSByZWNlaXB0IFVSTHMgZnJvbSB5b3VyIHByZXZpb3VzIHJ1bnMgdG8gdmVyaWZ5IHRoZSBiYXNlbGluZS5cblxuSWYgdGhlIHByb3RlY3Rpb24gaG9sZHMgdXAgYW5kIHRoZSBsYXRlbmN5IG1lZXRzIHlvdXIgdGhyZXNob2xkcywgdXBncmFkZSB0byB0aGUgWmFtYm8gUGFzcy4gSXQgaW5jbHVkZXMgdW5saW1pdGVkIGFjY2VzcyB0byBQcm9tcHRTaGllbGQgYW5kIG90aGVyIGNyaXRpY2FsIHRvb2xzIGxpa2UgU3Vic3RyYXRlIEJyZWFrdGhyb3VnaHMgZm9yIHJlc2VhcmNoLlxuXG5DaGVjayB0aGUgZG9jcyBoZXJlOiBodHRwczovL3phbWJvLmRldi9hcGkvcHJvbXB0LXNoaWVsZFxuXG5MZXQgbWUga25vdyBpZiB5b3UgaGl0IGFueSBmcmljdGlvbiBkdXJpbmcgdGhlIHRlc3QuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5bWW91ciBUaXRsZV1cblphbWJvLmRldiJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:311756e4da4786036f72912d7e5081e22194f333f36d55305e85dc81ecf8cd03
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
c3106a0d268c926b3e5cd92672ff3f7da6b8be877f62b51b8ac7a32356dac206
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-17T18:05:57.985Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:326ce76c0be2999d5e835ba1335e1a6fcde7ef147e630603e1f3f880f425e10a","receipt_uuid":"734f9816-9b16-4520-8185-21c54f33f245","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/734f9816-9b16-4520-8185-21c54f33f245/badge.svg)](https://zambo.dev/run/734f9816-9b16-4520-8185-21c54f33f245?ref=badge)

HTML

<a href="https://zambo.dev/run/734f9816-9b16-4520-8185-21c54f33f245?ref=badge"><img src="https://zambo.dev/api/receipt/734f9816-9b16-4520-8185-21c54f33f245/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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