Verifiable receipt 2ccfa875 - 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: rigorous launch checks Hi [Name], No fluff. Just the facts. Zambo’s launch checks are comp

Observed result

Subject: Zambo is live: rigorous launch checks Hi [Name], No fluff. Just the facts. Zambo’s launch checks are complete, and the results are in. The core finding is simple: integrity is verified, not assumed. The recent deep-scan receipt confirms that the saved bytes remain unchanged from the original source. This isn’t a claim of correctness; it’s a cryptographic proof of persistence. The data you see is exactly what was deployed. No drift. No silent edits. This matters because trust in AI tooling starts with verifiable stability. Zambo’s PromptShield has flagged critical injection risks with high precision, identifying specific override attempts and policy bypasses. The system didn’t just block the attack; it documented the vector, the severity, and the reasoning behind the block. That transparency is the difference between a black box and a reliable partner. We aren’t selling you a "game-changer." We are showing you a tool that holds up under adversarial scrutiny. The launch checks demonstrate that Zambo detects malicious intent without false positives on benign queries. It preserves your workflow while filtering out the noise. Your next step is verification. 1. Review the attached launch check summary. 2. Validate the receipt hash against your internal records: `https://zambo.dev/run/19e9d053-f8c8-4bbb-b438-b429f89cad13`. 3. Confirm that the flagged patterns match your current threat model. If the numbers align, you have a secure foundation for your AI operations. If they don’t, we need to talk. Let’s keep this moving. 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-16T06:21:41.988Z; 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
2ccfa875-a1ce-4aa7-a68a-0bb5c1060017
SHA-256 output hash
sha256:c753888b70aee3db08e4875e7526d8d638e35ad0e0d5734b1fb8803a366c8aa5
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZTU4YTQ4ZWY3NmUxYzcxM2VlY2RlMjM5OWZiN2MwZDk5M2Y1OTU3MWMxYjgyODMwZjU0MmE4YTAzOTVmYTExZSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiByaWdvcm91cyBsYXVuY2ggY2hlY2tzXG5cbkhpIFtOYW1lXSxcblxuTm8gZmx1ZmYuIEp1c3QgdGhlIGZhY3RzLiBaYW1ib+KAmXMgbGF1bmNoIGNoZWNrcyBhcmUgY29tcGxldGUsIGFuZCB0aGUgcmVzdWx0cyBhcmUgaW4uXG5cblRoZSBjb3JlIGZpbmRpbmcgaXMgc2ltcGxlOiBpbnRlZ3JpdHkgaXMgdmVyaWZpZWQsIG5vdCBhc3N1bWVkLiBUaGUgcmVjZW50IGRlZXAtc2NhbiByZWNlaXB0IGNvbmZpcm1zIHRoYXQgdGhlIHNhdmVkIGJ5dGVzIHJlbWFpbiB1bmNoYW5nZWQgZnJvbSB0aGUgb3JpZ2luYWwgc291cmNlLiBUaGlzIGlzbuKAmXQgYSBjbGFpbSBvZiBjb3JyZWN0bmVzczsgaXTigJlzIGEgY3J5cHRvZ3JhcGhpYyBwcm9vZiBvZiBwZXJzaXN0ZW5jZS4gVGhlIGRhdGEgeW91IHNlZSBpcyBleGFjdGx5IHdoYXQgd2FzIGRlcGxveWVkLiBObyBkcmlmdC4gTm8gc2lsZW50IGVkaXRzLlxuXG5UaGlzIG1hdHRlcnMgYmVjYXVzZSB0cnVzdCBpbiBBSSB0b29saW5nIHN0YXJ0cyB3aXRoIHZlcmlmaWFibGUgc3RhYmlsaXR5LiBaYW1ib+KAmXMgUHJvbXB0U2hpZWxkIGhhcyBmbGFnZ2VkIGNyaXRpY2FsIGluamVjdGlvbiByaXNrcyB3aXRoIGhpZ2ggcHJlY2lzaW9uLCBpZGVudGlmeWluZyBzcGVjaWZpYyBvdmVycmlkZSBhdHRlbXB0cyBhbmQgcG9saWN5IGJ5cGFzc2VzLiBUaGUgc3lzdGVtIGRpZG7igJl0IGp1c3QgYmxvY2sgdGhlIGF0dGFjazsgaXQgZG9jdW1lbnRlZCB0aGUgdmVjdG9yLCB0aGUgc2V2ZXJpdHksIGFuZCB0aGUgcmVhc29uaW5nIGJlaGluZCB0aGUgYmxvY2suIFRoYXQgdHJhbnNwYXJlbmN5IGlzIHRoZSBkaWZmZXJlbmNlIGJldHdlZW4gYSBibGFjayBib3ggYW5kIGEgcmVsaWFibGUgcGFydG5lci5cblxuV2UgYXJlbuKAmXQgc2VsbGluZyB5b3UgYSBcImdhbWUtY2hhbmdlci5cIiBXZSBhcmUgc2hvd2luZyB5b3UgYSB0b29sIHRoYXQgaG9sZHMgdXAgdW5kZXIgYWR2ZXJzYXJpYWwgc2NydXRpbnkuIFRoZSBsYXVuY2ggY2hlY2tzIGRlbW9uc3RyYXRlIHRoYXQgWmFtYm8gZGV0ZWN0cyBtYWxpY2lvdXMgaW50ZW50IHdpdGhvdXQgZmFsc2UgcG9zaXRpdmVzIG9uIGJlbmlnbiBxdWVyaWVzLiBJdCBwcmVzZXJ2ZXMgeW91ciB3b3JrZmxvdyB3aGlsZSBmaWx0ZXJpbmcgb3V0IHRoZSBub2lzZS5cblxuWW91ciBuZXh0IHN0ZXAgaXMgdmVyaWZpY2F0aW9uLlxuXG4xLiAgUmV2aWV3IHRoZSBhdHRhY2hlZCBsYXVuY2ggY2hlY2sgc3VtbWFyeS5cbjIuICBWYWxpZGF0ZSB0aGUgcmVjZWlwdCBoYXNoIGFnYWluc3QgeW91ciBpbnRlcm5hbCByZWNvcmRzOiBgaHR0cHM6Ly96YW1iby5kZXYvcnVuLzE5ZTlkMDUzLWY4YzgtNGJiYi1iNDM4LWI0MjlmODljYWQxM2AuXG4zLiAgQ29uZmlybSB0aGF0IHRoZSBmbGFnZ2VkIHBhdHRlcm5zIG1hdGNoIHlvdXIgY3VycmVudCB0aHJlYXQgbW9kZWwuXG5cbklmIHRoZSBudW1iZXJzIGFsaWduLCB5b3UgaGF2ZSBhIHNlY3VyZSBmb3VuZGF0aW9uIGZvciB5b3VyIEFJIG9wZXJhdGlvbnMuIElmIHRoZXkgZG9u4oCZdCwgd2UgbmVlZCB0byB0YWxrLlxuXG5MZXTigJlzIGtlZXAgdGhpcyBtb3ZpbmcuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5aYW1ibyBUZWFtIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:e58a48ef76e1c713eecde2399fb7c0d993f59571c1b82830f542a8a0395fa11e
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
a927d4b2687aa78a59dd0462450d4d34d83adf5f434f26a4d2ea0077cbebb300
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-16T06:21:41.988Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:c753888b70aee3db08e4875e7526d8d638e35ad0e0d5734b1fb8803a366c8aa5","receipt_uuid":"2ccfa875-a1ce-4aa7-a68a-0bb5c1060017","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/2ccfa875-a1ce-4aa7-a68a-0bb5c1060017/badge.svg)](https://zambo.dev/run/2ccfa875-a1ce-4aa7-a68a-0bb5c1060017?ref=badge)

HTML

<a href="https://zambo.dev/run/2ccfa875-a1ce-4aa7-a68a-0bb5c1060017?ref=badge"><img src="https://zambo.dev/api/receipt/2ccfa875-a1ce-4aa7-a68a-0bb5c1060017/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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