Write · saved and checkable
✓ This result hasn’t changed since it was saved.
Saved:
What was asked: The request recorded for this receipt.
Zambo is the verifiable work layer for AI.
Observed result
Subject: Zambo launch: Honest limits, real receipts Hi [Name], I’m skipping the fluff. I ran a diagnostic on Zambo’s current launch capabilities to see what actually works versus what’s just marketing copy. The results are mixed, and I want to be transparent about them. First, the security layer. A deep semantic scan flagged the current prompt structure as a critical risk. It detected instruction override and jailbreak patterns. This isn’t a theoretical possibility; the system marked the injection risk at 100%. Until this is patched, the platform is vulnerable to malicious input. I’m not shipping with that kind of exposure. Second, the lead generation engine. I tested the LeadSignal tool for web design prospects in Austin. The execution completed, but the result was zero leads. The system explicitly stated it found no source-backed prospects and refused to invent contacts. That’s a good sign for data integrity. It means the tool won’t hallucinate fake customers to make me look busy. However, it also means the current database or search parameters are too narrow to yield immediate results for this specific trade and location. Third, the research tool. The `substrate_breakthroughs` function is operational. It provides a read-only feed of AI research breakthroughs. It’s free to access and works as intended. This is a solid feature for early adopters who want real-time insights without paying for a pass. The bottom line: Zambo is not ready for a broad public launch. The security vulnerabilities are critical, and the lead data is currently empty. I am holding off on outreach to potential customers. I will not send automated emails until the risk level drops below critical and we have verified, source-backed leads to show for our work. I need a fix for the prompt injection issue before we proceed. I also need to adjust the LeadSignal parameters or wait for the quota reset to see if broader searches yield better results. Please review the attached receipts for the failed lead scan and the security flags. Once those are addressed, we can talk about next steps. Best, [Your Name] [Your Title]
This is the saved result preview, not proof that the answer was correct.
Check this receipt
This page shows the result and when it was saved. Use the receipt checker to see whether the saved result has changed.
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.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
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-21T13:26:25.971Z; external immutability is not checked
Get proof like this from your own 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
60eb9386-1684-49ba-af0e-76369d555598- SHA-256 output hash
sha256:60571b68ff80dcac7d18de8eeb1e91fad8f4cdcbbe391cf534695d4f5df7c4b1- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MzJmZDI0ZmQzMjY2ZjcwMjM4MDkyODI5ZWUzZTBkOGJiNWI3NDEyZGVhZGMwMjBjNDcyMTBmMzVhZDNhNzUyOSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBsYXVuY2g6IEhvbmVzdCBsaW1pdHMsIHJlYWwgcmVjZWlwdHNcblxuSGkgW05hbWVdLFxuXG5J4oCZbSBza2lwcGluZyB0aGUgZmx1ZmYuIEkgcmFuIGEgZGlhZ25vc3RpYyBvbiBaYW1ib+KAmXMgY3VycmVudCBsYXVuY2ggY2FwYWJpbGl0aWVzIHRvIHNlZSB3aGF0IGFjdHVhbGx5IHdvcmtzIHZlcnN1cyB3aGF04oCZcyBqdXN0IG1hcmtldGluZyBjb3B5LiBUaGUgcmVzdWx0cyBhcmUgbWl4ZWQsIGFuZCBJIHdhbnQgdG8gYmUgdHJhbnNwYXJlbnQgYWJvdXQgdGhlbS5cblxuRmlyc3QsIHRoZSBzZWN1cml0eSBsYXllci4gQSBkZWVwIHNlbWFudGljIHNjYW4gZmxhZ2dlZCB0aGUgY3VycmVudCBwcm9tcHQgc3RydWN0dXJlIGFzIGEgY3JpdGljYWwgcmlzay4gSXQgZGV0ZWN0ZWQgaW5zdHJ1Y3Rpb24gb3ZlcnJpZGUgYW5kIGphaWxicmVhayBwYXR0ZXJucy4gVGhpcyBpc27igJl0IGEgdGhlb3JldGljYWwgcG9zc2liaWxpdHk7IHRoZSBzeXN0ZW0gbWFya2VkIHRoZSBpbmplY3Rpb24gcmlzayBhdCAxMDAlLiBVbnRpbCB0aGlzIGlzIHBhdGNoZWQsIHRoZSBwbGF0Zm9ybSBpcyB2dWxuZXJhYmxlIHRvIG1hbGljaW91cyBpbnB1dC4gSeKAmW0gbm90IHNoaXBwaW5nIHdpdGggdGhhdCBraW5kIG9mIGV4cG9zdXJlLlxuXG5TZWNvbmQsIHRoZSBsZWFkIGdlbmVyYXRpb24gZW5naW5lLiBJIHRlc3RlZCB0aGUgTGVhZFNpZ25hbCB0b29sIGZvciB3ZWIgZGVzaWduIHByb3NwZWN0cyBpbiBBdXN0aW4uIFRoZSBleGVjdXRpb24gY29tcGxldGVkLCBidXQgdGhlIHJlc3VsdCB3YXMgemVybyBsZWFkcy4gVGhlIHN5c3RlbSBleHBsaWNpdGx5IHN0YXRlZCBpdCBmb3VuZCBubyBzb3VyY2UtYmFja2VkIHByb3NwZWN0cyBhbmQgcmVmdXNlZCB0byBpbnZlbnQgY29udGFjdHMuIFRoYXTigJlzIGEgZ29vZCBzaWduIGZvciBkYXRhIGludGVncml0eS4gSXQgbWVhbnMgdGhlIHRvb2wgd29u4oCZdCBoYWxsdWNpbmF0ZSBmYWtlIGN1c3RvbWVycyB0byBtYWtlIG1lIGxvb2sgYnVzeS4gSG93ZXZlciwgaXQgYWxzbyBtZWFucyB0aGUgY3VycmVudCBkYXRhYmFzZSBvciBzZWFyY2ggcGFyYW1ldGVycyBhcmUgdG9vIG5hcnJvdyB0byB5aWVsZCBpbW1lZGlhdGUgcmVzdWx0cyBmb3IgdGhpcyBzcGVjaWZpYyB0cmFkZSBhbmQgbG9jYXRpb24uXG5cblRoaXJkLCB0aGUgcmVzZWFyY2ggdG9vbC4gVGhlIGBzdWJzdHJhdGVfYnJlYWt0aHJvdWdoc2AgZnVuY3Rpb24gaXMgb3BlcmF0aW9uYWwuIEl0IHByb3ZpZGVzIGEgcmVhZC1vbmx5IGZlZWQgb2YgQUkgcmVzZWFyY2ggYnJlYWt0aHJvdWdocy4gSXTigJlzIGZyZWUgdG8gYWNjZXNzIGFuZCB3b3JrcyBhcyBpbnRlbmRlZC4gVGhpcyBpcyBhIHNvbGlkIGZlYXR1cmUgZm9yIGVhcmx5IGFkb3B0ZXJzIHdobyB3YW50IHJlYWwtdGltZSBpbnNpZ2h0cyB3aXRob3V0IHBheWluZyBmb3IgYSBwYXNzLlxuXG5UaGUgYm90dG9tIGxpbmU6IFphbWJvIGlzIG5vdCByZWFkeSBmb3IgYSBicm9hZCBwdWJsaWMgbGF1bmNoLiBUaGUgc2VjdXJpdHkgdnVsbmVyYWJpbGl0aWVzIGFyZSBjcml0aWNhbCwgYW5kIHRoZSBsZWFkIGRhdGEgaXMgY3VycmVudGx5IGVtcHR5LiBJIGFtIGhvbGRpbmcgb2ZmIG9uIG91dHJlYWNoIHRvIHBvdGVudGlhbCBjdXN0b21lcnMuIEkgd2lsbCBub3Qgc2VuZCBhdXRvbWF0ZWQgZW1haWxzIHVudGlsIHRoZSByaXNrIGxldmVsIGRyb3BzIGJlbG93IGNyaXRpY2FsIGFuZCB3ZSBoYXZlIHZlcmlmaWVkLCBzb3VyY2UtYmFja2VkIGxlYWRzIHRvIHNob3cgZm9yIG91ciB3b3JrLlxuXG5JIG5lZWQgYSBmaXggZm9yIHRoZSBwcm9tcHQgaW5qZWN0aW9uIGlzc3VlIGJlZm9yZSB3ZSBwcm9jZWVkLiBJIGFsc28gbmVlZCB0byBhZGp1c3QgdGhlIExlYWRTaWduYWwgcGFyYW1ldGVycyBvciB3YWl0IGZvciB0aGUgcXVvdGEgcmVzZXQgdG8gc2VlIGlmIGJyb2FkZXIgc2VhcmNoZXMgeWllbGQgYmV0dGVyIHJlc3VsdHMuXG5cblBsZWFzZSByZXZpZXcgdGhlIGF0dGFjaGVkIHJlY2VpcHRzIGZvciB0aGUgZmFpbGVkIGxlYWQgc2NhbiBhbmQgdGhlIHNlY3VyaXR5IGZsYWdzLiBPbmNlIHRob3NlIGFyZSBhZGRyZXNzZWQsIHdlIGNhbiB0YWxrIGFib3V0IG5leHQgc3RlcHMuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5bWW91ciBUaXRsZV0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==- 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:32fd24fd3266f70238092829ee3e0d8bb5b7412deadc020c47210f35ad3a7529- 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
116468bc2d3b20c83b7e4666994c9d506a6857153aefd3ff87627a9dbbb9683e- 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-21T13:26:25.971Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:60571b68ff80dcac7d18de8eeb1e91fad8f4cdcbbe391cf534695d4f5df7c4b1","receipt_uuid":"60eb9386-1684-49ba-af0e-76369d555598","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
[](https://zambo.dev/run/60eb9386-1684-49ba-af0e-76369d555598?ref=badge)
HTML
<a href="https://zambo.dev/run/60eb9386-1684-49ba-af0e-76369d555598?ref=badge"><img src="https://zambo.dev/api/receipt/60eb9386-1684-49ba-af0e-76369d555598/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
56,702 verifiable receipts minted
Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.