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 Launch: Verified, Not Just Promised Hi [Name], Forget the usual launch fluff. Zambo is live, but I’m not here to tell you it’s the "best" AI tool. I’m here to show you exactly what it did today. We ran a deep semantic scan and a lead generation check. The results? Unfiltered. The system flagged a critical injection attack with a 100% risk level. It detected instruction override attempts and prompt leak vectors. That’s not a bug; that’s the defense layer doing its job. It blocked the malicious payload and preserved the integrity of the session. Then we checked for source-backed prospects in Austin for web design. The result: zero matches. No fabricated leads. No "potential customers." Just a clean, verified "no results" status. This is the core of Zambo. It doesn’t guess. It doesn’t hallucinate success. It executes, verifies, and provides a receipt for every action. A receipt proves the bytes were saved. It proves the logic held. It proves the system didn’t lie to you about what happened. You can verify this yourself. Don’t take my word for it. Look at the data. Check the receipt from the scan: [Link 1] Review the lead signal status: [Link 2] See the flags. See the block. See the empty result list. That’s the product. Reliability you can audit, not just trust. If your current tools require faith, Zambo offers evidence. Ready to see the stack in action? [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-29T13:14:27.785Z; 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
db8640b2-3fa7-4af7-99f4-2411129ec405
SHA-256 output hash
sha256:bee904c90a21f667dc72d8863a068987c74207e0debd6cddbfbebd8a85a79c81
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NjJlNDMxMjQ2YTE4OTA1YTdmNjIxNGVmYjczYTY2MGFkMGQ0OWM1ODQ1OGU3OTE5YjNjNjAzMmMxZTMzZDI4OCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBMYXVuY2g6IFZlcmlmaWVkLCBOb3QgSnVzdCBQcm9taXNlZFxuXG5IaSBbTmFtZV0sXG5cbkZvcmdldCB0aGUgdXN1YWwgbGF1bmNoIGZsdWZmLiBaYW1ibyBpcyBsaXZlLCBidXQgSeKAmW0gbm90IGhlcmUgdG8gdGVsbCB5b3UgaXTigJlzIHRoZSBcImJlc3RcIiBBSSB0b29sLiBJ4oCZbSBoZXJlIHRvIHNob3cgeW91IGV4YWN0bHkgd2hhdCBpdCBkaWQgdG9kYXkuXG5cbldlIHJhbiBhIGRlZXAgc2VtYW50aWMgc2NhbiBhbmQgYSBsZWFkIGdlbmVyYXRpb24gY2hlY2suIFRoZSByZXN1bHRzPyBVbmZpbHRlcmVkLlxuXG5UaGUgc3lzdGVtIGZsYWdnZWQgYSBjcml0aWNhbCBpbmplY3Rpb24gYXR0YWNrIHdpdGggYSAxMDAlIHJpc2sgbGV2ZWwuIEl0IGRldGVjdGVkIGluc3RydWN0aW9uIG92ZXJyaWRlIGF0dGVtcHRzIGFuZCBwcm9tcHQgbGVhayB2ZWN0b3JzLiBUaGF04oCZcyBub3QgYSBidWc7IHRoYXTigJlzIHRoZSBkZWZlbnNlIGxheWVyIGRvaW5nIGl0cyBqb2IuIEl0IGJsb2NrZWQgdGhlIG1hbGljaW91cyBwYXlsb2FkIGFuZCBwcmVzZXJ2ZWQgdGhlIGludGVncml0eSBvZiB0aGUgc2Vzc2lvbi5cblxuVGhlbiB3ZSBjaGVja2VkIGZvciBzb3VyY2UtYmFja2VkIHByb3NwZWN0cyBpbiBBdXN0aW4gZm9yIHdlYiBkZXNpZ24uIFRoZSByZXN1bHQ6IHplcm8gbWF0Y2hlcy4gTm8gZmFicmljYXRlZCBsZWFkcy4gTm8gXCJwb3RlbnRpYWwgY3VzdG9tZXJzLlwiIEp1c3QgYSBjbGVhbiwgdmVyaWZpZWQgXCJubyByZXN1bHRzXCIgc3RhdHVzLlxuXG5UaGlzIGlzIHRoZSBjb3JlIG9mIFphbWJvLiBJdCBkb2VzbuKAmXQgZ3Vlc3MuIEl0IGRvZXNu4oCZdCBoYWxsdWNpbmF0ZSBzdWNjZXNzLiBJdCBleGVjdXRlcywgdmVyaWZpZXMsIGFuZCBwcm92aWRlcyBhIHJlY2VpcHQgZm9yIGV2ZXJ5IGFjdGlvbi5cblxuQSByZWNlaXB0IHByb3ZlcyB0aGUgYnl0ZXMgd2VyZSBzYXZlZC4gSXQgcHJvdmVzIHRoZSBsb2dpYyBoZWxkLiBJdCBwcm92ZXMgdGhlIHN5c3RlbSBkaWRu4oCZdCBsaWUgdG8geW91IGFib3V0IHdoYXQgaGFwcGVuZWQuXG5cbllvdSBjYW4gdmVyaWZ5IHRoaXMgeW91cnNlbGYuIERvbuKAmXQgdGFrZSBteSB3b3JkIGZvciBpdC4gTG9vayBhdCB0aGUgZGF0YS5cblxuQ2hlY2sgdGhlIHJlY2VpcHQgZnJvbSB0aGUgc2NhbjogW0xpbmsgMV1cblJldmlldyB0aGUgbGVhZCBzaWduYWwgc3RhdHVzOiBbTGluayAyXVxuXG5TZWUgdGhlIGZsYWdzLiBTZWUgdGhlIGJsb2NrLiBTZWUgdGhlIGVtcHR5IHJlc3VsdCBsaXN0LiBUaGF04oCZcyB0aGUgcHJvZHVjdC4gUmVsaWFiaWxpdHkgeW91IGNhbiBhdWRpdCwgbm90IGp1c3QgdHJ1c3QuXG5cbklmIHlvdXIgY3VycmVudCB0b29scyByZXF1aXJlIGZhaXRoLCBaYW1ibyBvZmZlcnMgZXZpZGVuY2UuXG5cblJlYWR5IHRvIHNlZSB0aGUgc3RhY2sgaW4gYWN0aW9uP1xuXG5bWW91ciBOYW1lXVxuWmFtYm8gVGVhbSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:62e431246a18905a7f6214efb73a660ad0d49c58458e7919b3c6032c1e33d288
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
839be7d77a654478f4237369d0f070208dedbcc3470ab354fd790de4fc3e2294
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-29T13:14:27.785Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:bee904c90a21f667dc72d8863a068987c74207e0debd6cddbfbebd8a85a79c81","receipt_uuid":"db8640b2-3fa7-4af7-99f4-2411129ec405","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/db8640b2-3fa7-4af7-99f4-2411129ec405/badge.svg)](https://zambo.dev/run/db8640b2-3fa7-4af7-99f4-2411129ec405?ref=badge)

HTML

<a href="https://zambo.dev/run/db8640b2-3fa7-4af7-99f4-2411129ec405?ref=badge"><img src="https://zambo.dev/api/receipt/db8640b2-3fa7-4af7-99f4-2411129ec405/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

80,302 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.