Verifiable receipt 1b9afbee - live_price result | Zambo
Verifiable receipt for a live_price call on Zambo: USD-COIN · $0.9997 USD ▼ 0.01% (24h) · Market cap: $73.86B Live price via CoinGecko · Thu, 17 Sep 2026 22:08:
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.
Observed result
USD-COIN · $0.9997 USD ▼ 0.01% (24h) · Market cap: $73.86B Live price via CoinGecko · Thu, 17 Sep 2026 22:08:43 GMT
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-09-17T22:08:43.705Z
Proof of observed execution
EXECUTED BY ZAMBO
- Receipt ID
1b9afbee-e86a-4a6c-b6ed-5a440e27f826- SHA-256 output hash
sha256:67cd0eaffd8457ad5125dd335345d9e99f74ca47fb48e5fd49aaa43b0a8c4504- Canonical bytes
eyJ0ZXh0IjoiVVNELUNPSU4gwrcgJDAuOTk5NyBVU0RcbuKWvCAwLjAxJSAoMjRoKSDCtyBNYXJrZXQgY2FwOiAkNzMuODZCXG5cbkxpdmUgcHJpY2UgdmlhIENvaW5HZWNrbyDCtyBUaHUsIDE3IFNlcCAyMDI2IDIyOjA4OjQzIEdNVCJ9- Timestamp
Bound call context
- Receipt schema
0.2- v0.2 receipt; call-context metadata was not recorded.
Bound upstream evidence
- Status
- captured
- Evidence SHA-256
sha256:b7be2c507ba991c11e89426d451b3b7d06c6d7ef3cee803f252aa729ab7fc910- Byte length
- 102
Neutral Nostr anchor
- Event ID
0a0563b3ba0ad9e626fba3c06d77b5641c7455ab2a2c7e8e360ed6f964a920d6- Anchor status
- partial
- Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41
Relay hints: wss://relay.damus.io · wss://nos.lol · wss://relay.primal.net
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/1b9afbee-e86a-4a6c-b6ed-5a440e27f826)
HTML
<a href="https://zambo.dev/run/1b9afbee-e86a-4a6c-b6ed-5a440e27f826"><img src="https://zambo.dev/api/receipt/1b9afbee-e86a-4a6c-b6ed-5a440e27f826/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent verifiable receipts
33,419 verifiable receipts minted