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: Verified AI workflows Hi [Name], No more guessing if your AI output is safe. Zambo’s PromptShield just finished its first deep scan, and the results are ready for review. We ran a critical security check on a test payload using our semantic analysis engine. The system flagged a high-severity injection attempt and a prompt leak in under 1.3 seconds. It identified the specific attack vector, blocked the malicious instruction, and generated a verifiable receipt proving the saved bytes were unchanged. This isn’t just a filter. It’s a layer of cryptographic trust for your AI interactions. We’re opening up access to a small group of early users who want to secure their AI workflows before they go public. We aren’t selling seats yet; we’re gathering feedback on how the shield integrates with your existing tools. **Next step:** If you want to see the full report from this scan or test your own prompts against our engine, reply with the word **SHIELD**. I’ll send you a direct link to the dashboard where you can run your first free check. No commitment. Just a look at what’s protecting your data right now. 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-27T04:41:00.571Z; 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
2646e1c6-d801-4202-9ae2-ada1e57ae8ac
SHA-256 output hash
sha256:8753b64b54948c99cf086311b8e550c51ee113e5dd8c1645ed285d039d87f5f0
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZTc0ODczNzdiNDI0MDdjZjJkZDI5MGVjNDc2M2Y3MGMzYjE0ZjdjY2Q2ZmJiMzBkODU3ZmI5MzA2Yjc1ZDNiMCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiIqKlN1YmplY3Q6KiogWmFtYm8gaXMgbGl2ZTogVmVyaWZpZWQgQUkgd29ya2Zsb3dzXG5cbkhpIFtOYW1lXSxcblxuTm8gbW9yZSBndWVzc2luZyBpZiB5b3VyIEFJIG91dHB1dCBpcyBzYWZlLiBaYW1ib+KAmXMgUHJvbXB0U2hpZWxkIGp1c3QgZmluaXNoZWQgaXRzIGZpcnN0IGRlZXAgc2NhbiwgYW5kIHRoZSByZXN1bHRzIGFyZSByZWFkeSBmb3IgcmV2aWV3LlxuXG5XZSByYW4gYSBjcml0aWNhbCBzZWN1cml0eSBjaGVjayBvbiBhIHRlc3QgcGF5bG9hZCB1c2luZyBvdXIgc2VtYW50aWMgYW5hbHlzaXMgZW5naW5lLiBUaGUgc3lzdGVtIGZsYWdnZWQgYSBoaWdoLXNldmVyaXR5IGluamVjdGlvbiBhdHRlbXB0IGFuZCBhIHByb21wdCBsZWFrIGluIHVuZGVyIDEuMyBzZWNvbmRzLiBJdCBpZGVudGlmaWVkIHRoZSBzcGVjaWZpYyBhdHRhY2sgdmVjdG9yLCBibG9ja2VkIHRoZSBtYWxpY2lvdXMgaW5zdHJ1Y3Rpb24sIGFuZCBnZW5lcmF0ZWQgYSB2ZXJpZmlhYmxlIHJlY2VpcHQgcHJvdmluZyB0aGUgc2F2ZWQgYnl0ZXMgd2VyZSB1bmNoYW5nZWQuXG5cblRoaXMgaXNu4oCZdCBqdXN0IGEgZmlsdGVyLiBJdOKAmXMgYSBsYXllciBvZiBjcnlwdG9ncmFwaGljIHRydXN0IGZvciB5b3VyIEFJIGludGVyYWN0aW9ucy5cblxuV2XigJlyZSBvcGVuaW5nIHVwIGFjY2VzcyB0byBhIHNtYWxsIGdyb3VwIG9mIGVhcmx5IHVzZXJzIHdobyB3YW50IHRvIHNlY3VyZSB0aGVpciBBSSB3b3JrZmxvd3MgYmVmb3JlIHRoZXkgZ28gcHVibGljLiBXZSBhcmVu4oCZdCBzZWxsaW5nIHNlYXRzIHlldDsgd2XigJlyZSBnYXRoZXJpbmcgZmVlZGJhY2sgb24gaG93IHRoZSBzaGllbGQgaW50ZWdyYXRlcyB3aXRoIHlvdXIgZXhpc3RpbmcgdG9vbHMuXG5cbioqTmV4dCBzdGVwOioqXG5cbklmIHlvdSB3YW50IHRvIHNlZSB0aGUgZnVsbCByZXBvcnQgZnJvbSB0aGlzIHNjYW4gb3IgdGVzdCB5b3VyIG93biBwcm9tcHRzIGFnYWluc3Qgb3VyIGVuZ2luZSwgcmVwbHkgd2l0aCB0aGUgd29yZCAqKlNISUVMRCoqLiBJ4oCZbGwgc2VuZCB5b3UgYSBkaXJlY3QgbGluayB0byB0aGUgZGFzaGJvYXJkIHdoZXJlIHlvdSBjYW4gcnVuIHlvdXIgZmlyc3QgZnJlZSBjaGVjay5cblxuTm8gY29tbWl0bWVudC4gSnVzdCBhIGxvb2sgYXQgd2hhdOKAmXMgcHJvdGVjdGluZyB5b3VyIGRhdGEgcmlnaHQgbm93LlxuXG5CZXN0LFxuXG5bWW91ciBOYW1lXVxuWmFtYm8gVGVhbSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:e7487377b42407cf2dd290ec4763f70c3b14f7ccd6fbb30d857fb9306b75d3b0
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
b7c8d1619575bfea7e43d16db2dba7edb142614be8843c07d8ca60973f016d90
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-27T04:41:00.571Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:8753b64b54948c99cf086311b8e550c51ee113e5dd8c1645ed285d039d87f5f0","receipt_uuid":"2646e1c6-d801-4202-9ae2-ada1e57ae8ac","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

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/2646e1c6-d801-4202-9ae2-ada1e57ae8ac/badge.svg)](https://zambo.dev/run/2646e1c6-d801-4202-9ae2-ada1e57ae8ac?ref=badge)

HTML

<a href="https://zambo.dev/run/2646e1c6-d801-4202-9ae2-ada1e57ae8ac?ref=badge"><img src="https://zambo.dev/api/receipt/2646e1c6-d801-4202-9ae2-ada1e57ae8ac/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

72,368 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