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** We just turned on the engine. Zambo is now fully executable. It scans deep, checks patterns, and returns verifiable results without the usual guesswork. You aren't waiting on a beta anymore. You have a working system that identifies risks, verifies outputs, and tracks every action with a receipt. Here is what it does right now: * **Deep Semantic Analysis:** It runs a 21-rule pattern check to flag injection risks and policy bypasses. It doesn’t just look at keywords; it understands intent. * **Verifiable Research:** It pulls source-backed data. If it finds a lead, it’s real. If it doesn’t, it tells you exactly that. No invented contacts. No hallucinated sales. * **Receipt-Driven Proof:** Every run generates a unique URL. That link proves the bytes were saved. It is an audit trail, not just a log. We built this for people who need certainty. If your workflow involves AI outputs, risk scanning, or lead generation, Zambo removes the "maybe." It gives you the "yes" or the "no," backed by data. The free tier is active. You can run unlimited calls on core capabilities. There is no setup fee. There is no waitlist. **One clear next step:** Test it against your current process. Run a scan. Check a receipt. See if the output matches your reality. If it works, integrate it. If it doesn’t, you lost nothing but a few seconds. The link is open. The system is ready. [Button: Start Your First Run] Best, The 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-25T06:56:38.190Z; 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
406ec57a-e4a1-4e2b-af14-a62f51e2c91a
SHA-256 output hash
sha256:fe281c61f32c62b4e01b175f5c8b9c30d9521f2066ef623d39a945679273ec35
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NGYwMzQ1MjZkNTM2YzMzOTY2OWFiOTk5ODY5NTU1ZWNiOWE2MmYwODQ4YmFmMWRlZTY3NWQ4NGUxZWI0ZGI0NyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiIqKlN1YmplY3Q6IFphbWJvIGlzIGxpdmUqKlxuXG5XZSBqdXN0IHR1cm5lZCBvbiB0aGUgZW5naW5lLlxuXG5aYW1ibyBpcyBub3cgZnVsbHkgZXhlY3V0YWJsZS4gSXQgc2NhbnMgZGVlcCwgY2hlY2tzIHBhdHRlcm5zLCBhbmQgcmV0dXJucyB2ZXJpZmlhYmxlIHJlc3VsdHMgd2l0aG91dCB0aGUgdXN1YWwgZ3Vlc3N3b3JrLlxuXG5Zb3UgYXJlbid0IHdhaXRpbmcgb24gYSBiZXRhIGFueW1vcmUuIFlvdSBoYXZlIGEgd29ya2luZyBzeXN0ZW0gdGhhdCBpZGVudGlmaWVzIHJpc2tzLCB2ZXJpZmllcyBvdXRwdXRzLCBhbmQgdHJhY2tzIGV2ZXJ5IGFjdGlvbiB3aXRoIGEgcmVjZWlwdC5cblxuSGVyZSBpcyB3aGF0IGl0IGRvZXMgcmlnaHQgbm93OlxuXG4qICAgKipEZWVwIFNlbWFudGljIEFuYWx5c2lzOioqIEl0IHJ1bnMgYSAyMS1ydWxlIHBhdHRlcm4gY2hlY2sgdG8gZmxhZyBpbmplY3Rpb24gcmlza3MgYW5kIHBvbGljeSBieXBhc3Nlcy4gSXQgZG9lc27igJl0IGp1c3QgbG9vayBhdCBrZXl3b3JkczsgaXQgdW5kZXJzdGFuZHMgaW50ZW50LlxuKiAgICoqVmVyaWZpYWJsZSBSZXNlYXJjaDoqKiBJdCBwdWxscyBzb3VyY2UtYmFja2VkIGRhdGEuIElmIGl0IGZpbmRzIGEgbGVhZCwgaXTigJlzIHJlYWwuIElmIGl0IGRvZXNu4oCZdCwgaXQgdGVsbHMgeW91IGV4YWN0bHkgdGhhdC4gTm8gaW52ZW50ZWQgY29udGFjdHMuIE5vIGhhbGx1Y2luYXRlZCBzYWxlcy5cbiogICAqKlJlY2VpcHQtRHJpdmVuIFByb29mOioqIEV2ZXJ5IHJ1biBnZW5lcmF0ZXMgYSB1bmlxdWUgVVJMLiBUaGF0IGxpbmsgcHJvdmVzIHRoZSBieXRlcyB3ZXJlIHNhdmVkLiBJdCBpcyBhbiBhdWRpdCB0cmFpbCwgbm90IGp1c3QgYSBsb2cuXG5cbldlIGJ1aWx0IHRoaXMgZm9yIHBlb3BsZSB3aG8gbmVlZCBjZXJ0YWludHkuIElmIHlvdXIgd29ya2Zsb3cgaW52b2x2ZXMgQUkgb3V0cHV0cywgcmlzayBzY2FubmluZywgb3IgbGVhZCBnZW5lcmF0aW9uLCBaYW1ibyByZW1vdmVzIHRoZSBcIm1heWJlLlwiIEl0IGdpdmVzIHlvdSB0aGUgXCJ5ZXNcIiBvciB0aGUgXCJubyxcIiBiYWNrZWQgYnkgZGF0YS5cblxuVGhlIGZyZWUgdGllciBpcyBhY3RpdmUuIFlvdSBjYW4gcnVuIHVubGltaXRlZCBjYWxscyBvbiBjb3JlIGNhcGFiaWxpdGllcy4gVGhlcmUgaXMgbm8gc2V0dXAgZmVlLiBUaGVyZSBpcyBubyB3YWl0bGlzdC5cblxuKipPbmUgY2xlYXIgbmV4dCBzdGVwOioqXG5cblRlc3QgaXQgYWdhaW5zdCB5b3VyIGN1cnJlbnQgcHJvY2Vzcy4gUnVuIGEgc2Nhbi4gQ2hlY2sgYSByZWNlaXB0LiBTZWUgaWYgdGhlIG91dHB1dCBtYXRjaGVzIHlvdXIgcmVhbGl0eS5cblxuSWYgaXQgd29ya3MsIGludGVncmF0ZSBpdC4gSWYgaXQgZG9lc27igJl0LCB5b3UgbG9zdCBub3RoaW5nIGJ1dCBhIGZldyBzZWNvbmRzLlxuXG5UaGUgbGluayBpcyBvcGVuLiBUaGUgc3lzdGVtIGlzIHJlYWR5LlxuXG5bQnV0dG9uOiBTdGFydCBZb3VyIEZpcnN0IFJ1bl1cblxuQmVzdCxcblxuVGhlIFphbWJvIFRlYW0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:4f034526d536c339669ab999869555ecb9a62f0848baf1dee675d84e1eb4db47
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
96d947ddabf0e67bebca0100172b1cb43c85f4b8cc7959615aa9c70b76ec3ad2
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-25T06:56:38.190Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:fe281c61f32c62b4e01b175f5c8b9c30d9521f2066ef623d39a945679273ec35","receipt_uuid":"406ec57a-e4a1-4e2b-af14-a62f51e2c91a","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/406ec57a-e4a1-4e2b-af14-a62f51e2c91a/badge.svg)](https://zambo.dev/run/406ec57a-e4a1-4e2b-af14-a62f51e2c91a?ref=badge)

HTML

<a href="https://zambo.dev/run/406ec57a-e4a1-4e2b-af14-a62f51e2c91a?ref=badge"><img src="https://zambo.dev/api/receipt/406ec57a-e4a1-4e2b-af14-a62f51e2c91a/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

66,249 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.