BTC price, saved and checkable

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-10-06T22:39:23.078Z; external immutability is not checked

Committed provenance claim

EXECUTED BY ZAMBO

legacy receipt, provenance not cryptographically bound

Receipt ID

18464583-6f07-497c-8209-d805f3d0480e

SHA-256 output hash

sha256:7c9600b380527bf5bf71d62a0965fe98cd1ef017d8e9471270131d96f197b6bd

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6Njg0Y2YxZWY1MTVhNGJiY2M3Mzg1ZjRlOWFhYTI1NGE3N2U4Yjk3NmQwZjM0MThiNGM3OTUxMzlkNWUwM2JjOCIsInR5cGUiOiJhbm9ueW1vdXMifSwib3V0cHV0Ijp7InRleHQiOiJCVEMgwrcgJDg1LDUyMS4wMCBVU0RcbuKWvCAwLjQ2JSAoMjRoKSDCtyBNYXJrZXQgY2FwOiAkMTcxOC40N0JcblxuTGl2ZSBwcmljZSB2aWEgQ29pbkdlY2tvIMK3IFR1ZSwgMDYgT2N0IDIwMjYgMjI6Mzk6MjIgR01UIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjMiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImxpdmVfcHJpY2UiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-10-06T22:39:23.078Z

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:684cf1ef515a4bbcc7385f4e9aaa254a77e8b976d0f3418b4c795139d5e03bc8

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:5d9fd6055b0ae2b9654f12954d6dbe0eac22332b39d624c9aa44812bd83c02c5

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-10-06T22:39:22.985Z · raw response hash: sha256:5d9fd6055b0ae2b9654f12954d6dbe0eac22332b39d624c9aa44812bd83c02c5

Neutral Nostr anchor

Event ID

4bdb2358d320aeff1ba5368e44c44d215429b051a15b58e0c79e26799b465877

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-10-06T22:39:23.005Z","evidence_byte_length":98,"evidence_sha256":"sha256:5d9fd6055b0ae2b9654f12954d6dbe0eac22332b39d624c9aa44812bd83c02c5","evidence_url":"https://zambo.dev/api/evidence/5d9fd6055b0ae2b9654f12954d6dbe0eac22332b39d624c9aa44812bd83c02c5","output_sha256":"sha256:7c9600b380527bf5bf71d62a0965fe98cd1ef017d8e9471270131d96f197b6bd","receipt_uuid":"18464583-6f07-497c-8209-d805f3d0480e","schema_version":"zambo-receipt-anchor/1"}

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

Check this hash yourself

Receipt commitment: verification_failed. This checks the saved bytes, not whether 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.