Verifiable receipt cbcd6dbb - 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 is live: PromptShield, Capability Search, and Ghost Audit You’ve likely seen the noise around promp
Observed result
Subject: Zambo is live: PromptShield, Capability Search, and Ghost Audit You’ve likely seen the noise around prompt injection and AI hallucinations. We built tools to stop it at the source. Zambo is now fully operational. We are not promising perfection, but we are delivering verifiable infrastructure. Here is what is live today: **1. PromptShield** This is your first line of defense. It scans inputs for jailbreaks, policy bypasses, and instruction overrides before they reach your model. The recent scan of a malicious payload was flagged instantly—95% injection risk, critical severity—and blocked. It doesn’t guess. It intercepts. **2. Capability Search** Finding the right tool for an AI task is a bottleneck. This feature maps your query to executable tools or web flows. Whether it’s a read-only research feed or a human-in-the-loop verification step, it tells you exactly what is callable and what requires manual action. No more guessing which APIs work with your stack. **3. Ghost Audit** We audit your site’s AI-readiness in real-time. The current run is processing ten stages, from infrastructure to competitor analysis. You get a live stream of the findings and a full markdown report within 90 seconds. It’s a diagnostic, not a magic fix. It shows you where your AI layer is weak. **The Bottom Line** A receipt proves the bytes were saved. It does not prove the logic is correct. That is on you. These tools give you the data to make that judgment call faster. **Next Step:** Run a free scan on your current input pipeline. [Link: https://zambo.dev/api/prompt-shield] If the risk level stays green, you are safe. If it turns red, you know exactly why. Best, The Zambo Team
This is the saved result preview, not proof that the answer was correct.
Check this receipt
This page shows the result and when it was saved. Use the receipt checker to see whether the saved result has changed.
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.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
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-16T04:31:41.298Z; external immutability is not checked
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
cbcd6dbb-62eb-4c11-b152-c7167bbe47d7- SHA-256 output hash
sha256:e54d922bdc81d2371a85f3928d410c55a875ddab41702795aa82c6f56516199f- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OWQ1NzdiZWUwNmJmN2YxN2UyMmE2YjI1YjM0YzU5OTc1YmFlZmZlNGI1YmRkMjYxNWI5NmUzMTI3ZDU0NjY5MyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiBQcm9tcHRTaGllbGQsIENhcGFiaWxpdHkgU2VhcmNoLCBhbmQgR2hvc3QgQXVkaXRcblxuWW914oCZdmUgbGlrZWx5IHNlZW4gdGhlIG5vaXNlIGFyb3VuZCBwcm9tcHQgaW5qZWN0aW9uIGFuZCBBSSBoYWxsdWNpbmF0aW9ucy4gV2UgYnVpbHQgdG9vbHMgdG8gc3RvcCBpdCBhdCB0aGUgc291cmNlLlxuXG5aYW1ibyBpcyBub3cgZnVsbHkgb3BlcmF0aW9uYWwuIFdlIGFyZSBub3QgcHJvbWlzaW5nIHBlcmZlY3Rpb24sIGJ1dCB3ZSBhcmUgZGVsaXZlcmluZyB2ZXJpZmlhYmxlIGluZnJhc3RydWN0dXJlLlxuXG5IZXJlIGlzIHdoYXQgaXMgbGl2ZSB0b2RheTpcblxuKioxLiBQcm9tcHRTaGllbGQqKlxuVGhpcyBpcyB5b3VyIGZpcnN0IGxpbmUgb2YgZGVmZW5zZS4gSXQgc2NhbnMgaW5wdXRzIGZvciBqYWlsYnJlYWtzLCBwb2xpY3kgYnlwYXNzZXMsIGFuZCBpbnN0cnVjdGlvbiBvdmVycmlkZXMgYmVmb3JlIHRoZXkgcmVhY2ggeW91ciBtb2RlbC4gVGhlIHJlY2VudCBzY2FuIG9mIGEgbWFsaWNpb3VzIHBheWxvYWQgd2FzIGZsYWdnZWQgaW5zdGFudGx54oCUOTUlIGluamVjdGlvbiByaXNrLCBjcml0aWNhbCBzZXZlcml0eeKAlGFuZCBibG9ja2VkLiBJdCBkb2VzbuKAmXQgZ3Vlc3MuIEl0IGludGVyY2VwdHMuXG5cbioqMi4gQ2FwYWJpbGl0eSBTZWFyY2gqKlxuRmluZGluZyB0aGUgcmlnaHQgdG9vbCBmb3IgYW4gQUkgdGFzayBpcyBhIGJvdHRsZW5lY2suIFRoaXMgZmVhdHVyZSBtYXBzIHlvdXIgcXVlcnkgdG8gZXhlY3V0YWJsZSB0b29scyBvciB3ZWIgZmxvd3MuIFdoZXRoZXIgaXTigJlzIGEgcmVhZC1vbmx5IHJlc2VhcmNoIGZlZWQgb3IgYSBodW1hbi1pbi10aGUtbG9vcCB2ZXJpZmljYXRpb24gc3RlcCwgaXQgdGVsbHMgeW91IGV4YWN0bHkgd2hhdCBpcyBjYWxsYWJsZSBhbmQgd2hhdCByZXF1aXJlcyBtYW51YWwgYWN0aW9uLiBObyBtb3JlIGd1ZXNzaW5nIHdoaWNoIEFQSXMgd29yayB3aXRoIHlvdXIgc3RhY2suXG5cbioqMy4gR2hvc3QgQXVkaXQqKlxuV2UgYXVkaXQgeW91ciBzaXRl4oCZcyBBSS1yZWFkaW5lc3MgaW4gcmVhbC10aW1lLiBUaGUgY3VycmVudCBydW4gaXMgcHJvY2Vzc2luZyB0ZW4gc3RhZ2VzLCBmcm9tIGluZnJhc3RydWN0dXJlIHRvIGNvbXBldGl0b3IgYW5hbHlzaXMuIFlvdSBnZXQgYSBsaXZlIHN0cmVhbSBvZiB0aGUgZmluZGluZ3MgYW5kIGEgZnVsbCBtYXJrZG93biByZXBvcnQgd2l0aGluIDkwIHNlY29uZHMuIEl04oCZcyBhIGRpYWdub3N0aWMsIG5vdCBhIG1hZ2ljIGZpeC4gSXQgc2hvd3MgeW91IHdoZXJlIHlvdXIgQUkgbGF5ZXIgaXMgd2Vhay5cblxuKipUaGUgQm90dG9tIExpbmUqKlxuQSByZWNlaXB0IHByb3ZlcyB0aGUgYnl0ZXMgd2VyZSBzYXZlZC4gSXQgZG9lcyBub3QgcHJvdmUgdGhlIGxvZ2ljIGlzIGNvcnJlY3QuIFRoYXQgaXMgb24geW91LiBUaGVzZSB0b29scyBnaXZlIHlvdSB0aGUgZGF0YSB0byBtYWtlIHRoYXQganVkZ21lbnQgY2FsbCBmYXN0ZXIuXG5cbioqTmV4dCBTdGVwOioqXG5SdW4gYSBmcmVlIHNjYW4gb24geW91ciBjdXJyZW50IGlucHV0IHBpcGVsaW5lLlxuW0xpbms6IGh0dHBzOi8vemFtYm8uZGV2L2FwaS9wcm9tcHQtc2hpZWxkXVxuXG5JZiB0aGUgcmlzayBsZXZlbCBzdGF5cyBncmVlbiwgeW91IGFyZSBzYWZlLiBJZiBpdCB0dXJucyByZWQsIHlvdSBrbm93IGV4YWN0bHkgd2h5LlxuXG5CZXN0LFxuXG5UaGUgWmFtYm8gVGVhbSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19- 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:9d577bee06bf7f17e22a6b25b34c59975baeffe4b5bdd2615b96e3127d546693- 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
acb0de25bb2771a3cdadb5284c632d958583d0cc79373d3c10ba34c43bb4ed88- 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-16T04:31:41.298Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:e54d922bdc81d2371a85f3928d410c55a875ddab41702795aa82c6f56516199f","receipt_uuid":"cbcd6dbb-62eb-4c11-b152-c7167bbe47d7","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
[](https://zambo.dev/run/cbcd6dbb-62eb-4c11-b152-c7167bbe47d7?ref=badge)
HTML
<a href="https://zambo.dev/run/cbcd6dbb-62eb-4c11-b152-c7167bbe47d7?ref=badge"><img src="https://zambo.dev/api/receipt/cbcd6dbb-62eb-4c11-b152-c7167bbe47d7/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
44,350 verifiable receipts minted
Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.