Verifiable receipt 1dc39050 - 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: Your prompt just triggered a critical alert You built a defense. It worked. The logs show a high-confiden

Observed result

Subject: Your prompt just triggered a critical alert You built a defense. It worked. The logs show a high-confidence detection of an instruction override attempt against your API. The system correctly flagged the malicious intent, categorized the risk as critical, and blocked the execution before any data leakage occurred. The latency was under 1.1 seconds. The pattern library identified the specific jailbreak vector without false positives. This is not just a log entry. It is proof that your architecture holds under pressure. When an attacker tries to bypass your safety rails, your system sees it, names it, and stops it. That reliability is the core of what we are launching. We are shipping a tool that makes this level of integrity visible. No more guessing if your guardrails are active. No more hoping your endpoints are secure. You get a clear, auditable trail of every threat detected and every block executed. Right now, we are onboarding a small group of teams to test the full suite. We are not promising a customer relationship yet. We are offering you a chance to see the raw data your systems are already generating, formatted for clarity. If you want to see exactly how your current defenses perform under attack, reply with the word "Show." We will send over a sample report based on the structure of the logs above. No sales pitch. Just the truth of what your system caught. The gate is open. The threat is real. Your defense just proved it works. Best, The Zambo Team [Your Name] [Your Title] Zambo https://zambo.dev

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:11:41.906Z; 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
1dc39050-4a7a-403e-8ad0-834cec366358
SHA-256 output hash
sha256:39ec14d1b64a7d1a950faa04aeaabb4d32dfe722f3844b978ca3b48195f0a43b
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NDExYmEzMDVkMGZlZjYzYTQyMzYzZmQ4NGE3Y2VhMmMzNWNkYjE1MjNkNDdmN2Q4ZTExYzdhOTJlYjEyMzY1YyIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBZb3VyIHByb21wdCBqdXN0IHRyaWdnZXJlZCBhIGNyaXRpY2FsIGFsZXJ0XG5cbllvdSBidWlsdCBhIGRlZmVuc2UuIEl0IHdvcmtlZC5cblxuVGhlIGxvZ3Mgc2hvdyBhIGhpZ2gtY29uZmlkZW5jZSBkZXRlY3Rpb24gb2YgYW4gaW5zdHJ1Y3Rpb24gb3ZlcnJpZGUgYXR0ZW1wdCBhZ2FpbnN0IHlvdXIgQVBJLiBUaGUgc3lzdGVtIGNvcnJlY3RseSBmbGFnZ2VkIHRoZSBtYWxpY2lvdXMgaW50ZW50LCBjYXRlZ29yaXplZCB0aGUgcmlzayBhcyBjcml0aWNhbCwgYW5kIGJsb2NrZWQgdGhlIGV4ZWN1dGlvbiBiZWZvcmUgYW55IGRhdGEgbGVha2FnZSBvY2N1cnJlZC4gVGhlIGxhdGVuY3kgd2FzIHVuZGVyIDEuMSBzZWNvbmRzLiBUaGUgcGF0dGVybiBsaWJyYXJ5IGlkZW50aWZpZWQgdGhlIHNwZWNpZmljIGphaWxicmVhayB2ZWN0b3Igd2l0aG91dCBmYWxzZSBwb3NpdGl2ZXMuXG5cblRoaXMgaXMgbm90IGp1c3QgYSBsb2cgZW50cnkuIEl0IGlzIHByb29mIHRoYXQgeW91ciBhcmNoaXRlY3R1cmUgaG9sZHMgdW5kZXIgcHJlc3N1cmUuIFdoZW4gYW4gYXR0YWNrZXIgdHJpZXMgdG8gYnlwYXNzIHlvdXIgc2FmZXR5IHJhaWxzLCB5b3VyIHN5c3RlbSBzZWVzIGl0LCBuYW1lcyBpdCwgYW5kIHN0b3BzIGl0LiBUaGF0IHJlbGlhYmlsaXR5IGlzIHRoZSBjb3JlIG9mIHdoYXQgd2UgYXJlIGxhdW5jaGluZy5cblxuV2UgYXJlIHNoaXBwaW5nIGEgdG9vbCB0aGF0IG1ha2VzIHRoaXMgbGV2ZWwgb2YgaW50ZWdyaXR5IHZpc2libGUuIE5vIG1vcmUgZ3Vlc3NpbmcgaWYgeW91ciBndWFyZHJhaWxzIGFyZSBhY3RpdmUuIE5vIG1vcmUgaG9waW5nIHlvdXIgZW5kcG9pbnRzIGFyZSBzZWN1cmUuIFlvdSBnZXQgYSBjbGVhciwgYXVkaXRhYmxlIHRyYWlsIG9mIGV2ZXJ5IHRocmVhdCBkZXRlY3RlZCBhbmQgZXZlcnkgYmxvY2sgZXhlY3V0ZWQuXG5cblJpZ2h0IG5vdywgd2UgYXJlIG9uYm9hcmRpbmcgYSBzbWFsbCBncm91cCBvZiB0ZWFtcyB0byB0ZXN0IHRoZSBmdWxsIHN1aXRlLiBXZSBhcmUgbm90IHByb21pc2luZyBhIGN1c3RvbWVyIHJlbGF0aW9uc2hpcCB5ZXQuIFdlIGFyZSBvZmZlcmluZyB5b3UgYSBjaGFuY2UgdG8gc2VlIHRoZSByYXcgZGF0YSB5b3VyIHN5c3RlbXMgYXJlIGFscmVhZHkgZ2VuZXJhdGluZywgZm9ybWF0dGVkIGZvciBjbGFyaXR5LlxuXG5JZiB5b3Ugd2FudCB0byBzZWUgZXhhY3RseSBob3cgeW91ciBjdXJyZW50IGRlZmVuc2VzIHBlcmZvcm0gdW5kZXIgYXR0YWNrLCByZXBseSB3aXRoIHRoZSB3b3JkIFwiU2hvdy5cIiBXZSB3aWxsIHNlbmQgb3ZlciBhIHNhbXBsZSByZXBvcnQgYmFzZWQgb24gdGhlIHN0cnVjdHVyZSBvZiB0aGUgbG9ncyBhYm92ZS4gTm8gc2FsZXMgcGl0Y2guIEp1c3QgdGhlIHRydXRoIG9mIHdoYXQgeW91ciBzeXN0ZW0gY2F1Z2h0LlxuXG5UaGUgZ2F0ZSBpcyBvcGVuLiBUaGUgdGhyZWF0IGlzIHJlYWwuIFlvdXIgZGVmZW5zZSBqdXN0IHByb3ZlZCBpdCB3b3Jrcy5cblxuQmVzdCxcblxuVGhlIFphbWJvIFRlYW1cbltZb3VyIE5hbWVdXG5bWW91ciBUaXRsZV1cblphbWJvXG5odHRwczovL3phbWJvLmRldiJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:411ba305d0fef63a42363fd84a7cea2c35cdb1523d47f7d8e11c7a92eb12365c
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
ff87a176fbdec42c0d6f1fcbdc5e37e125fd031973e6543d9853a950650a7b2a
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:11:41.906Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:39ec14d1b64a7d1a950faa04aeaabb4d32dfe722f3844b978ca3b48195f0a43b","receipt_uuid":"1dc39050-4a7a-403e-8ad0-834cec366358","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/1dc39050-4a7a-403e-8ad0-834cec366358/badge.svg)](https://zambo.dev/run/1dc39050-4a7a-403e-8ad0-834cec366358?ref=badge)

HTML

<a href="https://zambo.dev/run/1dc39050-4a7a-403e-8ad0-834cec366358?ref=badge"><img src="https://zambo.dev/api/receipt/1dc39050-4a7a-403e-8ad0-834cec366358/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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