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 research, zero guesswork Hi [Name], Zambo is officially live. It’s not another wrapper around a chatbot; it’s a research engine that executes, verifies, and hands you proof. Most AI tools give you a guess. Zambo gives you a receipt. When you run a task in Zambo, you get three things: 1. **Source-Backed Data:** No hallucinated leads or invented metrics. If the tool searches for prospects, it only returns what is publicly verifiable. If there are no leads, it says so. 2. **Security Integrity:** Every run includes a semantic scan. We block injection attacks, prompt leaks, and malicious overrides before they touch your data. You see the risk level and the verdict. 3. **Immutable Proof:** Every action generates a unique receipt URL. This doesn’t just show the output; it proves the saved bytes haven’t changed. It’s an audit trail for your AI workflow. We built Zambo for teams who need to trust their AI outputs. Whether you’re verifying AI-generated content with cryptographic trust scores or executing complex research queries, you get the result plus the evidence. **Try it now:** Head to [Link to Zambo] and run your first query. You’ll see the execution plan, the security scan, and the receipt instantly. No credit card required for the first run. If you want to see how the verification works, check out our latest run here: [Insert Link to Sample Receipt]. Let’s make your AI accountable. Best, [Your Name] [Your Title] 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 · 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-24T18:19:12.123Z; 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
e69018ae-f812-4530-9959-ad156a0110ae
SHA-256 output hash
sha256:3720f3ce8fe912ac3fa6d0cddf7dada2597e4d4b5a098ef399abe6fb492df2b1
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZmJkMzY5YTEwODM3YzY2NDlhODg0NDhlYjgwMWE2ZjY3ZDE3MzEzOTQzYjAzNGEwZWVlMzA2MGE4OWUzZDFlNyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiBWZXJpZmllZCBBSSByZXNlYXJjaCwgemVybyBndWVzc3dvcmtcblxuSGkgW05hbWVdLFxuXG5aYW1ibyBpcyBvZmZpY2lhbGx5IGxpdmUuIEl04oCZcyBub3QgYW5vdGhlciB3cmFwcGVyIGFyb3VuZCBhIGNoYXRib3Q7IGl04oCZcyBhIHJlc2VhcmNoIGVuZ2luZSB0aGF0IGV4ZWN1dGVzLCB2ZXJpZmllcywgYW5kIGhhbmRzIHlvdSBwcm9vZi5cblxuTW9zdCBBSSB0b29scyBnaXZlIHlvdSBhIGd1ZXNzLiBaYW1ibyBnaXZlcyB5b3UgYSByZWNlaXB0LlxuXG5XaGVuIHlvdSBydW4gYSB0YXNrIGluIFphbWJvLCB5b3UgZ2V0IHRocmVlIHRoaW5nczpcbjEuICoqU291cmNlLUJhY2tlZCBEYXRhOioqIE5vIGhhbGx1Y2luYXRlZCBsZWFkcyBvciBpbnZlbnRlZCBtZXRyaWNzLiBJZiB0aGUgdG9vbCBzZWFyY2hlcyBmb3IgcHJvc3BlY3RzLCBpdCBvbmx5IHJldHVybnMgd2hhdCBpcyBwdWJsaWNseSB2ZXJpZmlhYmxlLiBJZiB0aGVyZSBhcmUgbm8gbGVhZHMsIGl0IHNheXMgc28uXG4yLiAqKlNlY3VyaXR5IEludGVncml0eToqKiBFdmVyeSBydW4gaW5jbHVkZXMgYSBzZW1hbnRpYyBzY2FuLiBXZSBibG9jayBpbmplY3Rpb24gYXR0YWNrcywgcHJvbXB0IGxlYWtzLCBhbmQgbWFsaWNpb3VzIG92ZXJyaWRlcyBiZWZvcmUgdGhleSB0b3VjaCB5b3VyIGRhdGEuIFlvdSBzZWUgdGhlIHJpc2sgbGV2ZWwgYW5kIHRoZSB2ZXJkaWN0LlxuMy4gKipJbW11dGFibGUgUHJvb2Y6KiogRXZlcnkgYWN0aW9uIGdlbmVyYXRlcyBhIHVuaXF1ZSByZWNlaXB0IFVSTC4gVGhpcyBkb2VzbuKAmXQganVzdCBzaG93IHRoZSBvdXRwdXQ7IGl0IHByb3ZlcyB0aGUgc2F2ZWQgYnl0ZXMgaGF2ZW7igJl0IGNoYW5nZWQuIEl04oCZcyBhbiBhdWRpdCB0cmFpbCBmb3IgeW91ciBBSSB3b3JrZmxvdy5cblxuV2UgYnVpbHQgWmFtYm8gZm9yIHRlYW1zIHdobyBuZWVkIHRvIHRydXN0IHRoZWlyIEFJIG91dHB1dHMuIFdoZXRoZXIgeW914oCZcmUgdmVyaWZ5aW5nIEFJLWdlbmVyYXRlZCBjb250ZW50IHdpdGggY3J5cHRvZ3JhcGhpYyB0cnVzdCBzY29yZXMgb3IgZXhlY3V0aW5nIGNvbXBsZXggcmVzZWFyY2ggcXVlcmllcywgeW91IGdldCB0aGUgcmVzdWx0IHBsdXMgdGhlIGV2aWRlbmNlLlxuXG4qKlRyeSBpdCBub3c6KipcbkhlYWQgdG8gW0xpbmsgdG8gWmFtYm9dIGFuZCBydW4geW91ciBmaXJzdCBxdWVyeS4gWW914oCZbGwgc2VlIHRoZSBleGVjdXRpb24gcGxhbiwgdGhlIHNlY3VyaXR5IHNjYW4sIGFuZCB0aGUgcmVjZWlwdCBpbnN0YW50bHkuIE5vIGNyZWRpdCBjYXJkIHJlcXVpcmVkIGZvciB0aGUgZmlyc3QgcnVuLlxuXG5JZiB5b3Ugd2FudCB0byBzZWUgaG93IHRoZSB2ZXJpZmljYXRpb24gd29ya3MsIGNoZWNrIG91dCBvdXIgbGF0ZXN0IHJ1biBoZXJlOiBbSW5zZXJ0IExpbmsgdG8gU2FtcGxlIFJlY2VpcHRdLlxuXG5MZXTigJlzIG1ha2UgeW91ciBBSSBhY2NvdW50YWJsZS5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cbltZb3VyIFRpdGxlXVxuWmFtYm8ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:fbd369a10837c6649a88448eb801a6f67d17313943b034a0eee3060a89e3d1e7
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
ea227469d887d21066c890cd0f36efa7408c913b42cdc762275ec9adc72dea21
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-24T18:19:12.123Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:3720f3ce8fe912ac3fa6d0cddf7dada2597e4d4b5a098ef399abe6fb492df2b1","receipt_uuid":"e69018ae-f812-4530-9959-ad156a0110ae","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/e69018ae-f812-4530-9959-ad156a0110ae/badge.svg)](https://zambo.dev/run/e69018ae-f812-4530-9959-ad156a0110ae?ref=badge)

HTML

<a href="https://zambo.dev/run/e69018ae-f812-4530-9959-ad156a0110ae?ref=badge"><img src="https://zambo.dev/api/receipt/e69018ae-f812-4530-9959-ad156a0110ae/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

69,497 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.