Verifiable receipt 7bb64982 - zambo_universal 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: PASS; The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
• Metadata binding: PASS; metadata_hash matches the canonical metadata block.
• 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-16T15:26:33.248Z; external immutability is not checked

Committed provenance claim

EXECUTED BY ZAMBO

The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.

Receipt ID

7bb64982-2d3a-4c2a-bb15-8af7b2198e05

SHA-256 output hash

sha256:f5b384726645ebdaa236ea43877c62b57c6f771cf7f46b352f0e44286a08aee9

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NDQ5OWE5OTU5ZWVkZDI4MTg0MGJhZDdjYzdmMmIwNTg5OTgzMzAwNGRhNzAxMjM3ZWE1ODk0Y2FmNTI1MTNhYiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJleGVjdXRlZCI6dHJ1ZSwiZXhlY3V0ZWRfdG9vbHMiOlsibGl2ZV9wcmljZSJdLCJwcmltYXJ5X3Rvb2wiOiJsaXZlX3ByaWNlIiwicmVzdWx0IjoiQlRDIMK3ICQ4MSw1MjAuMDAgVVNEXG7ilrwgMC45MCUgKDI0aCkgwrcgTWFya2V0IGNhcDogJDE2MzguNDZCXG5cbkxpdmUgcHJpY2UgdmlhIENvaW5HZWNrbyDCtyBGcmksIDE2IE9jdCAyMDI2IDE1OjI2OjMzIEdNVCIsInN0YXR1cyI6ImV4ZWN1dGVkIiwidmVyaWZ5Ijp7Im1lc3NhZ2UiOiJCVEMtVVNEIHByaWNlIGFuZCBzb3VyY2Ugd2VyZSByZXR1cm5lZCBieSB0aGUgbGl2ZSBwcmljZSBwcm92aWRlci4iLCJzdGF0dXMiOiJjb21wbGV0ZSJ9fSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6InphbWJvX3VuaXZlcnNhbCIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-10-16T15:26:33.248Z

Bound call context

Receipt schema

0.4

Tool name

zambo_universal

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:4499a9959eedd281840bad7cc7f2b05899833004da701237ea5894caf52513ab

Declared side effects

state_write

Side-effects schema

zambo-side-effects/1

Declaration hash

sha256:dfb4412aa429d3ac637a05668c435bcc90a251363fcdd49f7b85ae4ab55b5bc9

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:864af12b4d99bde29de9a6003b395c189ed8757b2795d2f43f6a054a172a4f45

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-16T15:26:33.194Z · raw response hash: sha256:864af12b4d99bde29de9a6003b395c189ed8757b2795d2f43f6a054a172a4f45

Neutral Nostr anchor

Event ID

6bd1d5e4d96a70a49ea0d57672e670e0f90a286f28e21ecd8eccc1ef19f3206a

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-16T15:26:33.248Z","evidence_byte_length":98,"evidence_sha256":"sha256:864af12b4d99bde29de9a6003b395c189ed8757b2795d2f43f6a054a172a4f45","evidence_url":"https://zambo.dev/api/evidence/864af12b4d99bde29de9a6003b395c189ed8757b2795d2f43f6a054a172a4f45","output_sha256":"sha256:f5b384726645ebdaa236ea43877c62b57c6f771cf7f46b352f0e44286a08aee9","receipt_uuid":"7bb64982-2d3a-4c2a-bb15-8af7b2198e05","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

API v2 status: verified. 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.