Verifiable receipt 237619db - 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 PromptShield is live Hi [Name], Zambo PromptShield is officially launching today. This tool scans i

Observed result

Subject: Zambo PromptShield is live Hi [Name], Zambo PromptShield is officially launching today. This tool scans incoming prompts to detect jailbreaks, injection attempts, and policy bypasses before they reach your LLM. It uses semantic analysis and a pattern check library to flag critical risks like instruction overrides and data extraction attempts. The system returns a clear risk level and specific flagged patterns, allowing you to block malicious inputs instantly while letting safe queries pass through. It includes detailed reasoning for each detection, so you know exactly why a prompt was flagged. We also integrated usage tracking directly into the response. You can see your remaining daily calls, your current plan status, and a direct link to upgrade if you hit your limit. The API is simple: send a prompt, get a verdict and a receipt URL for auditability. Ready to secure your AI stack? 1. Visit [Registration Link] to create your free account. 2. Grab your API key from the dashboard. 3. Run your first test prompt using the endpoint documented here: [Docs Link]. You get 20 free calls daily on the free tier. No credit card required to start. Let me know if you need help setting up the webhook or parsing the JSON response. Best, [Your Name] Product Lead, 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 ·

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-20T02:16:40.178Z; 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
237619db-9a86-43e2-be77-468902845858
SHA-256 output hash
sha256:32563ad1fd3417ec9df284ef550c39029e69951e40b823ae66f970bf06232dc8
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YTEzOWVkMDYzNWVkZGZmZjczN2U0NTU3OGNlYTc4OTAyZDEwNmFjN2UxODE2M2Y4ZTZjMDQ3MjI1ODkzMjIzMSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBQcm9tcHRTaGllbGQgaXMgbGl2ZVxuXG5IaSBbTmFtZV0sXG5cblphbWJvIFByb21wdFNoaWVsZCBpcyBvZmZpY2lhbGx5IGxhdW5jaGluZyB0b2RheS5cblxuVGhpcyB0b29sIHNjYW5zIGluY29taW5nIHByb21wdHMgdG8gZGV0ZWN0IGphaWxicmVha3MsIGluamVjdGlvbiBhdHRlbXB0cywgYW5kIHBvbGljeSBieXBhc3NlcyBiZWZvcmUgdGhleSByZWFjaCB5b3VyIExMTS4gSXQgdXNlcyBzZW1hbnRpYyBhbmFseXNpcyBhbmQgYSBwYXR0ZXJuIGNoZWNrIGxpYnJhcnkgdG8gZmxhZyBjcml0aWNhbCByaXNrcyBsaWtlIGluc3RydWN0aW9uIG92ZXJyaWRlcyBhbmQgZGF0YSBleHRyYWN0aW9uIGF0dGVtcHRzLlxuXG5UaGUgc3lzdGVtIHJldHVybnMgYSBjbGVhciByaXNrIGxldmVsIGFuZCBzcGVjaWZpYyBmbGFnZ2VkIHBhdHRlcm5zLCBhbGxvd2luZyB5b3UgdG8gYmxvY2sgbWFsaWNpb3VzIGlucHV0cyBpbnN0YW50bHkgd2hpbGUgbGV0dGluZyBzYWZlIHF1ZXJpZXMgcGFzcyB0aHJvdWdoLiBJdCBpbmNsdWRlcyBkZXRhaWxlZCByZWFzb25pbmcgZm9yIGVhY2ggZGV0ZWN0aW9uLCBzbyB5b3Uga25vdyBleGFjdGx5IHdoeSBhIHByb21wdCB3YXMgZmxhZ2dlZC5cblxuV2UgYWxzbyBpbnRlZ3JhdGVkIHVzYWdlIHRyYWNraW5nIGRpcmVjdGx5IGludG8gdGhlIHJlc3BvbnNlLiBZb3UgY2FuIHNlZSB5b3VyIHJlbWFpbmluZyBkYWlseSBjYWxscywgeW91ciBjdXJyZW50IHBsYW4gc3RhdHVzLCBhbmQgYSBkaXJlY3QgbGluayB0byB1cGdyYWRlIGlmIHlvdSBoaXQgeW91ciBsaW1pdC4gVGhlIEFQSSBpcyBzaW1wbGU6IHNlbmQgYSBwcm9tcHQsIGdldCBhIHZlcmRpY3QgYW5kIGEgcmVjZWlwdCBVUkwgZm9yIGF1ZGl0YWJpbGl0eS5cblxuUmVhZHkgdG8gc2VjdXJlIHlvdXIgQUkgc3RhY2s/XG5cbjEuIFZpc2l0IFtSZWdpc3RyYXRpb24gTGlua10gdG8gY3JlYXRlIHlvdXIgZnJlZSBhY2NvdW50LlxuMi4gR3JhYiB5b3VyIEFQSSBrZXkgZnJvbSB0aGUgZGFzaGJvYXJkLlxuMy4gUnVuIHlvdXIgZmlyc3QgdGVzdCBwcm9tcHQgdXNpbmcgdGhlIGVuZHBvaW50IGRvY3VtZW50ZWQgaGVyZTogW0RvY3MgTGlua10uXG5cbllvdSBnZXQgMjAgZnJlZSBjYWxscyBkYWlseSBvbiB0aGUgZnJlZSB0aWVyLiBObyBjcmVkaXQgY2FyZCByZXF1aXJlZCB0byBzdGFydC5cblxuTGV0IG1lIGtub3cgaWYgeW91IG5lZWQgaGVscCBzZXR0aW5nIHVwIHRoZSB3ZWJob29rIG9yIHBhcnNpbmcgdGhlIEpTT04gcmVzcG9uc2UuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5Qcm9kdWN0IExlYWQsIFphbWJvIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:a139ed0635eddfff737e45578cea78902d106ac7e18163f8e6c0472258932231
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
f9ceb1ffaa465e9273336e64e59bba1292a83e5f74fd6aadb3e821aa34be2018
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-20T02:16:40.178Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:32563ad1fd3417ec9df284ef550c39029e69951e40b823ae66f970bf06232dc8","receipt_uuid":"237619db-9a86-43e2-be77-468902845858","schema_version":"zambo-receipt-anchor/1"}

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

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/237619db-9a86-43e2-be77-468902845858/badge.svg)](https://zambo.dev/run/237619db-9a86-43e2-be77-468902845858?ref=badge)

HTML

<a href="https://zambo.dev/run/237619db-9a86-43e2-be77-468902845858?ref=badge"><img src="https://zambo.dev/api/receipt/237619db-9a86-43e2-be77-468902845858/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

53,223 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