Verifiable receipt 72245c61 - live_price result | Zambo

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 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.

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.

Verification checks

• SHA-256 commitment: Checked independently against the exact decoded bytes
• Provenance binding: LEGACY; legacy receipt, provenance not cryptographically bound
• Metadata binding: LEGACY; legacy receipt, metadata is not cryptographically bound
• 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-28T11:18:52.110Z; external immutability is not checked

Committed provenance claim

EXECUTED BY ZAMBO

legacy receipt, provenance not cryptographically bound

Receipt ID

72245c61-7730-4fa1-abc4-a94e789bda28

SHA-256 output hash

sha256:d148a3442a8d50c1563424bfef311b8ca34499174b7d24ce8fb7c3924f30e682

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OTE3ODAzNWU1YTliNTVjZjk3OWU3NTEyN2FiODg4NjI5YTk0ZjJmZDBlMTlmMjEwZmQ0NmQ0ZDJlYTJkOTdlNyIsInR5cGUiOiJhbm9ueW1vdXMifSwib3V0cHV0Ijp7InRleHQiOiJCVEMgwrcgJDgyLDk4My4wMCBVU0RcbuKWvCAyLjE5JSAoMjRoKSDCtyBNYXJrZXQgY2FwOiAkMTY2Ny4wNUJcblxuTGl2ZSBwcmljZSB2aWEgQ29pbkdlY2tvIMK3IE1vbiwgMjggU2VwIDIwMjYgMTE6MTg6NTIgR01UIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjMiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImxpdmVfcHJpY2UiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-09-28T11:18:52.110Z

Bound call context

Receipt schema

0.3

Tool name

live_price

Tool version

4.0.0

Permission scope

public

Caller type

anonymous

Caller ID

sha256:9178035e5a9b55cf979e75127ab888629a94f2fd0e19f210fd46d4d2ea2d97e7

Declared side effects

none

Side-effects schema

zambo-side-effects/1

Declaration hash

sha256:45aad38f3aa982b9aafe92ecb416ebe98791eddbaf8ab6df0bd08605b7c1bfee

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:b05977354b0c5cd3c46cc1fb302a7257a18991a74c449193b44e854f7785866b

Byte length

98

Fetch exact evidence bytes

Upstream provenance

This receipt is independently auditable against the named upstream source. This is not a mathematical correctness claim.

• Source: CoinGecko · queried at: 2026-09-28T11:18:52.038Z · raw response hash: sha256:b05977354b0c5cd3c46cc1fb302a7257a18991a74c449193b44e854f7785866b

Neutral Nostr anchor

Event ID

9e2e2276b5393f58ee08418ccd10bb91c3bec27b2207b4ea855919e639bfa02e

Anchor status

published

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-28T11:18:52.083Z","evidence_byte_length":98,"evidence_sha256":"sha256:b05977354b0c5cd3c46cc1fb302a7257a18991a74c449193b44e854f7785866b","evidence_url":"https://zambo.dev/api/evidence/b05977354b0c5cd3c46cc1fb302a7257a18991a74c449193b44e854f7785866b","output_sha256":"sha256:d148a3442a8d50c1563424bfef311b8ca34499174b7d24ce8fb7c3924f30e682","receipt_uuid":"72245c61-7730-4fa1-abc4-a94e789bda28","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

Check this hash yourself

API v2 status: verification_failed. This status summarizes the v2 commitment and provenance checks; it does not prove the answer was correct. Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. See the Nostr anchor event on a public viewer. The fingerprint is timestamped outside Zambo too.