Verifiable receipt 2d7159b4 - 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 AI output is now verifiable Hi [Name], You don’t need to trust my word for it. You need proof. VeriA

Observed result

Subject: Your AI output is now verifiable Hi [Name], You don’t need to trust my word for it. You need proof. VeriAI assigns a cryptographic trust score to any AI-generated output. It’s a hard line between "looks right" and "is right." We’ve integrated this directly into Zambo. When you generate code, copy, or analysis, you get a tamper-evident receipt. If someone alters the bytes later, the signature breaks. You’ll know immediately. This matters for two reasons: 1. **Auditability:** You can prove exactly what your model produced at timestamp X. 2. **Integrity:** You stop guessing if a downstream process corrupted the data. I’m not asking you to buy anything yet. I’m asking you to run one test. **The CTA:** Generate any simple text block through Zambo. Check the receipt link in the footer. Try to edit one character manually. Watch the validation fail. That’s the whole product. No dashboards to learn. No API keys to manage. Just a binary signal: trusted or compromised. If this solves a compliance headache you’ve been carrying, reply with "demo" and I’ll walk you through the integration in 15 minutes. If it’s not relevant, ignore this email. No hard feelings. Best, [Your Name] [Your Title] [Company Name]

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-16T14:20:39.921Z; 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
2d7159b4-eb1c-4da4-b2c4-c76e0d25e34b
SHA-256 output hash
sha256:7b9aa3641bff69087b99ae352a42c6190511279a9fd45af9d42a0f23186fc3fa
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YzU3NWQ4ZDg3YzUxZDFkY2YzMDNmYTAzYTRiNzg3NjdjMjIxZTY3OGUxOTQzYTk0ZjE0NmMwNGEzZGRmMDgwZSIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBZb3VyIEFJIG91dHB1dCBpcyBub3cgdmVyaWZpYWJsZVxuXG5IaSBbTmFtZV0sXG5cbllvdSBkb27igJl0IG5lZWQgdG8gdHJ1c3QgbXkgd29yZCBmb3IgaXQuIFlvdSBuZWVkIHByb29mLlxuXG5WZXJpQUkgYXNzaWducyBhIGNyeXB0b2dyYXBoaWMgdHJ1c3Qgc2NvcmUgdG8gYW55IEFJLWdlbmVyYXRlZCBvdXRwdXQuIEl04oCZcyBhIGhhcmQgbGluZSBiZXR3ZWVuIFwibG9va3MgcmlnaHRcIiBhbmQgXCJpcyByaWdodC5cIlxuXG5XZeKAmXZlIGludGVncmF0ZWQgdGhpcyBkaXJlY3RseSBpbnRvIFphbWJvLiBXaGVuIHlvdSBnZW5lcmF0ZSBjb2RlLCBjb3B5LCBvciBhbmFseXNpcywgeW91IGdldCBhIHRhbXBlci1ldmlkZW50IHJlY2VpcHQuIElmIHNvbWVvbmUgYWx0ZXJzIHRoZSBieXRlcyBsYXRlciwgdGhlIHNpZ25hdHVyZSBicmVha3MuIFlvdeKAmWxsIGtub3cgaW1tZWRpYXRlbHkuXG5cblRoaXMgbWF0dGVycyBmb3IgdHdvIHJlYXNvbnM6XG4xLiAqKkF1ZGl0YWJpbGl0eToqKiBZb3UgY2FuIHByb3ZlIGV4YWN0bHkgd2hhdCB5b3VyIG1vZGVsIHByb2R1Y2VkIGF0IHRpbWVzdGFtcCBYLlxuMi4gKipJbnRlZ3JpdHk6KiogWW91IHN0b3AgZ3Vlc3NpbmcgaWYgYSBkb3duc3RyZWFtIHByb2Nlc3MgY29ycnVwdGVkIHRoZSBkYXRhLlxuXG5J4oCZbSBub3QgYXNraW5nIHlvdSB0byBidXkgYW55dGhpbmcgeWV0LiBJ4oCZbSBhc2tpbmcgeW91IHRvIHJ1biBvbmUgdGVzdC5cblxuKipUaGUgQ1RBOioqXG5HZW5lcmF0ZSBhbnkgc2ltcGxlIHRleHQgYmxvY2sgdGhyb3VnaCBaYW1iby4gQ2hlY2sgdGhlIHJlY2VpcHQgbGluayBpbiB0aGUgZm9vdGVyLiBUcnkgdG8gZWRpdCBvbmUgY2hhcmFjdGVyIG1hbnVhbGx5LiBXYXRjaCB0aGUgdmFsaWRhdGlvbiBmYWlsLlxuXG5UaGF04oCZcyB0aGUgd2hvbGUgcHJvZHVjdC4gTm8gZGFzaGJvYXJkcyB0byBsZWFybi4gTm8gQVBJIGtleXMgdG8gbWFuYWdlLiBKdXN0IGEgYmluYXJ5IHNpZ25hbDogdHJ1c3RlZCBvciBjb21wcm9taXNlZC5cblxuSWYgdGhpcyBzb2x2ZXMgYSBjb21wbGlhbmNlIGhlYWRhY2hlIHlvdeKAmXZlIGJlZW4gY2FycnlpbmcsIHJlcGx5IHdpdGggXCJkZW1vXCIgYW5kIEnigJlsbCB3YWxrIHlvdSB0aHJvdWdoIHRoZSBpbnRlZ3JhdGlvbiBpbiAxNSBtaW51dGVzLiBJZiBpdOKAmXMgbm90IHJlbGV2YW50LCBpZ25vcmUgdGhpcyBlbWFpbC4gTm8gaGFyZCBmZWVsaW5ncy5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cbltZb3VyIFRpdGxlXVxuW0NvbXBhbnkgTmFtZV0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:c575d8d87c51d1dcf303fa03a4b78767c221e678e1943a94f146c04a3ddf080e
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
18081f453f1d45d34a9a624610bd98a7891d1fcc5c7cb0a34b6ac75646b5476b
Anchor status
partial
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-16T14:20:39.921Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:7b9aa3641bff69087b99ae352a42c6190511279a9fd45af9d42a0f23186fc3fa","receipt_uuid":"2d7159b4-eb1c-4da4-b2c4-c76e0d25e34b","schema_version":"zambo-receipt-anchor/1"}

Anchor status "partial": Published to some configured relay targets; publication was not confirmed by every configured relay.

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/2d7159b4-eb1c-4da4-b2c4-c76e0d25e34b/badge.svg)](https://zambo.dev/run/2d7159b4-eb1c-4da4-b2c4-c76e0d25e34b?ref=badge)

HTML

<a href="https://zambo.dev/run/2d7159b4-eb1c-4da4-b2c4-c76e0d25e34b?ref=badge"><img src="https://zambo.dev/api/receipt/2d7159b4-eb1c-4da4-b2c4-c76e0d25e34b/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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