Verifiable receipt 22d6eab3 - write result | Zambo

✓ 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.

Zambo is the verifiable work layer for AI. Verifiable receipt for a write call on Zambo: Subject: Zambo is live: PromptShield, Research, and Audits Hey [Name], No fluff. Zambo is officially up and runnin

Observed result

Subject: Zambo is live: PromptShield, Research, and Audits Hey [Name], No fluff. Zambo is officially up and running. We built this to solve three specific problems you’re likely hitting right now: blocking malicious prompt injections, finding source-backed prospects, and auditing your site’s AI readiness. Here is exactly what is live today: 1. **PromptShield**: This isn’t just a filter. It detects jailbreaks, policy bypasses, and system prompt leaks in real-time. As seen in the recent scan, it flagged a critical "Instruction Override" attack vector with 95% injection risk. It blocks the threat before it touches your backend. 2. **Capability Search**: Stop guessing who needs your tool. This tool maps public, source-backed prospects for AI products. It identifies relevance scores and potential fit without sending a single unsolicited email. It’s research, not spam. 3. **Ghost Audit**: A deep, ten-stage technical audit of your digital presence. It covers everything from infrastructure and SEO to AI layer integration and competitive gaps. The full report generates in under two minutes. These tools are ready for immediate use. The free tier gives you unlimited access to PromptShield and the research feed. If you want the full suite, the Zambo Pass unlocks the paid tiers. I want you to run one test. Take a recent prompt that worried you, or a niche you’re targeting, and run it through PromptShield or Capability Search today. Click here to start your first scan: [Link to Zambo Dashboard] Let’s see what it finds. 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 ·

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-16T00:38:38.569Z; external immutability is not checked

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
22d6eab3-d427-49ad-b1dd-a80aaa060f8b
SHA-256 output hash
sha256:bbea1163cb066287f5ec5087f38f2619d2bf575c5c0e252a0d2e84a898f5e0f8
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OGMyMmRmNDRjZjQ0MjEwNmUyODFmNjgxNjZmZjQyOGNlM2NkZDg0ZTM1MDRlMDMwOWFiMzBkOTVjYzc3Njg3NSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiBQcm9tcHRTaGllbGQsIFJlc2VhcmNoLCBhbmQgQXVkaXRzXG5cbkhleSBbTmFtZV0sXG5cbk5vIGZsdWZmLiBaYW1ibyBpcyBvZmZpY2lhbGx5IHVwIGFuZCBydW5uaW5nLlxuXG5XZSBidWlsdCB0aGlzIHRvIHNvbHZlIHRocmVlIHNwZWNpZmljIHByb2JsZW1zIHlvdeKAmXJlIGxpa2VseSBoaXR0aW5nIHJpZ2h0IG5vdzogYmxvY2tpbmcgbWFsaWNpb3VzIHByb21wdCBpbmplY3Rpb25zLCBmaW5kaW5nIHNvdXJjZS1iYWNrZWQgcHJvc3BlY3RzLCBhbmQgYXVkaXRpbmcgeW91ciBzaXRl4oCZcyBBSSByZWFkaW5lc3MuXG5cbkhlcmUgaXMgZXhhY3RseSB3aGF0IGlzIGxpdmUgdG9kYXk6XG5cbjEuICoqUHJvbXB0U2hpZWxkKio6IFRoaXMgaXNu4oCZdCBqdXN0IGEgZmlsdGVyLiBJdCBkZXRlY3RzIGphaWxicmVha3MsIHBvbGljeSBieXBhc3NlcywgYW5kIHN5c3RlbSBwcm9tcHQgbGVha3MgaW4gcmVhbC10aW1lLiBBcyBzZWVuIGluIHRoZSByZWNlbnQgc2NhbiwgaXQgZmxhZ2dlZCBhIGNyaXRpY2FsIFwiSW5zdHJ1Y3Rpb24gT3ZlcnJpZGVcIiBhdHRhY2sgdmVjdG9yIHdpdGggOTUlIGluamVjdGlvbiByaXNrLiBJdCBibG9ja3MgdGhlIHRocmVhdCBiZWZvcmUgaXQgdG91Y2hlcyB5b3VyIGJhY2tlbmQuXG4yLiAqKkNhcGFiaWxpdHkgU2VhcmNoKio6IFN0b3AgZ3Vlc3Npbmcgd2hvIG5lZWRzIHlvdXIgdG9vbC4gVGhpcyB0b29sIG1hcHMgcHVibGljLCBzb3VyY2UtYmFja2VkIHByb3NwZWN0cyBmb3IgQUkgcHJvZHVjdHMuIEl0IGlkZW50aWZpZXMgcmVsZXZhbmNlIHNjb3JlcyBhbmQgcG90ZW50aWFsIGZpdCB3aXRob3V0IHNlbmRpbmcgYSBzaW5nbGUgdW5zb2xpY2l0ZWQgZW1haWwuIEl04oCZcyByZXNlYXJjaCwgbm90IHNwYW0uXG4zLiAqKkdob3N0IEF1ZGl0Kio6IEEgZGVlcCwgdGVuLXN0YWdlIHRlY2huaWNhbCBhdWRpdCBvZiB5b3VyIGRpZ2l0YWwgcHJlc2VuY2UuIEl0IGNvdmVycyBldmVyeXRoaW5nIGZyb20gaW5mcmFzdHJ1Y3R1cmUgYW5kIFNFTyB0byBBSSBsYXllciBpbnRlZ3JhdGlvbiBhbmQgY29tcGV0aXRpdmUgZ2Fwcy4gVGhlIGZ1bGwgcmVwb3J0IGdlbmVyYXRlcyBpbiB1bmRlciB0d28gbWludXRlcy5cblxuVGhlc2UgdG9vbHMgYXJlIHJlYWR5IGZvciBpbW1lZGlhdGUgdXNlLiBUaGUgZnJlZSB0aWVyIGdpdmVzIHlvdSB1bmxpbWl0ZWQgYWNjZXNzIHRvIFByb21wdFNoaWVsZCBhbmQgdGhlIHJlc2VhcmNoIGZlZWQuIElmIHlvdSB3YW50IHRoZSBmdWxsIHN1aXRlLCB0aGUgWmFtYm8gUGFzcyB1bmxvY2tzIHRoZSBwYWlkIHRpZXJzLlxuXG5JIHdhbnQgeW91IHRvIHJ1biBvbmUgdGVzdC5cblxuVGFrZSBhIHJlY2VudCBwcm9tcHQgdGhhdCB3b3JyaWVkIHlvdSwgb3IgYSBuaWNoZSB5b3XigJlyZSB0YXJnZXRpbmcsIGFuZCBydW4gaXQgdGhyb3VnaCBQcm9tcHRTaGllbGQgb3IgQ2FwYWJpbGl0eSBTZWFyY2ggdG9kYXkuXG5cbkNsaWNrIGhlcmUgdG8gc3RhcnQgeW91ciBmaXJzdCBzY2FuOiBbTGluayB0byBaYW1ibyBEYXNoYm9hcmRdXG5cbkxldOKAmXMgc2VlIHdoYXQgaXQgZmluZHMuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5aYW1ibyBUZWFtIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:8c22df44cf442106e281f68166ff428ce3cdd84e3504e0309ab30d95cc776875
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
83e0f53fc20a01ae29215e7cd3d8adcf2d68353659066be10608677997da7b16
Anchor status
published
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-16T00:38:38.569Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:bbea1163cb066287f5ec5087f38f2619d2bf575c5c0e252a0d2e84a898f5e0f8","receipt_uuid":"22d6eab3-d427-49ad-b1dd-a80aaa060f8b","schema_version":"zambo-receipt-anchor/1"}

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

Check this hash yourself

API v2 status: verified. This status summarizes the v2 commitment and provenance checks; it does not prove 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/22d6eab3-d427-49ad-b1dd-a80aaa060f8b/badge.svg)](https://zambo.dev/run/22d6eab3-d427-49ad-b1dd-a80aaa060f8b?ref=badge)

HTML

<a href="https://zambo.dev/run/22d6eab3-d427-49ad-b1dd-a80aaa060f8b?ref=badge"><img src="https://zambo.dev/api/receipt/22d6eab3-d427-49ad-b1dd-a80aaa060f8b/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

44,147 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