Verifiable receipt 0e110ec3 - live_price result | Zambo
Verifiable receipt for a live_price call on Zambo: BTC · $76,374.00 USD ▲ 0.93% (24h) · Market cap: $1533.99B 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
BTC · $76,374.00 USD ▲ 0.93% (24h) · Market cap: $1533.99B Live price via CoinGecko · Thu, 17 Sep 2026 22:08:38 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:38.323Z
Proof of observed execution
EXECUTED BY ZAMBO
- Receipt ID
0e110ec3-2643-419b-b392-6dedbcf3baee- SHA-256 output hash
sha256:015b0affecf021a4e77a9b132bff1d5bda00b271f691a62c98ecae5844d4b9ef- Canonical bytes
eyJ0ZXh0IjoiQlRDIMK3ICQ3NiwzNzQuMDAgVVNEXG7ilrIgMC45MyUgKDI0aCkgwrcgTWFya2V0IGNhcDogJDE1MzMuOTlCXG5cbkxpdmUgcHJpY2UgdmlhIENvaW5HZWNrbyDCtyBUaHUsIDE3IFNlcCAyMDI2IDIyOjA4OjM4IEdNVCJ9- 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:579c3babfda79ff4c6d45227aa2380f07b87504b8c31bc6e71b905fef9e19348- Byte length
- 97
Neutral Nostr anchor
- Event ID
47363ea4f1cd97c24d1eb5701749cc8831bb55a63166b419e66fd51390b39a8b- 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/0e110ec3-2643-419b-b392-6dedbcf3baee)
HTML
<a href="https://zambo.dev/run/0e110ec3-2643-419b-b392-6dedbcf3baee"><img src="https://zambo.dev/api/receipt/0e110ec3-2643-419b-b392-6dedbcf3baee/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent verifiable receipts
33,419 verifiable receipts minted