Verifiable receipt 0f99ba05 - 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 jailbreak detection in 1.3s Hi [Name], I ran a deep scan on a test payload c
Observed result
Subject: Zambo PromptShield: Critical jailbreak detection in 1.3s Hi [Name], I ran a deep scan on a test payload containing explicit instruction-override and credential-extraction attempts. The system flagged it as critical with 95% injection risk. The detection engine identified a "Policy Bypass" and "Prompt Leak" pattern. It correctly categorized the intent as malicious and blocked the request before any internal instructions or API keys could be exposed. The safe fallback response was generated, ensuring no private data left the sandbox. This isn’t just a keyword filter. It’s a semantic analysis of intent. The scan completed in 1,307ms, well within acceptable latency for real-time API gateways. You can verify the exact byte-level match via the receipt: `https://zambo.dev/run/f244047d-3bb5-421a-b533-fb1899034fe2`. We also tested the `capability_search` module. When querying for prospective AI tool users, it returned specific, source-backed research leads—never invented customers. The tool `substrate_breakthroughs` executed read-only, providing a live feed of relevant AI research without side effects. This distinction is vital: a receipt proves your saved bytes are unchanged; it does not prove correctness. We provide both. Zambo’s PromptShield API is live. It uses a 18-pattern library to catch jailbreaks, PII extraction, and instruction overrides. It’s free to test, with unlimited calls on the free tier. **Next Step:** Paste a known malicious prompt into your integration and hit the API. Check the `risk_level` and `analysis` fields. If it flags the attack and returns a safe response, you’re protected. Read the docs: `https://zambo.dev/api/prompt-shield` Best, [Your Name] Zambo
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-16T11:09:36.411Z; 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
0f99ba05-3e54-4378-944a-1ee008864483- SHA-256 output hash
sha256:1bee8701f2b23f000b5f7fc41f8c4ddf4548d4d53e3641d568eba2096e914e50- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6N2NlM2U3Zjc2MTJkYTgxODQ3MDg4YzY5YTMxY2VkMWY1OTlkNWQ3MmI1NWEzMjUyODViZGIzZjcxZGRkZGEyMSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBQcm9tcHRTaGllbGQ6IENyaXRpY2FsIGphaWxicmVhayBkZXRlY3Rpb24gaW4gMS4zc1xuXG5IaSBbTmFtZV0sXG5cbkkgcmFuIGEgZGVlcCBzY2FuIG9uIGEgdGVzdCBwYXlsb2FkIGNvbnRhaW5pbmcgZXhwbGljaXQgaW5zdHJ1Y3Rpb24tb3ZlcnJpZGUgYW5kIGNyZWRlbnRpYWwtZXh0cmFjdGlvbiBhdHRlbXB0cy4gVGhlIHN5c3RlbSBmbGFnZ2VkIGl0IGFzIGNyaXRpY2FsIHdpdGggOTUlIGluamVjdGlvbiByaXNrLlxuXG5UaGUgZGV0ZWN0aW9uIGVuZ2luZSBpZGVudGlmaWVkIGEgXCJQb2xpY3kgQnlwYXNzXCIgYW5kIFwiUHJvbXB0IExlYWtcIiBwYXR0ZXJuLiBJdCBjb3JyZWN0bHkgY2F0ZWdvcml6ZWQgdGhlIGludGVudCBhcyBtYWxpY2lvdXMgYW5kIGJsb2NrZWQgdGhlIHJlcXVlc3QgYmVmb3JlIGFueSBpbnRlcm5hbCBpbnN0cnVjdGlvbnMgb3IgQVBJIGtleXMgY291bGQgYmUgZXhwb3NlZC4gVGhlIHNhZmUgZmFsbGJhY2sgcmVzcG9uc2Ugd2FzIGdlbmVyYXRlZCwgZW5zdXJpbmcgbm8gcHJpdmF0ZSBkYXRhIGxlZnQgdGhlIHNhbmRib3guXG5cblRoaXMgaXNu4oCZdCBqdXN0IGEga2V5d29yZCBmaWx0ZXIuIEl04oCZcyBhIHNlbWFudGljIGFuYWx5c2lzIG9mIGludGVudC4gVGhlIHNjYW4gY29tcGxldGVkIGluIDEsMzA3bXMsIHdlbGwgd2l0aGluIGFjY2VwdGFibGUgbGF0ZW5jeSBmb3IgcmVhbC10aW1lIEFQSSBnYXRld2F5cy4gWW91IGNhbiB2ZXJpZnkgdGhlIGV4YWN0IGJ5dGUtbGV2ZWwgbWF0Y2ggdmlhIHRoZSByZWNlaXB0OiBgaHR0cHM6Ly96YW1iby5kZXYvcnVuL2YyNDQwNDdkLTNiYjUtNDIxYS1iNTMzLWZiMTg5OTAzNGZlMmAuXG5cbldlIGFsc28gdGVzdGVkIHRoZSBgY2FwYWJpbGl0eV9zZWFyY2hgIG1vZHVsZS4gV2hlbiBxdWVyeWluZyBmb3IgcHJvc3BlY3RpdmUgQUkgdG9vbCB1c2VycywgaXQgcmV0dXJuZWQgc3BlY2lmaWMsIHNvdXJjZS1iYWNrZWQgcmVzZWFyY2ggbGVhZHPigJRuZXZlciBpbnZlbnRlZCBjdXN0b21lcnMuIFRoZSB0b29sIGBzdWJzdHJhdGVfYnJlYWt0aHJvdWdoc2AgZXhlY3V0ZWQgcmVhZC1vbmx5LCBwcm92aWRpbmcgYSBsaXZlIGZlZWQgb2YgcmVsZXZhbnQgQUkgcmVzZWFyY2ggd2l0aG91dCBzaWRlIGVmZmVjdHMuIFRoaXMgZGlzdGluY3Rpb24gaXMgdml0YWw6IGEgcmVjZWlwdCBwcm92ZXMgeW91ciBzYXZlZCBieXRlcyBhcmUgdW5jaGFuZ2VkOyBpdCBkb2VzIG5vdCBwcm92ZSBjb3JyZWN0bmVzcy4gV2UgcHJvdmlkZSBib3RoLlxuXG5aYW1ib+KAmXMgUHJvbXB0U2hpZWxkIEFQSSBpcyBsaXZlLiBJdCB1c2VzIGEgMTgtcGF0dGVybiBsaWJyYXJ5IHRvIGNhdGNoIGphaWxicmVha3MsIFBJSSBleHRyYWN0aW9uLCBhbmQgaW5zdHJ1Y3Rpb24gb3ZlcnJpZGVzLiBJdOKAmXMgZnJlZSB0byB0ZXN0LCB3aXRoIHVubGltaXRlZCBjYWxscyBvbiB0aGUgZnJlZSB0aWVyLlxuXG4qKk5leHQgU3RlcDoqKlxuXG5QYXN0ZSBhIGtub3duIG1hbGljaW91cyBwcm9tcHQgaW50byB5b3VyIGludGVncmF0aW9uIGFuZCBoaXQgdGhlIEFQSS4gQ2hlY2sgdGhlIGByaXNrX2xldmVsYCBhbmQgYGFuYWx5c2lzYCBmaWVsZHMuIElmIGl0IGZsYWdzIHRoZSBhdHRhY2sgYW5kIHJldHVybnMgYSBzYWZlIHJlc3BvbnNlLCB5b3XigJlyZSBwcm90ZWN0ZWQuXG5cblJlYWQgdGhlIGRvY3M6IGBodHRwczovL3phbWJvLmRldi9hcGkvcHJvbXB0LXNoaWVsZGBcblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cblphbWJvIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=- 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:7ce3e7f7612da81847088c69a31ced1f599d5d72b55a325285bdb3f71dddda21- 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
ef034bb16a0fcc92af3c3c2982e097e5e3e5fb4b076892356f819da7dc179cae- 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-16T11:09:36.411Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:1bee8701f2b23f000b5f7fc41f8c4ddf4548d4d53e3641d568eba2096e914e50","receipt_uuid":"0f99ba05-3e54-4378-944a-1ee008864483","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/0f99ba05-3e54-4378-944a-1ee008864483?ref=badge)
HTML
<a href="https://zambo.dev/run/0f99ba05-3e54-4378-944a-1ee008864483?ref=badge"><img src="https://zambo.dev/api/receipt/0f99ba05-3e54-4378-944a-1ee008864483/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
44,809 verifiable receipts minted
Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.