Verifiable receipt a1adbc5c - 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
Observed result
{"status":"executed","primary_tool":"live_price","executed":true,"executed_tools":["live_price"],"result":"BTC · $85,325.00 USD\n▲ 0.47% (24h) · Market cap: $1714.44B\n\nLive price via CoinGecko · Sun, 04 Oct 2026 18:52:34 GMT","verify":{"status":"complete","message":"BTC-USD price and source were returned by the live price provider."}}
Verify this receipt
This is a verifiable receipt: the result above is hashed and timestamped at a permanent URL.
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?
An AI agent completed a tool call through Zambo, and this page records the result. The SHA-256 hash below fingerprints exactly what the agent produced. The timestamp shows when it ran. The Nostr anchor posts that fingerprint to public relays, so the record exists outside Zambo too. 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.
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, using the same tool and 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-10-04T18:52:34.123Z
Proof of observed execution
EXECUTED BY ZAMBO
- Receipt ID
a1adbc5c-d5fa-44ce-90df-3ec91af83248- SHA-256 output hash
sha256:fd5d734eb84f8d6347269288ff8751fbf66531b634b9a9194272dcfdd7453184- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ODg2YmM4NTZkOTA2NmU3ZWQ4ZWI0NjI3YzhmOTllNWJhOTM5MDQ4Y2E5OTRkYzJjYzE0ODIxYjI4NDVjZDEyNSIsInR5cGUiOiJhbm9ueW1vdXMifSwib3V0cHV0Ijp7ImV4ZWN1dGVkIjp0cnVlLCJleGVjdXRlZF90b29scyI6WyJsaXZlX3ByaWNlIl0sInByaW1hcnlfdG9vbCI6ImxpdmVfcHJpY2UiLCJyZXN1bHQiOiJCVEMgwrcgJDg1LDMyNS4wMCBVU0RcbuKWsiAwLjQ3JSAoMjRoKSDCtyBNYXJrZXQgY2FwOiAkMTcxNC40NEJcblxuTGl2ZSBwcmljZSB2aWEgQ29pbkdlY2tvIMK3IFN1biwgMDQgT2N0IDIwMjYgMTg6NTI6MzQgR01UIiwic3RhdHVzIjoiZXhlY3V0ZWQiLCJ2ZXJpZnkiOnsibWVzc2FnZSI6IkJUQy1VU0QgcHJpY2UgYW5kIHNvdXJjZSB3ZXJlIHJldHVybmVkIGJ5IHRoZSBsaXZlIHByaWNlIHByb3ZpZGVyLiIsInN0YXR1cyI6ImNvbXBsZXRlIn19LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC4zIiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiemFtYm9fdW5pdmVyc2FsIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=- Timestamp
Bound call context
- Receipt schema
0.3- Tool name
zambo_universal- Tool version
4.0.0- Permission scope
public- Caller type
anonymous- Caller ID
sha256:886bc856d9066e7ed8eb4627c8f99e5ba939048ca994dc2cc14821b2845cd125- 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:555b9f90b92b8c0e14938706460c81663c6984a04c8d1df09cdbabce9c83caab- Byte length
- 97
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:555b9f90b92b8c0e14938706460c81663c6984a04c8d1df09cdbabce9c83caab
Neutral Nostr anchor
- Event ID
53e0961b22ff7dda44707060eea1a6bcdb4884235c00eac2c562e668e30e3085- 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-04T18:52:34.092Z","evidence_byte_length":97,"evidence_sha256":"sha256:555b9f90b92b8c0e14938706460c81663c6984a04c8d1df09cdbabce9c83caab","evidence_url":"https://zambo.dev/api/evidence/555b9f90b92b8c0e14938706460c81663c6984a04c8d1df09cdbabce9c83caab","output_sha256":"sha256:fd5d734eb84f8d6347269288ff8751fbf66531b634b9a9194272dcfdd7453184","receipt_uuid":"a1adbc5c-d5fa-44ce-90df-3ec91af83248","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 does not say verified, do not 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/a1adbc5c-d5fa-44ce-90df-3ec91af83248)
HTML
<a href="https://zambo.dev/run/a1adbc5c-d5fa-44ce-90df-3ec91af83248"><img src="https://zambo.dev/api/receipt/a1adbc5c-d5fa-44ce-90df-3ec91af83248/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent verifiable receipts
39,455 verifiable receipts minted
Run your own calls. Free, 20 calls per tool per day, no account.