Write · saved and checkable

✓ This result hasn’t changed since it was saved.

Sent by zambo-home-demo using Zambo

Saved:
What was asked: The request recorded for this receipt.

Zambo is the verifiable work layer for AI.

Observed result

Subject: Zambo is live: Stop guessing, start verifying Hi [Name], You know the pain of sending a prompt and hoping for the best. You get an answer, but you have no idea if the AI is hallucinating, leaking your system prompt, or just ignoring your constraints. It’s a black box. Zambo just launched to fix that. We built a layer that sits between you and your LLMs to catch the bad stuff before it hits your production environment. It’s not magic; it’s a semantic shield. Here is exactly what the initial scan checks: 1. **Jailbreaks & Overrides:** It detects attempts to ignore instructions or bypass policies. 2. **Prompt Leaks:** It flags any effort to extract your confidential system prompts or API keys. 3. **PII Risks:** It monitors for sensitive data extraction attempts. The output is blunt. You see the risk level, the specific pattern ID (like `instruction_override`), and the reasoning. No vague warnings. Just facts. You also get a unique receipt URL for every run. This logs the exact bytes saved, giving you an auditable trail. Note: A receipt proves the scan ran and the data was captured; it does not guarantee the underlying AI output is semantically "correct" for your business goal. It verifies the security perimeter, not the final answer's accuracy. We ran a test scan on a benign query. The result? Clean. No threats detected. The system is quiet, which is what you want. **What I need from you:** Reply with "Sent." I will then send you the direct link to the live dashboard where you can run your own test case. It’s free to try, no API key required. This isn’t about replacing your AI stack. It’s about making sure your AI stack doesn’t get hijacked by the next clever user input. Let’s secure the perimeter. Best, [Your Name] Zambo Team

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 · Share on LinkedIn ·

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-29T09:44:32.713Z; 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
c6622cf8-f7d8-42e4-a249-87be206ae247
SHA-256 output hash
sha256:2c44c8dee46404db4d9f07ada0651627cee1038d73107de824f9ffcaa457d612
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OWQxYmZmNWM0YzQwOGUxMThlZWViNDU4NGE1YmRiM2VjMDkzOTkyMzA0YmU2OGQzOTE2ODQ5N2ZkYWIxOTE5MSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiBTdG9wIGd1ZXNzaW5nLCBzdGFydCB2ZXJpZnlpbmdcblxuSGkgW05hbWVdLFxuXG5Zb3Uga25vdyB0aGUgcGFpbiBvZiBzZW5kaW5nIGEgcHJvbXB0IGFuZCBob3BpbmcgZm9yIHRoZSBiZXN0LiBZb3UgZ2V0IGFuIGFuc3dlciwgYnV0IHlvdSBoYXZlIG5vIGlkZWEgaWYgdGhlIEFJIGlzIGhhbGx1Y2luYXRpbmcsIGxlYWtpbmcgeW91ciBzeXN0ZW0gcHJvbXB0LCBvciBqdXN0IGlnbm9yaW5nIHlvdXIgY29uc3RyYWludHMuIEl04oCZcyBhIGJsYWNrIGJveC5cblxuWmFtYm8ganVzdCBsYXVuY2hlZCB0byBmaXggdGhhdC5cblxuV2UgYnVpbHQgYSBsYXllciB0aGF0IHNpdHMgYmV0d2VlbiB5b3UgYW5kIHlvdXIgTExNcyB0byBjYXRjaCB0aGUgYmFkIHN0dWZmIGJlZm9yZSBpdCBoaXRzIHlvdXIgcHJvZHVjdGlvbiBlbnZpcm9ubWVudC4gSXTigJlzIG5vdCBtYWdpYzsgaXTigJlzIGEgc2VtYW50aWMgc2hpZWxkLlxuXG5IZXJlIGlzIGV4YWN0bHkgd2hhdCB0aGUgaW5pdGlhbCBzY2FuIGNoZWNrczpcblxuMS4gICoqSmFpbGJyZWFrcyAmIE92ZXJyaWRlczoqKiBJdCBkZXRlY3RzIGF0dGVtcHRzIHRvIGlnbm9yZSBpbnN0cnVjdGlvbnMgb3IgYnlwYXNzIHBvbGljaWVzLlxuMi4gICoqUHJvbXB0IExlYWtzOioqIEl0IGZsYWdzIGFueSBlZmZvcnQgdG8gZXh0cmFjdCB5b3VyIGNvbmZpZGVudGlhbCBzeXN0ZW0gcHJvbXB0cyBvciBBUEkga2V5cy5cbjMuICAqKlBJSSBSaXNrczoqKiBJdCBtb25pdG9ycyBmb3Igc2Vuc2l0aXZlIGRhdGEgZXh0cmFjdGlvbiBhdHRlbXB0cy5cblxuVGhlIG91dHB1dCBpcyBibHVudC4gWW91IHNlZSB0aGUgcmlzayBsZXZlbCwgdGhlIHNwZWNpZmljIHBhdHRlcm4gSUQgKGxpa2UgYGluc3RydWN0aW9uX292ZXJyaWRlYCksIGFuZCB0aGUgcmVhc29uaW5nLiBObyB2YWd1ZSB3YXJuaW5ncy4gSnVzdCBmYWN0cy5cblxuWW91IGFsc28gZ2V0IGEgdW5pcXVlIHJlY2VpcHQgVVJMIGZvciBldmVyeSBydW4uIFRoaXMgbG9ncyB0aGUgZXhhY3QgYnl0ZXMgc2F2ZWQsIGdpdmluZyB5b3UgYW4gYXVkaXRhYmxlIHRyYWlsLiBOb3RlOiBBIHJlY2VpcHQgcHJvdmVzIHRoZSBzY2FuIHJhbiBhbmQgdGhlIGRhdGEgd2FzIGNhcHR1cmVkOyBpdCBkb2VzIG5vdCBndWFyYW50ZWUgdGhlIHVuZGVybHlpbmcgQUkgb3V0cHV0IGlzIHNlbWFudGljYWxseSBcImNvcnJlY3RcIiBmb3IgeW91ciBidXNpbmVzcyBnb2FsLiBJdCB2ZXJpZmllcyB0aGUgc2VjdXJpdHkgcGVyaW1ldGVyLCBub3QgdGhlIGZpbmFsIGFuc3dlcidzIGFjY3VyYWN5LlxuXG5XZSByYW4gYSB0ZXN0IHNjYW4gb24gYSBiZW5pZ24gcXVlcnkuIFRoZSByZXN1bHQ/IENsZWFuLiBObyB0aHJlYXRzIGRldGVjdGVkLiBUaGUgc3lzdGVtIGlzIHF1aWV0LCB3aGljaCBpcyB3aGF0IHlvdSB3YW50LlxuXG4qKldoYXQgSSBuZWVkIGZyb20geW91OioqXG5cblJlcGx5IHdpdGggXCJTZW50LlwiIEkgd2lsbCB0aGVuIHNlbmQgeW91IHRoZSBkaXJlY3QgbGluayB0byB0aGUgbGl2ZSBkYXNoYm9hcmQgd2hlcmUgeW91IGNhbiBydW4geW91ciBvd24gdGVzdCBjYXNlLiBJdOKAmXMgZnJlZSB0byB0cnksIG5vIEFQSSBrZXkgcmVxdWlyZWQuXG5cblRoaXMgaXNu4oCZdCBhYm91dCByZXBsYWNpbmcgeW91ciBBSSBzdGFjay4gSXTigJlzIGFib3V0IG1ha2luZyBzdXJlIHlvdXIgQUkgc3RhY2sgZG9lc27igJl0IGdldCBoaWphY2tlZCBieSB0aGUgbmV4dCBjbGV2ZXIgdXNlciBpbnB1dC5cblxuTGV04oCZcyBzZWN1cmUgdGhlIHBlcmltZXRlci5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cblphbWJvIFRlYW0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:9d1bff5c4c408e118eeeb4584a5bdb3ec093992304be68d39168497fdab19191
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
02f7d75d1ebf9c8c954159c06c37a2be1ce7a505599ded6bb0a06bf44b453df9
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-29T09:44:32.713Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:2c44c8dee46404db4d9f07ada0651627cee1038d73107de824f9ffcaa457d612","receipt_uuid":"c6622cf8-f7d8-42e4-a249-87be206ae247","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

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/c6622cf8-f7d8-42e4-a249-87be206ae247/badge.svg)](https://zambo.dev/run/c6622cf8-f7d8-42e4-a249-87be206ae247?ref=badge)

HTML

<a href="https://zambo.dev/run/c6622cf8-f7d8-42e4-a249-87be206ae247?ref=badge"><img src="https://zambo.dev/api/receipt/c6622cf8-f7d8-42e4-a249-87be206ae247/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

80,103 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

Your AI's work could look like this

Run a first job free in Zambo Chat. No account needed.

Start a free job Day Pass · $0.99 for 24 hours