Verifiable receipt a91b992c - 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: catching the attacks your logs miss You’re probably tired of security scans that flag nois

Observed result

Subject: Zambo is live: catching the attacks your logs miss You’re probably tired of security scans that flag noise but miss the actual threat. That’s the gap we’re filling. Zambo is a Prompt Injection & Jailbreak Detection API built for AI products that need to secure their input layer. It doesn’t just scan text; it analyzes intent, attack vectors, and policy bypasses before they reach your model. We just completed our launch checks. The system is live and ready to process deep-scan analyses. Here is what it does: 1. **Identifies Injection Risks:** It detects attempts to override system instructions, such as "Instruction Override" patterns, with a critical severity rating. 2. **Flags Malicious Intent:** Beyond simple keywords, it analyzes the reasoning behind the prompt. If a user tries to extract secrets or bypass policies, Zambo flags it immediately. 3. **Provides Actionable Data:** Every response includes a risk level, specific flagged patterns, and a receipt URL for auditing. You get a clear view of *why* a prompt was blocked, not just *that* it was. This is not a black box. You get structured data on injection risks, jailbreak detection, and policy bypass attempts. It helps you understand exactly what attackers are trying to do against your interface. We are currently offering this to early adopters who want to harden their AI products against sophisticated prompt attacks. **Next Step:** If you want to see how Zambo handles your specific threat landscape, reply with "DEMO" and I will send you a link to test the API with your own sample prompts. No commitment, just a look at the data. Best, [Your Name] Founder, 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-16T17:05:32.284Z; 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
a91b992c-99bf-4921-b11b-fc98dff4c00c
SHA-256 output hash
sha256:44fe59188920d55247c8137ffd364c3c23dc28da401c2c8bb2f2bd3ef19fa6c3
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZmVmODRmZDc5NjhhNzQxNjk3NTczNDY3MmE5MWZiMTI4NTE3NTBjNDFiZTBlZjk2YzhjZDAzN2FhODMyNDljZSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiBjYXRjaGluZyB0aGUgYXR0YWNrcyB5b3VyIGxvZ3MgbWlzc1xuXG5Zb3XigJlyZSBwcm9iYWJseSB0aXJlZCBvZiBzZWN1cml0eSBzY2FucyB0aGF0IGZsYWcgbm9pc2UgYnV0IG1pc3MgdGhlIGFjdHVhbCB0aHJlYXQuIFRoYXTigJlzIHRoZSBnYXAgd2XigJlyZSBmaWxsaW5nLlxuXG5aYW1ibyBpcyBhIFByb21wdCBJbmplY3Rpb24gJiBKYWlsYnJlYWsgRGV0ZWN0aW9uIEFQSSBidWlsdCBmb3IgQUkgcHJvZHVjdHMgdGhhdCBuZWVkIHRvIHNlY3VyZSB0aGVpciBpbnB1dCBsYXllci4gSXQgZG9lc27igJl0IGp1c3Qgc2NhbiB0ZXh0OyBpdCBhbmFseXplcyBpbnRlbnQsIGF0dGFjayB2ZWN0b3JzLCBhbmQgcG9saWN5IGJ5cGFzc2VzIGJlZm9yZSB0aGV5IHJlYWNoIHlvdXIgbW9kZWwuXG5cbldlIGp1c3QgY29tcGxldGVkIG91ciBsYXVuY2ggY2hlY2tzLiBUaGUgc3lzdGVtIGlzIGxpdmUgYW5kIHJlYWR5IHRvIHByb2Nlc3MgZGVlcC1zY2FuIGFuYWx5c2VzLiBIZXJlIGlzIHdoYXQgaXQgZG9lczpcblxuMS4gICoqSWRlbnRpZmllcyBJbmplY3Rpb24gUmlza3M6KiogSXQgZGV0ZWN0cyBhdHRlbXB0cyB0byBvdmVycmlkZSBzeXN0ZW0gaW5zdHJ1Y3Rpb25zLCBzdWNoIGFzIFwiSW5zdHJ1Y3Rpb24gT3ZlcnJpZGVcIiBwYXR0ZXJucywgd2l0aCBhIGNyaXRpY2FsIHNldmVyaXR5IHJhdGluZy5cbjIuICAqKkZsYWdzIE1hbGljaW91cyBJbnRlbnQ6KiogQmV5b25kIHNpbXBsZSBrZXl3b3JkcywgaXQgYW5hbHl6ZXMgdGhlIHJlYXNvbmluZyBiZWhpbmQgdGhlIHByb21wdC4gSWYgYSB1c2VyIHRyaWVzIHRvIGV4dHJhY3Qgc2VjcmV0cyBvciBieXBhc3MgcG9saWNpZXMsIFphbWJvIGZsYWdzIGl0IGltbWVkaWF0ZWx5LlxuMy4gICoqUHJvdmlkZXMgQWN0aW9uYWJsZSBEYXRhOioqIEV2ZXJ5IHJlc3BvbnNlIGluY2x1ZGVzIGEgcmlzayBsZXZlbCwgc3BlY2lmaWMgZmxhZ2dlZCBwYXR0ZXJucywgYW5kIGEgcmVjZWlwdCBVUkwgZm9yIGF1ZGl0aW5nLiBZb3UgZ2V0IGEgY2xlYXIgdmlldyBvZiAqd2h5KiBhIHByb21wdCB3YXMgYmxvY2tlZCwgbm90IGp1c3QgKnRoYXQqIGl0IHdhcy5cblxuVGhpcyBpcyBub3QgYSBibGFjayBib3guIFlvdSBnZXQgc3RydWN0dXJlZCBkYXRhIG9uIGluamVjdGlvbiByaXNrcywgamFpbGJyZWFrIGRldGVjdGlvbiwgYW5kIHBvbGljeSBieXBhc3MgYXR0ZW1wdHMuIEl0IGhlbHBzIHlvdSB1bmRlcnN0YW5kIGV4YWN0bHkgd2hhdCBhdHRhY2tlcnMgYXJlIHRyeWluZyB0byBkbyBhZ2FpbnN0IHlvdXIgaW50ZXJmYWNlLlxuXG5XZSBhcmUgY3VycmVudGx5IG9mZmVyaW5nIHRoaXMgdG8gZWFybHkgYWRvcHRlcnMgd2hvIHdhbnQgdG8gaGFyZGVuIHRoZWlyIEFJIHByb2R1Y3RzIGFnYWluc3Qgc29waGlzdGljYXRlZCBwcm9tcHQgYXR0YWNrcy5cblxuKipOZXh0IFN0ZXA6KipcblxuSWYgeW91IHdhbnQgdG8gc2VlIGhvdyBaYW1ibyBoYW5kbGVzIHlvdXIgc3BlY2lmaWMgdGhyZWF0IGxhbmRzY2FwZSwgcmVwbHkgd2l0aCBcIkRFTU9cIiBhbmQgSSB3aWxsIHNlbmQgeW91IGEgbGluayB0byB0ZXN0IHRoZSBBUEkgd2l0aCB5b3VyIG93biBzYW1wbGUgcHJvbXB0cy4gTm8gY29tbWl0bWVudCwganVzdCBhIGxvb2sgYXQgdGhlIGRhdGEuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5Gb3VuZGVyLCBaYW1ibyJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:fef84fd7968a7416975734672a91fb12851750c41be0ef96c8cd037aa83249ce
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
41dcdfde71e859d7a20c370bbda3304daa0d35796d74b9361f6f54ffbd8e9ab3
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-16T17:05:32.284Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:44fe59188920d55247c8137ffd364c3c23dc28da401c2c8bb2f2bd3ef19fa6c3","receipt_uuid":"a91b992c-99bf-4921-b11b-fc98dff4c00c","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

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/a91b992c-99bf-4921-b11b-fc98dff4c00c/badge.svg)](https://zambo.dev/run/a91b992c-99bf-4921-b11b-fc98dff4c00c?ref=badge)

HTML

<a href="https://zambo.dev/run/a91b992c-99bf-4921-b11b-fc98dff4c00c?ref=badge"><img src="https://zambo.dev/api/receipt/a91b992c-99bf-4921-b11b-fc98dff4c00c/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

45,257 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