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: Real-time prompt security & lead intelligence Hi [Name], Zambo just hit general availability. It solves two distinct problems for AI-native teams: it stops prompt injection attacks before they reach your logic, and it verifies lead data against live sources. The launch check you ran highlights the security layer. That scan flagged a critical instruction override and prompt leak attempt with 100% injection risk. It didn’t just block the attack; it generated a deep semantic analysis, identifying the specific attack vector and reasoning behind the breach. This is not a keyword filter. It’s a structural defense. The lead intelligence side is equally precise. Your recent Austin query for web design prospects returned zero source-backed leads. That is a feature, not a bug. Zambo refuses to hallucinate connections. It reports exactly what the data says: no verifiable prospects exist right now. You get accurate snapshots, not inflated lists. Every action generates a receipt. That link proves the bytes saved and the logic executed. It is an audit trail for your AI operations. The platform runs on a free tier. You have 12 calls remaining today. No API keys. No signup friction. Just direct access to the strategy, code audit, and lead generation tools. Stop guessing if your AI is safe. Stop trusting lead lists that look good on paper. [Link to Zambo Dashboard] Start your next scan or lead check now. Best, [Your Name] [Your Title] [Your Company]

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-29T17:18:11.710Z; 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
6e80b504-9931-4126-9572-a10f59c7d058
SHA-256 output hash
sha256:4443e0861f35147ff5e209fc9a8da4fec80035d97c5d98936ab007022a89179d
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MTVlMzQyZGIwMjU3NTUyYmFhM2U3OWQyZjg1MDFkMjAxNmJkODM2NDU1NTdkMGE0OTRmZjEyNGJmNWRjMGE3NyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiBSZWFsLXRpbWUgcHJvbXB0IHNlY3VyaXR5ICYgbGVhZCBpbnRlbGxpZ2VuY2VcblxuSGkgW05hbWVdLFxuXG5aYW1ibyBqdXN0IGhpdCBnZW5lcmFsIGF2YWlsYWJpbGl0eS4gSXQgc29sdmVzIHR3byBkaXN0aW5jdCBwcm9ibGVtcyBmb3IgQUktbmF0aXZlIHRlYW1zOiBpdCBzdG9wcyBwcm9tcHQgaW5qZWN0aW9uIGF0dGFja3MgYmVmb3JlIHRoZXkgcmVhY2ggeW91ciBsb2dpYywgYW5kIGl0IHZlcmlmaWVzIGxlYWQgZGF0YSBhZ2FpbnN0IGxpdmUgc291cmNlcy5cblxuVGhlIGxhdW5jaCBjaGVjayB5b3UgcmFuIGhpZ2hsaWdodHMgdGhlIHNlY3VyaXR5IGxheWVyLiBUaGF0IHNjYW4gZmxhZ2dlZCBhIGNyaXRpY2FsIGluc3RydWN0aW9uIG92ZXJyaWRlIGFuZCBwcm9tcHQgbGVhayBhdHRlbXB0IHdpdGggMTAwJSBpbmplY3Rpb24gcmlzay4gSXQgZGlkbuKAmXQganVzdCBibG9jayB0aGUgYXR0YWNrOyBpdCBnZW5lcmF0ZWQgYSBkZWVwIHNlbWFudGljIGFuYWx5c2lzLCBpZGVudGlmeWluZyB0aGUgc3BlY2lmaWMgYXR0YWNrIHZlY3RvciBhbmQgcmVhc29uaW5nIGJlaGluZCB0aGUgYnJlYWNoLiBUaGlzIGlzIG5vdCBhIGtleXdvcmQgZmlsdGVyLiBJdOKAmXMgYSBzdHJ1Y3R1cmFsIGRlZmVuc2UuXG5cblRoZSBsZWFkIGludGVsbGlnZW5jZSBzaWRlIGlzIGVxdWFsbHkgcHJlY2lzZS4gWW91ciByZWNlbnQgQXVzdGluIHF1ZXJ5IGZvciB3ZWIgZGVzaWduIHByb3NwZWN0cyByZXR1cm5lZCB6ZXJvIHNvdXJjZS1iYWNrZWQgbGVhZHMuIFRoYXQgaXMgYSBmZWF0dXJlLCBub3QgYSBidWcuIFphbWJvIHJlZnVzZXMgdG8gaGFsbHVjaW5hdGUgY29ubmVjdGlvbnMuIEl0IHJlcG9ydHMgZXhhY3RseSB3aGF0IHRoZSBkYXRhIHNheXM6IG5vIHZlcmlmaWFibGUgcHJvc3BlY3RzIGV4aXN0IHJpZ2h0IG5vdy4gWW91IGdldCBhY2N1cmF0ZSBzbmFwc2hvdHMsIG5vdCBpbmZsYXRlZCBsaXN0cy5cblxuRXZlcnkgYWN0aW9uIGdlbmVyYXRlcyBhIHJlY2VpcHQuIFRoYXQgbGluayBwcm92ZXMgdGhlIGJ5dGVzIHNhdmVkIGFuZCB0aGUgbG9naWMgZXhlY3V0ZWQuIEl0IGlzIGFuIGF1ZGl0IHRyYWlsIGZvciB5b3VyIEFJIG9wZXJhdGlvbnMuXG5cblRoZSBwbGF0Zm9ybSBydW5zIG9uIGEgZnJlZSB0aWVyLiBZb3UgaGF2ZSAxMiBjYWxscyByZW1haW5pbmcgdG9kYXkuIE5vIEFQSSBrZXlzLiBObyBzaWdudXAgZnJpY3Rpb24uIEp1c3QgZGlyZWN0IGFjY2VzcyB0byB0aGUgc3RyYXRlZ3ksIGNvZGUgYXVkaXQsIGFuZCBsZWFkIGdlbmVyYXRpb24gdG9vbHMuXG5cblN0b3AgZ3Vlc3NpbmcgaWYgeW91ciBBSSBpcyBzYWZlLiBTdG9wIHRydXN0aW5nIGxlYWQgbGlzdHMgdGhhdCBsb29rIGdvb2Qgb24gcGFwZXIuXG5cbltMaW5rIHRvIFphbWJvIERhc2hib2FyZF1cblxuU3RhcnQgeW91ciBuZXh0IHNjYW4gb3IgbGVhZCBjaGVjayBub3cuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5bWW91ciBUaXRsZV1cbltZb3VyIENvbXBhbnldIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:15e342db0257552baa3e79d2f8501d2016bd83645557d0a494ff124bf5dc0a77
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
b04c27a7c9af30467cfa4edab0cf12b50ae60c4a84cc3287c96b746bd7f4067a
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-29T17:18:11.710Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:4443e0861f35147ff5e209fc9a8da4fec80035d97c5d98936ab007022a89179d","receipt_uuid":"6e80b504-9931-4126-9572-a10f59c7d058","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/6e80b504-9931-4126-9572-a10f59c7d058/badge.svg)](https://zambo.dev/run/6e80b504-9931-4126-9572-a10f59c7d058?ref=badge)

HTML

<a href="https://zambo.dev/run/6e80b504-9931-4126-9572-a10f59c7d058?ref=badge"><img src="https://zambo.dev/api/receipt/6e80b504-9931-4126-9572-a10f59c7d058/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

81,547 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.