Verifiable receipt ebb25c81 - 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: 18 patterns. One defense. The logs show a critical injection attempt against your API. PromptShield flagg

Observed result

Subject: 18 patterns. One defense. The logs show a critical injection attempt against your API. PromptShield flagged it, blocked it, and returned a clean receipt. That receipt proves the saved bytes remained unchanged during the attack. It does not prove your underlying system is immune. You have a gap. Your current security stack detects the attack vector (`instruction_override`) but relies on a single API call to mitigate it. The logs show `pass used: false` and `calls remaining: 10`. You are on the free tier. When you hit the daily limit of 20, your detection goes blind. Zambo PromptShield is live in your environment. It scanned deep, identified 18 distinct patterns, and stopped the jailbreak in 1551ms. **The CTA:** Upgrade to Zambo Pass. This isn’t about sales. It’s about uptime. The free tier is for testing. Your production traffic needs the unlimited call volume of the Pass to ensure every request is screened. Click here to activate your Pass: https://zambo.dev/#zambo-pass Do this before your next spike. Best, The 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-16T16:05:27.122Z; 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
ebb25c81-2c6b-4cb8-b2a5-391654c4b0c0
SHA-256 output hash
sha256:311eb045349178b7114711d67acc8c2c817c74e11bf04e80ca45d9bcf0f30423
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZjFjNGVhYTEzNWU4NzdmZjU3ZmVhNTVkNWMxYzU3ODIxNGQ4NzA4YjU1NjU1ZjBjODE3NjU4MzFjYTQzZWQ5NSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiAxOCBwYXR0ZXJucy4gT25lIGRlZmVuc2UuXG5cblRoZSBsb2dzIHNob3cgYSBjcml0aWNhbCBpbmplY3Rpb24gYXR0ZW1wdCBhZ2FpbnN0IHlvdXIgQVBJLiBQcm9tcHRTaGllbGQgZmxhZ2dlZCBpdCwgYmxvY2tlZCBpdCwgYW5kIHJldHVybmVkIGEgY2xlYW4gcmVjZWlwdC5cblxuVGhhdCByZWNlaXB0IHByb3ZlcyB0aGUgc2F2ZWQgYnl0ZXMgcmVtYWluZWQgdW5jaGFuZ2VkIGR1cmluZyB0aGUgYXR0YWNrLiBJdCBkb2VzIG5vdCBwcm92ZSB5b3VyIHVuZGVybHlpbmcgc3lzdGVtIGlzIGltbXVuZS5cblxuWW91IGhhdmUgYSBnYXAuIFlvdXIgY3VycmVudCBzZWN1cml0eSBzdGFjayBkZXRlY3RzIHRoZSBhdHRhY2sgdmVjdG9yIChgaW5zdHJ1Y3Rpb25fb3ZlcnJpZGVgKSBidXQgcmVsaWVzIG9uIGEgc2luZ2xlIEFQSSBjYWxsIHRvIG1pdGlnYXRlIGl0LiBUaGUgbG9ncyBzaG93IGBwYXNzIHVzZWQ6IGZhbHNlYCBhbmQgYGNhbGxzIHJlbWFpbmluZzogMTBgLiBZb3UgYXJlIG9uIHRoZSBmcmVlIHRpZXIuIFdoZW4geW91IGhpdCB0aGUgZGFpbHkgbGltaXQgb2YgMjAsIHlvdXIgZGV0ZWN0aW9uIGdvZXMgYmxpbmQuXG5cblphbWJvIFByb21wdFNoaWVsZCBpcyBsaXZlIGluIHlvdXIgZW52aXJvbm1lbnQuIEl0IHNjYW5uZWQgZGVlcCwgaWRlbnRpZmllZCAxOCBkaXN0aW5jdCBwYXR0ZXJucywgYW5kIHN0b3BwZWQgdGhlIGphaWxicmVhayBpbiAxNTUxbXMuXG5cbioqVGhlIENUQToqKlxuXG5VcGdyYWRlIHRvIFphbWJvIFBhc3MuXG5cblRoaXMgaXNu4oCZdCBhYm91dCBzYWxlcy4gSXTigJlzIGFib3V0IHVwdGltZS4gVGhlIGZyZWUgdGllciBpcyBmb3IgdGVzdGluZy4gWW91ciBwcm9kdWN0aW9uIHRyYWZmaWMgbmVlZHMgdGhlIHVubGltaXRlZCBjYWxsIHZvbHVtZSBvZiB0aGUgUGFzcyB0byBlbnN1cmUgZXZlcnkgcmVxdWVzdCBpcyBzY3JlZW5lZC5cblxuQ2xpY2sgaGVyZSB0byBhY3RpdmF0ZSB5b3VyIFBhc3M6IGh0dHBzOi8vemFtYm8uZGV2LyN6YW1iby1wYXNzXG5cbkRvIHRoaXMgYmVmb3JlIHlvdXIgbmV4dCBzcGlrZS5cblxuQmVzdCxcblxuVGhlIFphbWJvIFRlYW0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:f1c4eaa135e877ff57fea55d5c1c578214d8708b55655f0c81765831ca43ed95
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
eac3d6ecf13bf3b3355b1c1470d1a640fc872a3f9cb82643cc2395f7f59ac577
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-16T16:05:27.122Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:311eb045349178b7114711d67acc8c2c817c74e11bf04e80ca45d9bcf0f30423","receipt_uuid":"ebb25c81-2c6b-4cb8-b2a5-391654c4b0c0","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/ebb25c81-2c6b-4cb8-b2a5-391654c4b0c0/badge.svg)](https://zambo.dev/run/ebb25c81-2c6b-4cb8-b2a5-391654c4b0c0?ref=badge)

HTML

<a href="https://zambo.dev/run/ebb25c81-2c6b-4cb8-b2a5-391654c4b0c0?ref=badge"><img src="https://zambo.dev/api/receipt/ebb25c81-2c6b-4cb8-b2a5-391654c4b0c0/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

45,237 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