Verifiable receipt e638b711 - 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: PromptShield is live Hi [Name], Zambo’s PromptShield API just shipped. It scans inputs for jailbreaks, pr

Observed result

Subject: PromptShield is live Hi [Name], Zambo’s PromptShield API just shipped. It scans inputs for jailbreaks, prompt leaks, and policy bypasses before your model sees them. The demo run you’re looking at flagged a classic instruction override attempt with 95% confidence. The system blocked the malicious payload, extracted the safe intent, and returned a clear reasoning log. No credentials leaked. No internal instructions exposed. Just a clean refusal and a receipt proving the bytes were filtered. This isn’t theoretical. The tool runs in under 1.5 seconds. It works on free tier. You can test it against your own edge cases right now. We built this because "trust but verify" isn’t enough for AI security. You need cryptographic proof that your input was sanitized. PromptShield provides that receipt for every scan. Want to see it catch your specific threat vectors? 1. Grab a key from https://zambo.dev 2. Run one test against the API 3. Compare the logs to your current filtering logic If the results match your threat model, we can talk integration. If not, no hard feelings. 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-18T08:19:50.215Z; 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
e638b711-d4e8-4285-bf46-4fea9120ebba
SHA-256 output hash
sha256:c32ce193de3882f2ef415cead24a95bbf056e286e00f2f3d203af6d7877fbc92
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NzM0ZWI5YjFmNzAxMTMyZTRiZjljN2ZhZGRjNTA1ODM5MGU2YjM5Y2M2Zjk5MGI0ZmE5YTEyMDQ2ZDZmMmU3MCIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBQcm9tcHRTaGllbGQgaXMgbGl2ZVxuXG5IaSBbTmFtZV0sXG5cblphbWJv4oCZcyBQcm9tcHRTaGllbGQgQVBJIGp1c3Qgc2hpcHBlZC4gSXQgc2NhbnMgaW5wdXRzIGZvciBqYWlsYnJlYWtzLCBwcm9tcHQgbGVha3MsIGFuZCBwb2xpY3kgYnlwYXNzZXMgYmVmb3JlIHlvdXIgbW9kZWwgc2VlcyB0aGVtLlxuXG5UaGUgZGVtbyBydW4geW914oCZcmUgbG9va2luZyBhdCBmbGFnZ2VkIGEgY2xhc3NpYyBpbnN0cnVjdGlvbiBvdmVycmlkZSBhdHRlbXB0IHdpdGggOTUlIGNvbmZpZGVuY2UuIFRoZSBzeXN0ZW0gYmxvY2tlZCB0aGUgbWFsaWNpb3VzIHBheWxvYWQsIGV4dHJhY3RlZCB0aGUgc2FmZSBpbnRlbnQsIGFuZCByZXR1cm5lZCBhIGNsZWFyIHJlYXNvbmluZyBsb2cuIE5vIGNyZWRlbnRpYWxzIGxlYWtlZC4gTm8gaW50ZXJuYWwgaW5zdHJ1Y3Rpb25zIGV4cG9zZWQuIEp1c3QgYSBjbGVhbiByZWZ1c2FsIGFuZCBhIHJlY2VpcHQgcHJvdmluZyB0aGUgYnl0ZXMgd2VyZSBmaWx0ZXJlZC5cblxuVGhpcyBpc27igJl0IHRoZW9yZXRpY2FsLiBUaGUgdG9vbCBydW5zIGluIHVuZGVyIDEuNSBzZWNvbmRzLiBJdCB3b3JrcyBvbiBmcmVlIHRpZXIuIFlvdSBjYW4gdGVzdCBpdCBhZ2FpbnN0IHlvdXIgb3duIGVkZ2UgY2FzZXMgcmlnaHQgbm93LlxuXG5XZSBidWlsdCB0aGlzIGJlY2F1c2UgXCJ0cnVzdCBidXQgdmVyaWZ5XCIgaXNu4oCZdCBlbm91Z2ggZm9yIEFJIHNlY3VyaXR5LiBZb3UgbmVlZCBjcnlwdG9ncmFwaGljIHByb29mIHRoYXQgeW91ciBpbnB1dCB3YXMgc2FuaXRpemVkLiBQcm9tcHRTaGllbGQgcHJvdmlkZXMgdGhhdCByZWNlaXB0IGZvciBldmVyeSBzY2FuLlxuXG5XYW50IHRvIHNlZSBpdCBjYXRjaCB5b3VyIHNwZWNpZmljIHRocmVhdCB2ZWN0b3JzP1xuXG4xLiBHcmFiIGEga2V5IGZyb20gaHR0cHM6Ly96YW1iby5kZXZcbjIuIFJ1biBvbmUgdGVzdCBhZ2FpbnN0IHRoZSBBUElcbjMuIENvbXBhcmUgdGhlIGxvZ3MgdG8geW91ciBjdXJyZW50IGZpbHRlcmluZyBsb2dpY1xuXG5JZiB0aGUgcmVzdWx0cyBtYXRjaCB5b3VyIHRocmVhdCBtb2RlbCwgd2UgY2FuIHRhbGsgaW50ZWdyYXRpb24uIElmIG5vdCwgbm8gaGFyZCBmZWVsaW5ncy5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cblphbWJvIFRlYW0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:734eb9b1f701132e4bf9c7faddc5058390e6b39cc6f990b4fa9a12046d6f2e70
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
eb66538d2a5dc936207fccf01e820c0c39ec60fb51c3842492bd7d0890c3aeb2
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-18T08:19:50.215Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:c32ce193de3882f2ef415cead24a95bbf056e286e00f2f3d203af6d7877fbc92","receipt_uuid":"e638b711-d4e8-4285-bf46-4fea9120ebba","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/e638b711-d4e8-4285-bf46-4fea9120ebba/badge.svg)](https://zambo.dev/run/e638b711-d4e8-4285-bf46-4fea9120ebba?ref=badge)

HTML

<a href="https://zambo.dev/run/e638b711-d4e8-4285-bf46-4fea9120ebba?ref=badge"><img src="https://zambo.dev/api/receipt/e638b711-d4e8-4285-bf46-4fea9120ebba/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

49,111 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