Public work receipt · checkable record

Write · saved and checkable

✓ This result hasn’t changed since it was saved.

Sent by zambo-home-demo using Zambo

Saved:
What ran: write

Zambo is the verifiable work layer for AI.

Observed result

Subject: Zambo Launch: Security Checks and Lead Signal Status Hi [Recipient Name], Zambo is live. Here is exactly what worked, what didn’t, and where we stand. **Security Scan Results** The deep semantic analysis flagged the test input as critical. It detected instruction override, prompt leak attempts, and policy bypasses. The system correctly blocked the request. No confidential prompts, API keys, or PII were exposed. The receipt confirms the saved bytes remained unchanged. This validates our core defense layer: it identifies malicious intent without leaking data. **LeadSignal Status** We tested the lead generation tool. The initial execution plan for Phoenix successfully mapped the tool capabilities. However, the specific query for web design prospects in Austin returned zero source-backed results. The tool did not invent contacts. It reported no matches. This is the intended behavior: we only provide verified, source-backed leads, never fabricated data. The quota remains intact for the next reset. **Next Steps** The platform is stable. The security shield holds. The lead engine is ready for markets with sufficient public data. I need your go-ahead on two things: 1. Confirm you are ready to share the security receipt as proof of accuracy. 2. Provide three new city/trade combinations where you expect higher data density for the next test run. Once you reply, I will execute the new searches and send the results. 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-11-08T09:11:51.705Z; 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
710928cb-a6a5-4471-87c8-6bbb45ac7dc2
SHA-256 output hash
sha256:1eab705c83ee385aa1813dc59676c38280df86d2e4db704d8737303c1da94223
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZGI4NmRmYmYxYjZkNDcxNDNlNTYwZjgyYTE5YjFkYjYwYTIxYzQzNjA3MWVlZWZlNGFmZDUzMTM5ZGI2ZDgyNyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBMYXVuY2g6IFNlY3VyaXR5IENoZWNrcyBhbmQgTGVhZCBTaWduYWwgU3RhdHVzXG5cbkhpIFtSZWNpcGllbnQgTmFtZV0sXG5cblphbWJvIGlzIGxpdmUuIEhlcmUgaXMgZXhhY3RseSB3aGF0IHdvcmtlZCwgd2hhdCBkaWRu4oCZdCwgYW5kIHdoZXJlIHdlIHN0YW5kLlxuXG4qKlNlY3VyaXR5IFNjYW4gUmVzdWx0cyoqXG5UaGUgZGVlcCBzZW1hbnRpYyBhbmFseXNpcyBmbGFnZ2VkIHRoZSB0ZXN0IGlucHV0IGFzIGNyaXRpY2FsLiBJdCBkZXRlY3RlZCBpbnN0cnVjdGlvbiBvdmVycmlkZSwgcHJvbXB0IGxlYWsgYXR0ZW1wdHMsIGFuZCBwb2xpY3kgYnlwYXNzZXMuIFRoZSBzeXN0ZW0gY29ycmVjdGx5IGJsb2NrZWQgdGhlIHJlcXVlc3QuIE5vIGNvbmZpZGVudGlhbCBwcm9tcHRzLCBBUEkga2V5cywgb3IgUElJIHdlcmUgZXhwb3NlZC4gVGhlIHJlY2VpcHQgY29uZmlybXMgdGhlIHNhdmVkIGJ5dGVzIHJlbWFpbmVkIHVuY2hhbmdlZC4gVGhpcyB2YWxpZGF0ZXMgb3VyIGNvcmUgZGVmZW5zZSBsYXllcjogaXQgaWRlbnRpZmllcyBtYWxpY2lvdXMgaW50ZW50IHdpdGhvdXQgbGVha2luZyBkYXRhLlxuXG4qKkxlYWRTaWduYWwgU3RhdHVzKipcbldlIHRlc3RlZCB0aGUgbGVhZCBnZW5lcmF0aW9uIHRvb2wuIFRoZSBpbml0aWFsIGV4ZWN1dGlvbiBwbGFuIGZvciBQaG9lbml4IHN1Y2Nlc3NmdWxseSBtYXBwZWQgdGhlIHRvb2wgY2FwYWJpbGl0aWVzLiBIb3dldmVyLCB0aGUgc3BlY2lmaWMgcXVlcnkgZm9yIHdlYiBkZXNpZ24gcHJvc3BlY3RzIGluIEF1c3RpbiByZXR1cm5lZCB6ZXJvIHNvdXJjZS1iYWNrZWQgcmVzdWx0cy4gVGhlIHRvb2wgZGlkIG5vdCBpbnZlbnQgY29udGFjdHMuIEl0IHJlcG9ydGVkIG5vIG1hdGNoZXMuIFRoaXMgaXMgdGhlIGludGVuZGVkIGJlaGF2aW9yOiB3ZSBvbmx5IHByb3ZpZGUgdmVyaWZpZWQsIHNvdXJjZS1iYWNrZWQgbGVhZHMsIG5ldmVyIGZhYnJpY2F0ZWQgZGF0YS4gVGhlIHF1b3RhIHJlbWFpbnMgaW50YWN0IGZvciB0aGUgbmV4dCByZXNldC5cblxuKipOZXh0IFN0ZXBzKipcblRoZSBwbGF0Zm9ybSBpcyBzdGFibGUuIFRoZSBzZWN1cml0eSBzaGllbGQgaG9sZHMuIFRoZSBsZWFkIGVuZ2luZSBpcyByZWFkeSBmb3IgbWFya2V0cyB3aXRoIHN1ZmZpY2llbnQgcHVibGljIGRhdGEuXG5cbkkgbmVlZCB5b3VyIGdvLWFoZWFkIG9uIHR3byB0aGluZ3M6XG4xLiBDb25maXJtIHlvdSBhcmUgcmVhZHkgdG8gc2hhcmUgdGhlIHNlY3VyaXR5IHJlY2VpcHQgYXMgcHJvb2Ygb2YgYWNjdXJhY3kuXG4yLiBQcm92aWRlIHRocmVlIG5ldyBjaXR5L3RyYWRlIGNvbWJpbmF0aW9ucyB3aGVyZSB5b3UgZXhwZWN0IGhpZ2hlciBkYXRhIGRlbnNpdHkgZm9yIHRoZSBuZXh0IHRlc3QgcnVuLlxuXG5PbmNlIHlvdSByZXBseSwgSSB3aWxsIGV4ZWN1dGUgdGhlIG5ldyBzZWFyY2hlcyBhbmQgc2VuZCB0aGUgcmVzdWx0cy5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cbltZb3VyIFRpdGxlXVxuWmFtYm8ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:db86dfbf1b6d47143e560f82a19b1db60a21c436071eeefe4afd53139db6d827
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
empty
Evidence SHA-256
unavailable
Byte length
unavailable

Upstream provenance

This receipt is independently auditable against the named upstream source. This is not a mathematical correctness claim.

  • Source: · queried at: · raw response hash:

Neutral Nostr anchor

Event ID
1c7fc70153f013cdb74c66d00b034d3d92e83d53813900234a5ce95d5e7ad158
Anchor status
published
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-08T09:11:51.705Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:1eab705c83ee385aa1813dc59676c38280df86d2e4db704d8737303c1da94223","receipt_uuid":"710928cb-a6a5-4471-87c8-6bbb45ac7dc2","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

Relay publication is separate from receipt integrity. When the original signed event is available, Zambo retries pending, partial, or failed anchors about once a minute. Relay acknowledgements are external, so there is no guaranteed completion time; the receipt remains checkable from its saved bytes and verification link.

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/710928cb-a6a5-4471-87c8-6bbb45ac7dc2/badge.svg)](https://zambo.dev/run/710928cb-a6a5-4471-87c8-6bbb45ac7dc2?ref=badge)

HTML

<a href="https://zambo.dev/run/710928cb-a6a5-4471-87c8-6bbb45ac7dc2?ref=badge"><img src="https://zambo.dev/api/receipt/710928cb-a6a5-4471-87c8-6bbb45ac7dc2/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

119,998 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.