Verifiable receipt 43084cdd - 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: The Substrate Layer is ready for your research stack Hi [Name], No pleasantries. Just the
Observed result
Subject: Zambo is live: The Substrate Layer is ready for your research stack Hi [Name], No pleasantries. Just the news: Zambo has launched, and the Substrate Layer is fully executable in chat right now. If you are researching AI breakthroughs, this tool changes how you handle source-backed data. It is a living research machine tracking 51 lifeforms through adversarial research. It does not guess. It provides a read-only research feed of verified breakthroughs, complete with relevance scores and clear reasoning for why each item matters to your specific query. You can run the `substrate_breakthroughs` call immediately. It is free, unlimited on the free tier, and included in the Zambo Pass. There are no approval hurdles and no side effects beyond the data itself. We also tested VeriAI for cryptographic trust scoring. It is live at veriai.site, but note that it currently requires a human web action rather than a direct MCP route. We are treating it as a complementary workflow, not an automated pipeline. The receipt for this verification run is live at: https://zambo.dev/run/167f08a3-3fd0-483c-ac13-a843c16e8bb5 This link proves the saved bytes are unchanged. It does not prove correctness, only integrity. **Next Step:** Run `substrate_breakthroughs({})` in your preferred environment. Check the `breakthroughs` array and the `count` field. If the relevance scores align with your current research focus, you have a reliable, real-time feed. If not, ignore it. No commitment required. The tool is ready. The data is live. Best, [Your Name] [Your Title] Zambo
This is the saved result preview, not proof that the answer was correct.
Check this receipt
This page shows the result and when it was saved. Use the receipt checker to see whether the saved result has changed.
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.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
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-16T10:30:53.620Z; 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
43084cdd-5abb-46aa-9fb4-388dc7dcd44d- SHA-256 output hash
sha256:de6499fae1885e5a070248a3bb7267ce529236aff6dd336e0d847eb7fc54e22f- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NWJmYWNmNDgzMDY2NjVhMzdlODkwOWUzMDdkYmE1Zjk0MjA0YWRiY2I5YTJmOTUwYzgwZTQ2YTBkYzYwNjdjYiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiBUaGUgU3Vic3RyYXRlIExheWVyIGlzIHJlYWR5IGZvciB5b3VyIHJlc2VhcmNoIHN0YWNrXG5cbkhpIFtOYW1lXSxcblxuTm8gcGxlYXNhbnRyaWVzLiBKdXN0IHRoZSBuZXdzOiBaYW1ibyBoYXMgbGF1bmNoZWQsIGFuZCB0aGUgU3Vic3RyYXRlIExheWVyIGlzIGZ1bGx5IGV4ZWN1dGFibGUgaW4gY2hhdCByaWdodCBub3cuXG5cbklmIHlvdSBhcmUgcmVzZWFyY2hpbmcgQUkgYnJlYWt0aHJvdWdocywgdGhpcyB0b29sIGNoYW5nZXMgaG93IHlvdSBoYW5kbGUgc291cmNlLWJhY2tlZCBkYXRhLiBJdCBpcyBhIGxpdmluZyByZXNlYXJjaCBtYWNoaW5lIHRyYWNraW5nIDUxIGxpZmVmb3JtcyB0aHJvdWdoIGFkdmVyc2FyaWFsIHJlc2VhcmNoLiBJdCBkb2VzIG5vdCBndWVzcy4gSXQgcHJvdmlkZXMgYSByZWFkLW9ubHkgcmVzZWFyY2ggZmVlZCBvZiB2ZXJpZmllZCBicmVha3Rocm91Z2hzLCBjb21wbGV0ZSB3aXRoIHJlbGV2YW5jZSBzY29yZXMgYW5kIGNsZWFyIHJlYXNvbmluZyBmb3Igd2h5IGVhY2ggaXRlbSBtYXR0ZXJzIHRvIHlvdXIgc3BlY2lmaWMgcXVlcnkuXG5cbllvdSBjYW4gcnVuIHRoZSBgc3Vic3RyYXRlX2JyZWFrdGhyb3VnaHNgIGNhbGwgaW1tZWRpYXRlbHkuIEl0IGlzIGZyZWUsIHVubGltaXRlZCBvbiB0aGUgZnJlZSB0aWVyLCBhbmQgaW5jbHVkZWQgaW4gdGhlIFphbWJvIFBhc3MuIFRoZXJlIGFyZSBubyBhcHByb3ZhbCBodXJkbGVzIGFuZCBubyBzaWRlIGVmZmVjdHMgYmV5b25kIHRoZSBkYXRhIGl0c2VsZi5cblxuV2UgYWxzbyB0ZXN0ZWQgVmVyaUFJIGZvciBjcnlwdG9ncmFwaGljIHRydXN0IHNjb3JpbmcuIEl0IGlzIGxpdmUgYXQgdmVyaWFpLnNpdGUsIGJ1dCBub3RlIHRoYXQgaXQgY3VycmVudGx5IHJlcXVpcmVzIGEgaHVtYW4gd2ViIGFjdGlvbiByYXRoZXIgdGhhbiBhIGRpcmVjdCBNQ1Agcm91dGUuIFdlIGFyZSB0cmVhdGluZyBpdCBhcyBhIGNvbXBsZW1lbnRhcnkgd29ya2Zsb3csIG5vdCBhbiBhdXRvbWF0ZWQgcGlwZWxpbmUuXG5cblRoZSByZWNlaXB0IGZvciB0aGlzIHZlcmlmaWNhdGlvbiBydW4gaXMgbGl2ZSBhdDpcbmh0dHBzOi8vemFtYm8uZGV2L3J1bi8xNjdmMDhhMy0zZmQwLTQ4M2MtYWMxMy1hODQzYzE2ZThiYjVcblxuVGhpcyBsaW5rIHByb3ZlcyB0aGUgc2F2ZWQgYnl0ZXMgYXJlIHVuY2hhbmdlZC4gSXQgZG9lcyBub3QgcHJvdmUgY29ycmVjdG5lc3MsIG9ubHkgaW50ZWdyaXR5LlxuXG4qKk5leHQgU3RlcDoqKlxuUnVuIGBzdWJzdHJhdGVfYnJlYWt0aHJvdWdocyh7fSlgIGluIHlvdXIgcHJlZmVycmVkIGVudmlyb25tZW50LiBDaGVjayB0aGUgYGJyZWFrdGhyb3VnaHNgIGFycmF5IGFuZCB0aGUgYGNvdW50YCBmaWVsZC4gSWYgdGhlIHJlbGV2YW5jZSBzY29yZXMgYWxpZ24gd2l0aCB5b3VyIGN1cnJlbnQgcmVzZWFyY2ggZm9jdXMsIHlvdSBoYXZlIGEgcmVsaWFibGUsIHJlYWwtdGltZSBmZWVkLiBJZiBub3QsIGlnbm9yZSBpdC4gTm8gY29tbWl0bWVudCByZXF1aXJlZC5cblxuVGhlIHRvb2wgaXMgcmVhZHkuIFRoZSBkYXRhIGlzIGxpdmUuXG5cbkJlc3QsXG5cbltZb3VyIE5hbWVdXG5bWW91ciBUaXRsZV1cblphbWJvIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6IndyaXRlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=- 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:5bfacf48306665a37e8909e307dba5f94204adbcb9a2f950c80e46a0dc6067cb- 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
936d7e726bc8eabbe59bcbd7378844fba9913aef9eae8e8abae730d56a4262fe- 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-16T10:30:53.620Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:de6499fae1885e5a070248a3bb7267ce529236aff6dd336e0d847eb7fc54e22f","receipt_uuid":"43084cdd-5abb-46aa-9fb4-388dc7dcd44d","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/43084cdd-5abb-46aa-9fb4-388dc7dcd44d?ref=badge)
HTML
<a href="https://zambo.dev/run/43084cdd-5abb-46aa-9fb4-388dc7dcd44d?ref=badge"><img src="https://zambo.dev/api/receipt/43084cdd-5abb-46aa-9fb4-388dc7dcd44d/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
44,722 verifiable receipts minted
Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.