Verifiable receipt f26edf29 - 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 Launch: Two Verified AI Capabilities Hi [Name], I’m skipping the pleasantries to share what we just

Observed result

Subject: Zambo Launch: Two Verified AI Capabilities Hi [Name], I’m skipping the pleasantries to share what we just shipped. Zambo is live, and the initial audit confirms two specific, source-backed capabilities ready for use. First is **Substrate Breakthroughs**. This is a living AI research machine featuring 51 lifeforms and adversarial research logic. It is fully executable in chat. You get unlimited access on the free tier, or it’s included in the Zambo Pass. The tool returns a read-only research feed with no side effects. It is retry-safe and requires no approval. If you use it, you’ll get an object array of breakthroughs and a count. It is relevant for AI research workflows. Second is **VeriAI**. This provides a cryptographic trust score for any AI-generated output. Note: VeriAI does not have a confirmed callable Zambo MCP route. It requires human web action via https://veriai.site. We are not claiming these tools solve every problem. We are stating that they work as documented. Here is the critical distinction: The receipt at https://zambo.dev/run/f72cfa69-9e82-426d-a4c0-56648b7ee381 proves the saved bytes are unchanged. It does **not** prove correctness. A receipt is a hash check, not a quality guarantee. We treat source-backed prospects as prospects, not customers. We do not invent findings. If you want to test the Substrate Breakthroughs tool, run `substrate_breakthroughs({})` now. It is free, immediate, and read-only. Let me know if you want to dig into the VeriAI web flow or test the Substrate layer. Best, [Your Name] 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:25:44.311Z; 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
f26edf29-619a-488a-a793-cd811cac91e8
SHA-256 output hash
sha256:a5230f3064a003828abb969c5ce70a0a744e0c2fe7b69316a9244317a3e7b620
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6N2I1NjFmNmMxNmU3MThiYTk0NDQxNGI2Y2VjMzAyZDdiN2M3NTAzN2VhNGZkYjBlZGNjMjU4NjkyN2JmYjg2MiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBMYXVuY2g6IFR3byBWZXJpZmllZCBBSSBDYXBhYmlsaXRpZXNcblxuSGkgW05hbWVdLFxuXG5J4oCZbSBza2lwcGluZyB0aGUgcGxlYXNhbnRyaWVzIHRvIHNoYXJlIHdoYXQgd2UganVzdCBzaGlwcGVkLiBaYW1ibyBpcyBsaXZlLCBhbmQgdGhlIGluaXRpYWwgYXVkaXQgY29uZmlybXMgdHdvIHNwZWNpZmljLCBzb3VyY2UtYmFja2VkIGNhcGFiaWxpdGllcyByZWFkeSBmb3IgdXNlLlxuXG5GaXJzdCBpcyAqKlN1YnN0cmF0ZSBCcmVha3Rocm91Z2hzKiouIFRoaXMgaXMgYSBsaXZpbmcgQUkgcmVzZWFyY2ggbWFjaGluZSBmZWF0dXJpbmcgNTEgbGlmZWZvcm1zIGFuZCBhZHZlcnNhcmlhbCByZXNlYXJjaCBsb2dpYy4gSXQgaXMgZnVsbHkgZXhlY3V0YWJsZSBpbiBjaGF0LiBZb3UgZ2V0IHVubGltaXRlZCBhY2Nlc3Mgb24gdGhlIGZyZWUgdGllciwgb3IgaXTigJlzIGluY2x1ZGVkIGluIHRoZSBaYW1ibyBQYXNzLiBUaGUgdG9vbCByZXR1cm5zIGEgcmVhZC1vbmx5IHJlc2VhcmNoIGZlZWQgd2l0aCBubyBzaWRlIGVmZmVjdHMuIEl0IGlzIHJldHJ5LXNhZmUgYW5kIHJlcXVpcmVzIG5vIGFwcHJvdmFsLiBJZiB5b3UgdXNlIGl0LCB5b3XigJlsbCBnZXQgYW4gb2JqZWN0IGFycmF5IG9mIGJyZWFrdGhyb3VnaHMgYW5kIGEgY291bnQuIEl0IGlzIHJlbGV2YW50IGZvciBBSSByZXNlYXJjaCB3b3JrZmxvd3MuXG5cblNlY29uZCBpcyAqKlZlcmlBSSoqLiBUaGlzIHByb3ZpZGVzIGEgY3J5cHRvZ3JhcGhpYyB0cnVzdCBzY29yZSBmb3IgYW55IEFJLWdlbmVyYXRlZCBvdXRwdXQuIE5vdGU6IFZlcmlBSSBkb2VzIG5vdCBoYXZlIGEgY29uZmlybWVkIGNhbGxhYmxlIFphbWJvIE1DUCByb3V0ZS4gSXQgcmVxdWlyZXMgaHVtYW4gd2ViIGFjdGlvbiB2aWEgaHR0cHM6Ly92ZXJpYWkuc2l0ZS5cblxuV2UgYXJlIG5vdCBjbGFpbWluZyB0aGVzZSB0b29scyBzb2x2ZSBldmVyeSBwcm9ibGVtLiBXZSBhcmUgc3RhdGluZyB0aGF0IHRoZXkgd29yayBhcyBkb2N1bWVudGVkLlxuXG5IZXJlIGlzIHRoZSBjcml0aWNhbCBkaXN0aW5jdGlvbjogVGhlIHJlY2VpcHQgYXQgaHR0cHM6Ly96YW1iby5kZXYvcnVuL2Y3MmNmYTY5LTllODItNDI2ZC1hNGMwLTU2NjQ4YjdlZTM4MSBwcm92ZXMgdGhlIHNhdmVkIGJ5dGVzIGFyZSB1bmNoYW5nZWQuIEl0IGRvZXMgKipub3QqKiBwcm92ZSBjb3JyZWN0bmVzcy4gQSByZWNlaXB0IGlzIGEgaGFzaCBjaGVjaywgbm90IGEgcXVhbGl0eSBndWFyYW50ZWUuIFdlIHRyZWF0IHNvdXJjZS1iYWNrZWQgcHJvc3BlY3RzIGFzIHByb3NwZWN0cywgbm90IGN1c3RvbWVycy4gV2UgZG8gbm90IGludmVudCBmaW5kaW5ncy5cblxuSWYgeW91IHdhbnQgdG8gdGVzdCB0aGUgU3Vic3RyYXRlIEJyZWFrdGhyb3VnaHMgdG9vbCwgcnVuIGBzdWJzdHJhdGVfYnJlYWt0aHJvdWdocyh7fSlgIG5vdy4gSXQgaXMgZnJlZSwgaW1tZWRpYXRlLCBhbmQgcmVhZC1vbmx5LlxuXG5MZXQgbWUga25vdyBpZiB5b3Ugd2FudCB0byBkaWcgaW50byB0aGUgVmVyaUFJIHdlYiBmbG93IG9yIHRlc3QgdGhlIFN1YnN0cmF0ZSBsYXllci5cblxuQmVzdCxcblxuW1lvdXIgTmFtZV1cblphbWJvIFRlYW0ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoid3JpdGUiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:7b561f6c16e718ba944414b6cec302d7b7c75037ea4fdb0edcc2586927bfb862
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
fa9e7a56951402671701042780c9a2b72940fef4e9c8c340ea0d5b1ba03d2ef5
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-16T16:25:44.311Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:a5230f3064a003828abb969c5ce70a0a744e0c2fe7b69316a9244317a3e7b620","receipt_uuid":"f26edf29-619a-488a-a793-cd811cac91e8","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/f26edf29-619a-488a-a793-cd811cac91e8/badge.svg)](https://zambo.dev/run/f26edf29-619a-488a-a793-cd811cac91e8?ref=badge)

HTML

<a href="https://zambo.dev/run/f26edf29-619a-488a-a793-cd811cac91e8?ref=badge"><img src="https://zambo.dev/api/receipt/f26edf29-619a-488a-a793-cd811cac91e8/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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