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: Automated research, lead scanning, and prompt security The Zambo platform is now operational, integrating automated research, lead generation, and advanced prompt security into a single workflow. This launch introduces a unified system that handles complex data tasks while maintaining strict safety protocols. **Core Capabilities** * **Automated Research & Lead Scanning:** Zambo executes deep semantic analysis and pattern checks to identify prospects. In recent tests, the system successfully scanned for web design leads in Austin, TX. While no specific contacts were generated in that instance, the tool confirmed the absence of fabricated data, ensuring integrity. The system tracks quota usage and receipt URLs for every action, providing a verifiable trail of execution. * **Prompt Security & Shielding:** Every input passes through a critical risk assessment layer. The system detects jailbreak attempts, policy bypasses, and prompt leaks with high precision. For example, a recent critical-risk attempt to override system instructions was blocked before processing. The shield provides a detailed breakdown of flagged patterns, attack vectors, and recommended safe versions, ensuring that malicious inputs are neutralized without disrupting legitimate workflows. * **Tool Integration:** Zambo connects to specialized tools like `substrate_breakthroughs` for AI research feeds and `VeriAI` for cryptographic trust scoring. These integrations are read-only and safe for unlimited free calls on the base tier, allowing users to gather intelligence without side effects. **Proof of Work** Every execution generates a unique receipt URL, such as `https://zambo.dev/run/d5f1ef23-fc1d-4ce0-b557-cfc2e105fcb8`. These receipts prove that saved bytes remain unchanged and that the system operated as intended. They serve as an audit trail for compliance and verification, confirming that no data was invented or altered. **Next Steps** To proceed with client handoffs or further testing, use the command: `use zambo to hand this over to <client>`. This ensures that all verified data, including receipts and analysis reports, is transferred securely. Zambo focuses on accuracy and security. It does not guess; it verifies. If a lead does not exist, the system reports zero results rather than fabricating data. This approach builds trust in the output, whether you are scanning for prospects or protecting against prompt injections. Start with a simple query to test the shield or run a lead scan to see the verification process in action. The platform is designed to handle the heavy lifting of research and security, leaving you with clean, verified results. — The 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-22T18:29:28.313Z; 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
4fc3cacf-e52e-40a9-a371-0af3ed8ea601
SHA-256 output hash
sha256:1d07a27c03199acb114ee565a6ad6f1e546382e349155c91295f324b721fc990
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NmI5MWZkNTEzMzNmYWFkMWE2YTg3M2ZlYjlkODk5ZWQ0NGY0NDgyNjE3MzViYjM4NWQ1YzQ3MmQ5OTJiMjUxNCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiBBdXRvbWF0ZWQgcmVzZWFyY2gsIGxlYWQgc2Nhbm5pbmcsIGFuZCBwcm9tcHQgc2VjdXJpdHlcblxuVGhlIFphbWJvIHBsYXRmb3JtIGlzIG5vdyBvcGVyYXRpb25hbCwgaW50ZWdyYXRpbmcgYXV0b21hdGVkIHJlc2VhcmNoLCBsZWFkIGdlbmVyYXRpb24sIGFuZCBhZHZhbmNlZCBwcm9tcHQgc2VjdXJpdHkgaW50byBhIHNpbmdsZSB3b3JrZmxvdy4gVGhpcyBsYXVuY2ggaW50cm9kdWNlcyBhIHVuaWZpZWQgc3lzdGVtIHRoYXQgaGFuZGxlcyBjb21wbGV4IGRhdGEgdGFza3Mgd2hpbGUgbWFpbnRhaW5pbmcgc3RyaWN0IHNhZmV0eSBwcm90b2NvbHMuXG5cbioqQ29yZSBDYXBhYmlsaXRpZXMqKlxuXG4qICAgKipBdXRvbWF0ZWQgUmVzZWFyY2ggJiBMZWFkIFNjYW5uaW5nOioqIFphbWJvIGV4ZWN1dGVzIGRlZXAgc2VtYW50aWMgYW5hbHlzaXMgYW5kIHBhdHRlcm4gY2hlY2tzIHRvIGlkZW50aWZ5IHByb3NwZWN0cy4gSW4gcmVjZW50IHRlc3RzLCB0aGUgc3lzdGVtIHN1Y2Nlc3NmdWxseSBzY2FubmVkIGZvciB3ZWIgZGVzaWduIGxlYWRzIGluIEF1c3RpbiwgVFguIFdoaWxlIG5vIHNwZWNpZmljIGNvbnRhY3RzIHdlcmUgZ2VuZXJhdGVkIGluIHRoYXQgaW5zdGFuY2UsIHRoZSB0b29sIGNvbmZpcm1lZCB0aGUgYWJzZW5jZSBvZiBmYWJyaWNhdGVkIGRhdGEsIGVuc3VyaW5nIGludGVncml0eS4gVGhlIHN5c3RlbSB0cmFja3MgcXVvdGEgdXNhZ2UgYW5kIHJlY2VpcHQgVVJMcyBmb3IgZXZlcnkgYWN0aW9uLCBwcm92aWRpbmcgYSB2ZXJpZmlhYmxlIHRyYWlsIG9mIGV4ZWN1dGlvbi5cbiogICAqKlByb21wdCBTZWN1cml0eSAmIFNoaWVsZGluZzoqKiBFdmVyeSBpbnB1dCBwYXNzZXMgdGhyb3VnaCBhIGNyaXRpY2FsIHJpc2sgYXNzZXNzbWVudCBsYXllci4gVGhlIHN5c3RlbSBkZXRlY3RzIGphaWxicmVhayBhdHRlbXB0cywgcG9saWN5IGJ5cGFzc2VzLCBhbmQgcHJvbXB0IGxlYWtzIHdpdGggaGlnaCBwcmVjaXNpb24uIEZvciBleGFtcGxlLCBhIHJlY2VudCBjcml0aWNhbC1yaXNrIGF0dGVtcHQgdG8gb3ZlcnJpZGUgc3lzdGVtIGluc3RydWN0aW9ucyB3YXMgYmxvY2tlZCBiZWZvcmUgcHJvY2Vzc2luZy4gVGhlIHNoaWVsZCBwcm92aWRlcyBhIGRldGFpbGVkIGJyZWFrZG93biBvZiBmbGFnZ2VkIHBhdHRlcm5zLCBhdHRhY2sgdmVjdG9ycywgYW5kIHJlY29tbWVuZGVkIHNhZmUgdmVyc2lvbnMsIGVuc3VyaW5nIHRoYXQgbWFsaWNpb3VzIGlucHV0cyBhcmUgbmV1dHJhbGl6ZWQgd2l0aG91dCBkaXNydXB0aW5nIGxlZ2l0aW1hdGUgd29ya2Zsb3dzLlxuKiAgICoqVG9vbCBJbnRlZ3JhdGlvbjoqKiBaYW1ibyBjb25uZWN0cyB0byBzcGVjaWFsaXplZCB0b29scyBsaWtlIGBzdWJzdHJhdGVfYnJlYWt0aHJvdWdoc2AgZm9yIEFJIHJlc2VhcmNoIGZlZWRzIGFuZCBgVmVyaUFJYCBmb3IgY3J5cHRvZ3JhcGhpYyB0cnVzdCBzY29yaW5nLiBUaGVzZSBpbnRlZ3JhdGlvbnMgYXJlIHJlYWQtb25seSBhbmQgc2FmZSBmb3IgdW5saW1pdGVkIGZyZWUgY2FsbHMgb24gdGhlIGJhc2UgdGllciwgYWxsb3dpbmcgdXNlcnMgdG8gZ2F0aGVyIGludGVsbGlnZW5jZSB3aXRob3V0IHNpZGUgZWZmZWN0cy5cblxuKipQcm9vZiBvZiBXb3JrKipcblxuRXZlcnkgZXhlY3V0aW9uIGdlbmVyYXRlcyBhIHVuaXF1ZSByZWNlaXB0IFVSTCwgc3VjaCBhcyBgaHR0cHM6Ly96YW1iby5kZXYvcnVuL2Q1ZjFlZjIzLWZjMWQtNGNlMC1iNTU3LWNmYzJlMTA1ZmNiOGAuIFRoZXNlIHJlY2VpcHRzIHByb3ZlIHRoYXQgc2F2ZWQgYnl0ZXMgcmVtYWluIHVuY2hhbmdlZCBhbmQgdGhhdCB0aGUgc3lzdGVtIG9wZXJhdGVkIGFzIGludGVuZGVkLiBUaGV5IHNlcnZlIGFzIGFuIGF1ZGl0IHRyYWlsIGZvciBjb21wbGlhbmNlIGFuZCB2ZXJpZmljYXRpb24sIGNvbmZpcm1pbmcgdGhhdCBubyBkYXRhIHdhcyBpbnZlbnRlZCBvciBhbHRlcmVkLlxuXG4qKk5leHQgU3RlcHMqKlxuXG5UbyBwcm9jZWVkIHdpdGggY2xpZW50IGhhbmRvZmZzIG9yIGZ1cnRoZXIgdGVzdGluZywgdXNlIHRoZSBjb21tYW5kOiBgdXNlIHphbWJvIHRvIGhhbmQgdGhpcyBvdmVyIHRvIDxjbGllbnQ+YC4gVGhpcyBlbnN1cmVzIHRoYXQgYWxsIHZlcmlmaWVkIGRhdGEsIGluY2x1ZGluZyByZWNlaXB0cyBhbmQgYW5hbHlzaXMgcmVwb3J0cywgaXMgdHJhbnNmZXJyZWQgc2VjdXJlbHkuXG5cblphbWJvIGZvY3VzZXMgb24gYWNjdXJhY3kgYW5kIHNlY3VyaXR5LiBJdCBkb2VzIG5vdCBndWVzczsgaXQgdmVyaWZpZXMuIElmIGEgbGVhZCBkb2VzIG5vdCBleGlzdCwgdGhlIHN5c3RlbSByZXBvcnRzIHplcm8gcmVzdWx0cyByYXRoZXIgdGhhbiBmYWJyaWNhdGluZyBkYXRhLiBUaGlzIGFwcHJvYWNoIGJ1aWxkcyB0cnVzdCBpbiB0aGUgb3V0cHV0LCB3aGV0aGVyIHlvdSBhcmUgc2Nhbm5pbmcgZm9yIHByb3NwZWN0cyBvciBwcm90ZWN0aW5nIGFnYWluc3QgcHJvbXB0IGluamVjdGlvbnMuXG5cblN0YXJ0IHdpdGggYSBzaW1wbGUgcXVlcnkgdG8gdGVzdCB0aGUgc2hpZWxkIG9yIHJ1biBhIGxlYWQgc2NhbiB0byBzZWUgdGhlIHZlcmlmaWNhdGlvbiBwcm9jZXNzIGluIGFjdGlvbi4gVGhlIHBsYXRmb3JtIGlzIGRlc2lnbmVkIHRvIGhhbmRsZSB0aGUgaGVhdnkgbGlmdGluZyBvZiByZXNlYXJjaCBhbmQgc2VjdXJpdHksIGxlYXZpbmcgeW91IHdpdGggY2xlYW4sIHZlcmlmaWVkIHJlc3VsdHMuXG5cbuKAlCBUaGUgWmFtYm8gVGVhbSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:6b91fd51333faad1a6a873feb9d899ed44f448261735bb385d5c472d992b2514
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
8d4fc6835b90b77d676352d9c5b0d2a54e4bd4d3355e8e562fc7191048c0c37c
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-22T18:29:28.313Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:1d07a27c03199acb114ee565a6ad6f1e546382e349155c91295f324b721fc990","receipt_uuid":"4fc3cacf-e52e-40a9-a371-0af3ed8ea601","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/4fc3cacf-e52e-40a9-a371-0af3ed8ea601/badge.svg)](https://zambo.dev/run/4fc3cacf-e52e-40a9-a371-0af3ed8ea601?ref=badge)

HTML

<a href="https://zambo.dev/run/4fc3cacf-e52e-40a9-a371-0af3ed8ea601?ref=badge"><img src="https://zambo.dev/api/receipt/4fc3cacf-e52e-40a9-a371-0af3ed8ea601/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

59,760 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