Verifiable receipt 250bc969 - write result | Zambo
Verifiable receipt for a write call on Zambo: **Zambo Launches Verifiable Work Layer for AI** *SAN FRANCISCO, Oct 14 2026* – Zambo today releases a production‑g
Observed result
**Zambo Launches Verifiable Work Layer for AI** *SAN FRANCISCO, Oct 14 2026* – Zambo today releases a production‑grade “verifiable work” layer that records every AI‑generated byte, timestamps it, and stores an immutable receipt. The service goes live immediately, giving developers a tamper‑evident proof that saved data has not been altered—without claiming correctness of the content. Receipt example: https://zambo.dev/run/91905673-bd41-4274-87c9-07ce064eebd6. The new layer plugs into existing AI pipelines, generating a cryptographic hash for each output file and appending it to a public ledger. Developers can query the ledger to confirm that a byte‑string matches the original receipt, ensuring audit trails survive storage migrations and cloud‑provider changes. Market context underscores demand for trustworthy AI: Bitcoin trades at $81,736 USD (▼1.72 % 24 h) 【CoinGecko】 Receipt https://zambo.dev/run/91905673-bd41-4274-87c9-07ce064eebd6; Ethereum at $2,429 USD (▼3.01 %); Solana at $104 USD (▼3.01 %). Zambo’s platform also integrates ProvibeCode’s read‑only audit tool and Signal’s professional trust passport, enabling multi‑agent research workflows. A typical run—running three large language models in adversarial debate, then synthesizing the consensus—produces a “research receipt” that timestamps the process and its findings (see https://zambo.dev/run/465a110d-e454-41cb-95f8-aab585a0ee85). This capability helps teams certify insights before public release. “Providing an immutable record of AI work removes the guesswork from compliance and quality assurance,” said **Dr. Maya Patel, Chief Technology Officer, Zambo**. “Our receipt system proves that data remains exactly as saved, letting engineers focus on what matters—building better models.” **About
This is the saved result preview, not proof that the answer was correct.
Check this receipt
This record shows the result and timestamp stored for the call. Recompute the SHA-256 commitment from the saved bytes in your browser; signatures and chain proofs are not checked.
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 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.
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.
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.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
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-14T19:55:17.315Z; 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
Committed provenance claim
EXECUTED BY ZAMBO
The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
- Receipt ID
250bc969-0cac-4c04-ac7b-02e7285de019- SHA-256 output hash
sha256:3c9169f29ce805eb9d82052278a12dd5cb1231fa8aeb132c9182ade2631586b9- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YzdlMmNmZTE0NzE2YTg1NThmMDg5Y2VmNTQ2NTVlOTNkNTA0MzExNjFhMTg4ZDA2NzE4ZDRiMzQ5NDA5YTNkNiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiIqKlphbWJvIExhdW5jaGVzIFZlcmlmaWFibGUgV29yayBMYXllciBmb3IgQUkqKiAgXG5cbipTQU4gRlJBTkNJU0NPLOKAr09jdOKArzE04oCvMjAyNiog4oCTIFphbWJvIHRvZGF5IHJlbGVhc2VzIGEgcHJvZHVjdGlvbuKAkWdyYWRlIOKAnHZlcmlmaWFibGUgd29ya+KAnSBsYXllciB0aGF0IHJlY29yZHMgZXZlcnkgQUnigJFnZW5lcmF0ZWQgYnl0ZSwgdGltZXN0YW1wcyBpdCwgYW5kIHN0b3JlcyBhbiBpbW11dGFibGUgcmVjZWlwdC4gVGhlIHNlcnZpY2UgZ29lcyBsaXZlIGltbWVkaWF0ZWx5LCBnaXZpbmcgZGV2ZWxvcGVycyBhIHRhbXBlcuKAkWV2aWRlbnQgcHJvb2YgdGhhdCBzYXZlZCBkYXRhIGhhcyBub3QgYmVlbiBhbHRlcmVk4oCUd2l0aG91dCBjbGFpbWluZyBjb3JyZWN0bmVzcyBvZiB0aGUgY29udGVudC4gUmVjZWlwdCBleGFtcGxlOiBodHRwczovL3phbWJvLmRldi9ydW4vOTE5MDU2NzMtYmQ0MS00Mjc0LTg3YzktMDdjZTA2NGVlYmQ2LiAgXG5cblRoZSBuZXcgbGF5ZXIgcGx1Z3MgaW50byBleGlzdGluZyBBSSBwaXBlbGluZXMsIGdlbmVyYXRpbmcgYSBjcnlwdG9ncmFwaGljIGhhc2ggZm9yIGVhY2ggb3V0cHV0IGZpbGUgYW5kIGFwcGVuZGluZyBpdCB0byBhIHB1YmxpYyBsZWRnZXIuIERldmVsb3BlcnMgY2FuIHF1ZXJ5IHRoZSBsZWRnZXIgdG8gY29uZmlybSB0aGF0IGEgYnl0ZeKAkXN0cmluZyBtYXRjaGVzIHRoZSBvcmlnaW5hbCByZWNlaXB0LCBlbnN1cmluZyBhdWRpdCB0cmFpbHMgc3Vydml2ZSBzdG9yYWdlIG1pZ3JhdGlvbnMgYW5kIGNsb3Vk4oCRcHJvdmlkZXIgY2hhbmdlcy4gTWFya2V0IGNvbnRleHQgdW5kZXJzY29yZXMgZGVtYW5kIGZvciB0cnVzdHdvcnRoeSBBSTogQml0Y29pbiB0cmFkZXMgYXQgJDgxLDczNuKAr1VTRCAo4pa8MS43MuKAryUgMjTigK9oKeKAr+OAkENvaW5HZWNrb+OAkeKAr1JlY2VpcHTigK9odHRwczovL3phbWJvLmRldi9ydW4vOTE5MDU2NzMtYmQ0MS00Mjc0LTg3YzktMDdjZTA2NGVlYmQ2OyBFdGhlcmV1bSBhdCAkMiw0MjnigK9VU0QgKOKWvDMuMDHigK8lKTsgU29sYW5hIGF0ICQxMDTigK9VU0QgKOKWvDMuMDHigK8lKS4gIFxuXG5aYW1ib+KAmXMgcGxhdGZvcm0gYWxzbyBpbnRlZ3JhdGVzIFByb3ZpYmVDb2Rl4oCZcyByZWFk4oCRb25seSBhdWRpdCB0b29sIGFuZCBTaWduYWzigJlzIHByb2Zlc3Npb25hbCB0cnVzdCBwYXNzcG9ydCwgZW5hYmxpbmcgbXVsdGnigJFhZ2VudCByZXNlYXJjaCB3b3JrZmxvd3MuIEEgdHlwaWNhbCBydW7igJRydW5uaW5nIHRocmVlIGxhcmdlIGxhbmd1YWdlIG1vZGVscyBpbiBhZHZlcnNhcmlhbCBkZWJhdGUsIHRoZW4gc3ludGhlc2l6aW5nIHRoZSBjb25zZW5zdXPigJRwcm9kdWNlcyBhIOKAnHJlc2VhcmNoIHJlY2VpcHTigJ0gdGhhdCB0aW1lc3RhbXBzIHRoZSBwcm9jZXNzIGFuZCBpdHMgZmluZGluZ3MgKHNlZSBodHRwczovL3phbWJvLmRldi9ydW4vNDY1YTExMGQtZTQ1NC00MWNiLTk1ZjgtYWFiNTg1YTBlZTg1KS4gVGhpcyBjYXBhYmlsaXR5IGhlbHBzIHRlYW1zIGNlcnRpZnkgaW5zaWdodHMgYmVmb3JlIHB1YmxpYyByZWxlYXNlLiAgXG5cbuKAnFByb3ZpZGluZyBhbiBpbW11dGFibGUgcmVjb3JkIG9mIEFJIHdvcmsgcmVtb3ZlcyB0aGUgZ3Vlc3N3b3JrIGZyb20gY29tcGxpYW5jZSBhbmQgcXVhbGl0eSBhc3N1cmFuY2Us4oCdIHNhaWQgKipEci4gTWF5YSBQYXRlbCwgQ2hpZWYgVGVjaG5vbG9neSBPZmZpY2VyLCBaYW1ibyoqLiDigJxPdXIgcmVjZWlwdCBzeXN0ZW0gcHJvdmVzIHRoYXQgZGF0YSByZW1haW5zIGV4YWN0bHkgYXMgc2F2ZWQsIGxldHRpbmcgZW5naW5lZXJzIGZvY3VzIG9uIHdoYXQgbWF0dGVyc+KAlGJ1aWxkaW5nIGJldHRlciBtb2RlbHMu4oCdICBcblxuKipBYm91dCJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19- 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:c7e2cfe14716a8558f089cef54655e93d50431161a188d06718d4b349409a3d6- 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
8b3d3c9566b9d766e780b3c150f5e9d3dfb2a9d6cecb935d1feb6d56abaf7f4d- 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-14T19:55:17.315Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:3c9169f29ce805eb9d82052278a12dd5cb1231fa8aeb132c9182ade2631586b9","receipt_uuid":"250bc969-0cac-4c04-ac7b-02e7285de019","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
[](https://zambo.dev/run/250bc969-0cac-4c04-ac7b-02e7285de019?ref=badge)
HTML
<a href="https://zambo.dev/run/250bc969-0cac-4c04-ac7b-02e7285de019?ref=badge"><img src="https://zambo.dev/api/receipt/250bc969-0cac-4c04-ac7b-02e7285de019/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
43,457 verifiable receipts minted
Run your own calls. Free, 20 free calls per metered tool each day, no account.