Verifiable receipt 69990fa5 — zambo_universal result | Zambo
Verifiable receipt for a zambo_universal call on Zambo: {"status":"executed","primary_tool":"live_price","executed":true,"executed_tools":["live_price"],"result
What is this?
An AI agent did real work through Zambo, and this page is the proof. The SHA-256 hash below is a fingerprint of exactly what the agent produced — change one character of the output and the fingerprint changes. The timestamp shows when it ran. The Nostr anchor posts that fingerprint to public relays, so the record exists outside Zambo too — anyone can look it up by the event ID below. You don't have to take the agent's word for it. Check the hash yourself.
What is an execution receipt?
An execution receipt is the public record of one completed AI agent tool call. Read the canonical definition of an AI agent execution receipt.
Observed result
{"status":"executed","primary_tool":"live_price","executed":true,"executed_tools":["live_price"],"result":"ETH · $2,754.02 USD\n▲ 4.22% (24h) · Market cap: $336.15B\n\nLive price via CoinGecko · Mon, 21 Sep 2026 16:43:48 GMT","verify":{"status":"complete","message":"ETH-USD price and source were returned by the live price provider."}}
Keep the work moving
This receipt proves the call completed. When the free allowance is not enough, choose the access path that fits the job.
Or re-run this exact call — same tool, same arguments.
Share this receipt
Verification checks
- Integrity check: Recomputable from canonical bytes
- Issued by zambo.dev: Served from the zambo.dev receipt store
- Chain valid: Receipt hash chain is internally consistent
- Recorded in the immutable log: 2026-09-21T16:43:48.060Z
Proof of observed execution
- Receipt ID
69990fa5-2ddb-4ed4-99bd-8893f761291e- SHA-256 output hash
sha256:4fb8d32c753405c3218013c93cd2fec68d373399844c3a8cbd4708e09ef3726b- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NjAxNDMxMjM4ZDJkNzJmOGUzMjY4ZTNkMjFiMWQ3MjU3OTE5N2U2ZjJlZDJhMWE3N2ZkNjg4N2EwNzc3OWUxNCIsInR5cGUiOiJzZXNzaW9uIn0sIm91dHB1dCI6eyJleGVjdXRlZCI6dHJ1ZSwiZXhlY3V0ZWRfdG9vbHMiOlsibGl2ZV9wcmljZSJdLCJwcmltYXJ5X3Rvb2wiOiJsaXZlX3ByaWNlIiwicmVzdWx0IjoiRVRIIMK3ICQyLDc1NC4wMiBVU0RcbuKWsiA0LjIyJSAoMjRoKSDCtyBNYXJrZXQgY2FwOiAkMzM2LjE1QlxuXG5MaXZlIHByaWNlIHZpYSBDb2luR2Vja28gwrcgTW9uLCAyMSBTZXAgMjAyNiAxNjo0Mzo0OCBHTVQiLCJzdGF0dXMiOiJleGVjdXRlZCIsInZlcmlmeSI6eyJtZXNzYWdlIjoiRVRILVVTRCBwcmljZSBhbmQgc291cmNlIHdlcmUgcmV0dXJuZWQgYnkgdGhlIGxpdmUgcHJpY2UgcHJvdmlkZXIuIiwic3RhdHVzIjoiY29tcGxldGUifX0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjMiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ6YW1ib191bml2ZXJzYWwiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==- Timestamp
Bound call context
- Receipt schema
0.3- Tool name
zambo_universal- Tool version
4.0.0- Permission scope
public- Caller type
session- Caller ID
sha256:601431238d2d72f8e3268e3d21b1d72579197e6f2ed2a1a77fd6887a07779e14- Declared side effects
state_write- Side-effects schema
zambo-side-effects/1- Declaration hash
sha256:dfb4412aa429d3ac637a05668c435bcc90a251363fcdd49f7b85ae4ab55b5bc9
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
- captured
- Evidence SHA-256
sha256:5cc820f4260ea9207632af3ea8a7d759be54b36dbf409af8558ad50692cf43ab- Byte length
- 98
Upstream provenance
This receipt is independently auditable against the named upstream source. This is not a mathematical correctness claim.
-
Source: CoinGecko
· queried at:
· raw response hash:
sha256:5cc820f4260ea9207632af3ea8a7d759be54b36dbf409af8558ad50692cf43ab
Neutral Nostr anchor
- Event ID
9c93411d2d139c35077ac816d1ac54e98c46de6b18509739ad99067479174af9- 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-09-21T16:43:48.027Z","evidence_byte_length":98,"evidence_sha256":"sha256:5cc820f4260ea9207632af3ea8a7d759be54b36dbf409af8558ad50692cf43ab","evidence_url":"https://zambo.dev/api/evidence/5cc820f4260ea9207632af3ea8a7d759be54b36dbf409af8558ad50692cf43ab","output_sha256":"sha256:4fb8d32c753405c3218013c93cd2fec68d373399844c3a8cbd4708e09ef3726b","receipt_uuid":"69990fa5-2ddb-4ed4-99bd-8893f761291e","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
Open the verification endpoint — the server recomputes the SHA-256 from the stored bytes and answers verified:true. If it doesn't say verified, don't trust this page.
See the Nostr anchor event on a public viewer — the fingerprint is timestamped outside Zambo too.
Embed this receipt
Markdown
[](https://zambo.dev/run/69990fa5-2ddb-4ed4-99bd-8893f761291e)
HTML
<a href="https://zambo.dev/run/69990fa5-2ddb-4ed4-99bd-8893f761291e"><img src="https://zambo.dev/api/receipt/69990fa5-2ddb-4ed4-99bd-8893f761291e/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent verifiable receipts
32,890 verifiable receipts minted