CRYPTO 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-03T21:06:09.321Z; external immutability is not checked

Committed provenance claim

EXECUTED BY ZAMBO

legacy receipt, provenance not cryptographically bound

Receipt ID

6735bf37-723a-4e90-ad62-dc931dac308d

SHA-256 output hash

sha256:78535898a983424d6d1250057220d05d47eff501989f37e0198d6d4d7f490380

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MGU5YzgxZDNlNWMwZDNhNzJjNWE0ODFhNjVmMWRjMzU4MjcyNTE4NjE2YzI2Yzg3YTRhZmRlYjhiNDAxYzdkNyIsInR5cGUiOiJhbm9ueW1vdXMifSwib3V0cHV0Ijp7ImVycm9yIjoiTm8gdmVyaWZpZWQgbGl2ZSBwcmljZSBpcyBhdmFpbGFibGUgZnJvbSBDb2luR2Vja28gb3IgQ29pbmJhc2UsIGFuZCBubyBjYWNoZWQgcHJpY2UgZXhpc3RzIHlldC4iLCJyZXRyeWFibGUiOnRydWUsInN0YXR1cyI6InByb3ZpZGVyX3VuYXZhaWxhYmxlIiwic3ltYm9sIjoiSFRUUDovL0VYQU1QTEUuSU5WQUxJRC9YIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjMiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImxpdmVfcHJpY2UiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-10-03T21:06:09.321Z

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:0e9c81d3e5c0d3a72c5a481a65f1dc358272518616c26c87a4afdeb8b401c7d7

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:44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a

Byte length

2

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-03T21:06:09.292Z · raw response hash: sha256:44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a

Neutral Nostr anchor

Event ID

bd8fb1bebfbb2f751c979661a9f45b29decf9526de1c70397ebe45500d4857f4

Anchor status

partial

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-03T21:06:09.292Z","evidence_byte_length":2,"evidence_sha256":"sha256:44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a","evidence_url":"https://zambo.dev/api/evidence/44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a","output_sha256":"sha256:78535898a983424d6d1250057220d05d47eff501989f37e0198d6d4d7f490380","receipt_uuid":"6735bf37-723a-4e90-ad62-dc931dac308d","schema_version":"zambo-receipt-anchor/1"}

Anchor status "partial": Published to some configured relay targets; publication was not confirmed by every configured relay.

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.