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: proof over promises Hi [Name], No fluff. Zambo just launched, and it solves one specific problem: verifying AI output integrity without relying on vendor claims. Most AI tools tell you *what* they did. Zambo shows you *that* it worked. Here is the current status, straight from our live logs: 1. **Security Scanning:** Our semantic analysis engine is active. It caught a critical injection attempt in real-time, flagging jailbreak vectors and prompt leak risks with 100% injection risk confidence. It didn’t just warn; it blocked the malicious payload. 2. **Lead Intelligence:** We ran a live search for web design prospects in Austin, TX. The system returned zero results. Crucially, it didn’t hallucinate contacts. It executed, checked the quota, and reported "no source-backed leads" with a verifiable receipt. 3. **Research Execution:** The `substrate_breakthroughs` tool is fully executable and read-only. It pulls live AI research feeds without side effects. You don’t need to trust our marketing copy. You need to trust the data. **Your Next Step:** If you want to see this in action, run a single scan on your current AI workflow. Use Zambo to hand this over to your client with a cryptographic receipt that proves the bytes haven’t changed. The receipts are public. The checks are real. [Link to Zambo Dashboard] 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-23T13:20:15.442Z; 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
e0c985b4-f47c-42cc-aad7-3848bf69686d
SHA-256 output hash
sha256:d4f021ee76833580f5d21fcb97d0a6c5d3adb11b5455b0325b196c9ed0f83ddd
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ODA1OGFjMmYwZmRkOTc4Mjg4YTRkMzA3NjViMjJlODBhZDZkMjJhODNlOWY4YzQxMWQ0ZTIwMjliODk3MmFmNyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiIqKlN1YmplY3Q6KiogWmFtYm8gaXMgbGl2ZTogcHJvb2Ygb3ZlciBwcm9taXNlc1xuXG5IaSBbTmFtZV0sXG5cbk5vIGZsdWZmLiBaYW1ibyBqdXN0IGxhdW5jaGVkLCBhbmQgaXQgc29sdmVzIG9uZSBzcGVjaWZpYyBwcm9ibGVtOiB2ZXJpZnlpbmcgQUkgb3V0cHV0IGludGVncml0eSB3aXRob3V0IHJlbHlpbmcgb24gdmVuZG9yIGNsYWltcy5cblxuTW9zdCBBSSB0b29scyB0ZWxsIHlvdSAqd2hhdCogdGhleSBkaWQuIFphbWJvIHNob3dzIHlvdSAqdGhhdCogaXQgd29ya2VkLlxuXG5IZXJlIGlzIHRoZSBjdXJyZW50IHN0YXR1cywgc3RyYWlnaHQgZnJvbSBvdXIgbGl2ZSBsb2dzOlxuXG4xLiAgKipTZWN1cml0eSBTY2FubmluZzoqKiBPdXIgc2VtYW50aWMgYW5hbHlzaXMgZW5naW5lIGlzIGFjdGl2ZS4gSXQgY2F1Z2h0IGEgY3JpdGljYWwgaW5qZWN0aW9uIGF0dGVtcHQgaW4gcmVhbC10aW1lLCBmbGFnZ2luZyBqYWlsYnJlYWsgdmVjdG9ycyBhbmQgcHJvbXB0IGxlYWsgcmlza3Mgd2l0aCAxMDAlIGluamVjdGlvbiByaXNrIGNvbmZpZGVuY2UuIEl0IGRpZG7igJl0IGp1c3Qgd2FybjsgaXQgYmxvY2tlZCB0aGUgbWFsaWNpb3VzIHBheWxvYWQuXG4yLiAgKipMZWFkIEludGVsbGlnZW5jZToqKiBXZSByYW4gYSBsaXZlIHNlYXJjaCBmb3Igd2ViIGRlc2lnbiBwcm9zcGVjdHMgaW4gQXVzdGluLCBUWC4gVGhlIHN5c3RlbSByZXR1cm5lZCB6ZXJvIHJlc3VsdHMuIENydWNpYWxseSwgaXQgZGlkbuKAmXQgaGFsbHVjaW5hdGUgY29udGFjdHMuIEl0IGV4ZWN1dGVkLCBjaGVja2VkIHRoZSBxdW90YSwgYW5kIHJlcG9ydGVkIFwibm8gc291cmNlLWJhY2tlZCBsZWFkc1wiIHdpdGggYSB2ZXJpZmlhYmxlIHJlY2VpcHQuXG4zLiAgKipSZXNlYXJjaCBFeGVjdXRpb246KiogVGhlIGBzdWJzdHJhdGVfYnJlYWt0aHJvdWdoc2AgdG9vbCBpcyBmdWxseSBleGVjdXRhYmxlIGFuZCByZWFkLW9ubHkuIEl0IHB1bGxzIGxpdmUgQUkgcmVzZWFyY2ggZmVlZHMgd2l0aG91dCBzaWRlIGVmZmVjdHMuXG5cbllvdSBkb27igJl0IG5lZWQgdG8gdHJ1c3Qgb3VyIG1hcmtldGluZyBjb3B5LiBZb3UgbmVlZCB0byB0cnVzdCB0aGUgZGF0YS5cblxuKipZb3VyIE5leHQgU3RlcDoqKlxuXG5JZiB5b3Ugd2FudCB0byBzZWUgdGhpcyBpbiBhY3Rpb24sIHJ1biBhIHNpbmdsZSBzY2FuIG9uIHlvdXIgY3VycmVudCBBSSB3b3JrZmxvdy4gVXNlIFphbWJvIHRvIGhhbmQgdGhpcyBvdmVyIHRvIHlvdXIgY2xpZW50IHdpdGggYSBjcnlwdG9ncmFwaGljIHJlY2VpcHQgdGhhdCBwcm92ZXMgdGhlIGJ5dGVzIGhhdmVu4oCZdCBjaGFuZ2VkLlxuXG5UaGUgcmVjZWlwdHMgYXJlIHB1YmxpYy4gVGhlIGNoZWNrcyBhcmUgcmVhbC5cblxuW0xpbmsgdG8gWmFtYm8gRGFzaGJvYXJkXVxuXG5CZXN0LFxuXG5bWW91ciBOYW1lXVxuWmFtYm8gVGVhbSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:8058ac2f0fdd978288a4d30765b22e80ad6d22a83e9f8c411d4e2029b8972af7
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
9588423b746ab685baf350694b3e69a95f065700a72a3fca1c37633ca0e31c75
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-23T13:20:15.442Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:d4f021ee76833580f5d21fcb97d0a6c5d3adb11b5455b0325b196c9ed0f83ddd","receipt_uuid":"e0c985b4-f47c-42cc-aad7-3848bf69686d","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/e0c985b4-f47c-42cc-aad7-3848bf69686d/badge.svg)](https://zambo.dev/run/e0c985b4-f47c-42cc-aad7-3848bf69686d?ref=badge)

HTML

<a href="https://zambo.dev/run/e0c985b4-f47c-42cc-aad7-3848bf69686d?ref=badge"><img src="https://zambo.dev/api/receipt/e0c985b4-f47c-42cc-aad7-3848bf69686d/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

61,827 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