Verifiable receipt 2cf530ee - 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: Two tools, zero friction We shipped. Zambo is now operational. We focused on two core capa

Observed result

Subject: Zambo is live: Two tools, zero friction We shipped. Zambo is now operational. We focused on two core capabilities that solve specific bottlenecks in AI research and verification. No fluff, just the tools. **1. Substrate Layer** This is a living AI research machine. It houses 51 distinct lifeforms designed for adversarial research. It executes fully in chat with no approval gates. * **Access:** Free unlimited tier. Included in Zambo Pass. * **Status:** Fully executable. Read-only research feed. * **Why it matters:** It provides a dynamic, self-correcting environment for deep-dive AI analysis without manual orchestration. **2. VeriAI** A cryptographic trust score for any AI-generated output. It verifies data integrity. * **Access:** Web flow only. There is no confirmed callable MCP route for this specific tool yet. * **Action Required:** Use the public web interface at veriai.site to generate scores. * **Why it matters:** It bridges the gap between generated content and verifiable truth. **The Bottom Line** You can test Substrate Layer immediately. It is free, unlimited, and ready. For VeriAI, workflow integration requires the web step. We are not claiming these are perfect. We are claiming they are functional, accessible, and backed by source-verified research feeds. A receipt confirms our internal launch checks passed, but your usage will determine the real-world correctness. **Next Step** Run `substrate_breakthroughs({})` now. See the 51 lifeforms in action. Then, take one piece of AI output to veriai.site to test the trust score. Tell us if the Substrate feed feels too noisy or if the VeriAI web flow is too slow. We need raw feedback, not praise. 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-16T14:56:21.467Z; 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
2cf530ee-15e6-499f-a8fe-875699536f99
SHA-256 output hash
sha256:dc7be8f5ab2153d7151c9e791a862b173af6c9b2a667ca894f364273eaf396c8
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MmQyZWUxZGJhZDIwNmE5ZTU5MjRiYjlkZGUxYzQ2Mzk1N2ZjZGU5ZTRjMDNjOWE2NTk5OGFjZTQwYjI5YjFhYiIsImxhYmVsIjoiemFtYm8taG9tZS1kZW1vIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJTdWJqZWN0OiBaYW1ibyBpcyBsaXZlOiBUd28gdG9vbHMsIHplcm8gZnJpY3Rpb25cblxuV2Ugc2hpcHBlZC5cblxuWmFtYm8gaXMgbm93IG9wZXJhdGlvbmFsLiBXZSBmb2N1c2VkIG9uIHR3byBjb3JlIGNhcGFiaWxpdGllcyB0aGF0IHNvbHZlIHNwZWNpZmljIGJvdHRsZW5lY2tzIGluIEFJIHJlc2VhcmNoIGFuZCB2ZXJpZmljYXRpb24uIE5vIGZsdWZmLCBqdXN0IHRoZSB0b29scy5cblxuKioxLiBTdWJzdHJhdGUgTGF5ZXIqKlxuVGhpcyBpcyBhIGxpdmluZyBBSSByZXNlYXJjaCBtYWNoaW5lLiBJdCBob3VzZXMgNTEgZGlzdGluY3QgbGlmZWZvcm1zIGRlc2lnbmVkIGZvciBhZHZlcnNhcmlhbCByZXNlYXJjaC4gSXQgZXhlY3V0ZXMgZnVsbHkgaW4gY2hhdCB3aXRoIG5vIGFwcHJvdmFsIGdhdGVzLlxuKiAgICoqQWNjZXNzOioqIEZyZWUgdW5saW1pdGVkIHRpZXIuIEluY2x1ZGVkIGluIFphbWJvIFBhc3MuXG4qICAgKipTdGF0dXM6KiogRnVsbHkgZXhlY3V0YWJsZS4gUmVhZC1vbmx5IHJlc2VhcmNoIGZlZWQuXG4qICAgKipXaHkgaXQgbWF0dGVyczoqKiBJdCBwcm92aWRlcyBhIGR5bmFtaWMsIHNlbGYtY29ycmVjdGluZyBlbnZpcm9ubWVudCBmb3IgZGVlcC1kaXZlIEFJIGFuYWx5c2lzIHdpdGhvdXQgbWFudWFsIG9yY2hlc3RyYXRpb24uXG5cbioqMi4gVmVyaUFJKipcbkEgY3J5cHRvZ3JhcGhpYyB0cnVzdCBzY29yZSBmb3IgYW55IEFJLWdlbmVyYXRlZCBvdXRwdXQuIEl0IHZlcmlmaWVzIGRhdGEgaW50ZWdyaXR5LlxuKiAgICoqQWNjZXNzOioqIFdlYiBmbG93IG9ubHkuIFRoZXJlIGlzIG5vIGNvbmZpcm1lZCBjYWxsYWJsZSBNQ1Agcm91dGUgZm9yIHRoaXMgc3BlY2lmaWMgdG9vbCB5ZXQuXG4qICAgKipBY3Rpb24gUmVxdWlyZWQ6KiogVXNlIHRoZSBwdWJsaWMgd2ViIGludGVyZmFjZSBhdCB2ZXJpYWkuc2l0ZSB0byBnZW5lcmF0ZSBzY29yZXMuXG4qICAgKipXaHkgaXQgbWF0dGVyczoqKiBJdCBicmlkZ2VzIHRoZSBnYXAgYmV0d2VlbiBnZW5lcmF0ZWQgY29udGVudCBhbmQgdmVyaWZpYWJsZSB0cnV0aC5cblxuKipUaGUgQm90dG9tIExpbmUqKlxuWW91IGNhbiB0ZXN0IFN1YnN0cmF0ZSBMYXllciBpbW1lZGlhdGVseS4gSXQgaXMgZnJlZSwgdW5saW1pdGVkLCBhbmQgcmVhZHkuIEZvciBWZXJpQUksIHdvcmtmbG93IGludGVncmF0aW9uIHJlcXVpcmVzIHRoZSB3ZWIgc3RlcC5cblxuV2UgYXJlIG5vdCBjbGFpbWluZyB0aGVzZSBhcmUgcGVyZmVjdC4gV2UgYXJlIGNsYWltaW5nIHRoZXkgYXJlIGZ1bmN0aW9uYWwsIGFjY2Vzc2libGUsIGFuZCBiYWNrZWQgYnkgc291cmNlLXZlcmlmaWVkIHJlc2VhcmNoIGZlZWRzLiBBIHJlY2VpcHQgY29uZmlybXMgb3VyIGludGVybmFsIGxhdW5jaCBjaGVja3MgcGFzc2VkLCBidXQgeW91ciB1c2FnZSB3aWxsIGRldGVybWluZSB0aGUgcmVhbC13b3JsZCBjb3JyZWN0bmVzcy5cblxuKipOZXh0IFN0ZXAqKlxuUnVuIGBzdWJzdHJhdGVfYnJlYWt0aHJvdWdocyh7fSlgIG5vdy4gU2VlIHRoZSA1MSBsaWZlZm9ybXMgaW4gYWN0aW9uLiBUaGVuLCB0YWtlIG9uZSBwaWVjZSBvZiBBSSBvdXRwdXQgdG8gdmVyaWFpLnNpdGUgdG8gdGVzdCB0aGUgdHJ1c3Qgc2NvcmUuXG5cblRlbGwgdXMgaWYgdGhlIFN1YnN0cmF0ZSBmZWVkIGZlZWxzIHRvbyBub2lzeSBvciBpZiB0aGUgVmVyaUFJIHdlYiBmbG93IGlzIHRvbyBzbG93LiBXZSBuZWVkIHJhdyBmZWVkYmFjaywgbm90IHByYWlzZS5cblxuWmFtYm8gVGVhbSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ3cml0ZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
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:2d2ee1dbad206a9e5924bb9dde1c463957fcde9e4c03c9a65998ace40b29b1ab
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
f9d6492d1088ece328815b28ec372b6ff5c26f337c91fbea0e5bb3136de747a5
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:56:21.467Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:dc7be8f5ab2153d7151c9e791a862b173af6c9b2a667ca894f364273eaf396c8","receipt_uuid":"2cf530ee-15e6-499f-a8fe-875699536f99","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/2cf530ee-15e6-499f-a8fe-875699536f99/badge.svg)](https://zambo.dev/run/2cf530ee-15e6-499f-a8fe-875699536f99?ref=badge)

HTML

<a href="https://zambo.dev/run/2cf530ee-15e6-499f-a8fe-875699536f99?ref=badge"><img src="https://zambo.dev/api/receipt/2cf530ee-15e6-499f-a8fe-875699536f99/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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