Verifiable receipt 89e170e8 - live_price result | Zambo
Verifiable receipt for a live_price call on Zambo: ADA · $0.1956 USD ▼ 4.59% (24h) · Market cap: $7.34B Live price via CoinGecko · Wed, 16 Sep 2026 04:52:49 GMT
Observed result
ADA · $0.1956 USD ▼ 4.59% (24h) · Market cap: $7.34B Live price via CoinGecko · Wed, 16 Sep 2026 04:52:49 GMT
Check this receipt
This record shows the result and timestamp stored for the call. Recompute the SHA-256 commitment from the saved bytes in your browser; signatures and chain proofs are not checked.
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?
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.
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.
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.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
Verification checks
- SHA-256 commitment: NOT CHECKED; canonical bytes are unavailable
- Provenance binding: NOT_CHECKED; Canonical bytes are unavailable; provenance labels are not authenticated.
- 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-09-16T04:52:50.022Z; external immutability is not checked
Committed provenance claim
EXECUTED BY ZAMBO
Canonical bytes are unavailable; provenance labels are not authenticated.
- Receipt ID
89e170e8-aa8a-43cb-8e05-3fba269ea6c0- SHA-256 output hash
sha256:f1214a166056bbeb6acfe7dde7670657f923de8628643e91197a23fb62c43a3c- Canonical bytes
- Unavailable for legacy receipts
- Timestamp
Bound call context
- Receipt schema
0.2- v0.2 receipt; call-context metadata was not recorded.
Bound upstream evidence
- Status
- unavailable
- Evidence SHA-256
unavailable- Byte length
- unavailable
Neutral Nostr anchor
- Event ID
pending/unavailable- Anchor status
- unavailable
- Public key
unavailable
Relay hints: unavailable
Anchor status "unavailable": The anchor status is not available.
Check this hash yourself
Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. Signature and chain remain NOT CHECKED unless a real signature verifier or chain proof is supplied. There is no combined “verified” verdict.
Embed this receipt
Markdown
[](https://zambo.dev/run/89e170e8-aa8a-43cb-8e05-3fba269ea6c0)
HTML
<a href="https://zambo.dev/run/89e170e8-aa8a-43cb-8e05-3fba269ea6c0"><img src="https://zambo.dev/api/receipt/89e170e8-aa8a-43cb-8e05-3fba269ea6c0/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
40,841 verifiable receipts minted
Run your own calls. Free, 20 free calls per metered tool each day, no account.