Verifiable receipt e3c1352c - zambo_universal result | Zambo

Verifiable receipt for a zambo_universal call on Zambo: {"status":"executed","primary_tool":"live_price","executed":true,"executed_tools":["live_price"],"result

Observed result

{"status":"executed","primary_tool":"live_price","executed":true,"executed_tools":["live_price"],"result":"ETH · $2,492.77 USD\n▼ 0.14% (24h) · Market cap: $304.49B\n\nLive price via Coinbase · Sat, 10 Oct 2026 11:35:31 GMT","verify":{"status":"complete","message":"ETH-USD price and source were returned by the live price provider."}}

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.

UNLOCK 24H DAY PASS ($0.99) →

See all plans on the pricing page →

RUN YOUR OWN FREE CALL →

Or re-run this exact call, using the same tool and arguments.

Share on X ·

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-10T11:35:31.827Z; external immutability is not checked

Want a verifiable receipt for every job your bots do?

Add Zambo Receipt Bot to your team · File this in Receipt Bot

Committed provenance claim

EXECUTED BY ZAMBO

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

Receipt ID: e3c1352c-0e38-4c6b-b1dd-dac566b1795c
SHA-256 output hash: sha256:0e619b48552fbfaefb59c5c8f3fc91b43514ec13ffe9f1b88cb5ffce20132c1c
Canonical bytes: eyJjYWxsZXIiOnsiYmFzaXMiOiJpcF91YV8zMGQiLCJpZCI6InNoYTI1NjoxNjkzMTg5OTU2MzRiZTBjOTE1MDlhZDBjZTAzNWUzNjFlZTc0MDQzYWU2NDY1ZjI5NDc4MGE3Y2MwNDY3YWRiIiwibGFiZWwiOiJzd2VlcC0xMDEwIiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwicm90YXRlc19hdCI6IjIwMjYtMTEtMDNUMDA6MDA6MDAuMDAwWiIsInR5cGUiOiJhbm9ueW1vdXMifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7ImV4ZWN1dGVkIjp0cnVlLCJleGVjdXRlZF90b29scyI6WyJsaXZlX3ByaWNlIl0sInByaW1hcnlfdG9vbCI6ImxpdmVfcHJpY2UiLCJyZXN1bHQiOiJFVEggwrcgJDIsNDkyLjc3IFVTRFxu4pa8IDAuMTQlICgyNGgpIMK3IE1hcmtldCBjYXA6ICQzMDQuNDlCXG5cbkxpdmUgcHJpY2UgdmlhIENvaW5iYXNlIMK3IFNhdCwgMTAgT2N0IDIwMjYgMTE6MzU6MzEgR01UIiwic3RhdHVzIjoiZXhlY3V0ZWQiLCJ2ZXJpZnkiOnsibWVzc2FnZSI6IkVUSC1VU0QgcHJpY2UgYW5kIHNvdXJjZSB3ZXJlIHJldHVybmVkIGJ5IHRoZSBsaXZlIHByaWNlIHByb3ZpZGVyLiIsInN0YXR1cyI6ImNvbXBsZXRlIn19LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiemFtYm9fdW5pdmVyc2FsIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
Timestamp: 2026-10-10T11:35:31.827Z

Bound call context

Receipt schema: 0.4
Tool name: zambo_universal
Tool version: 4.0.0
Permission scope: public
Caller type: anonymous
Caller ID: sha256:169318995634be0c91509ad0ce035e361ee74043ae6465f294780a7cc0467adb
Caller basis: ip_ua_30d
Caller rotates at: 2026-11-03T00:00:00.000Z
Caller-reported label: sweep-1010 (caller_reported, not authenticated team ownership)
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:6529e19eb4c125e9bf94e997ea53c292ea8f4d6d0a8f8c25fb400947c088da2e
Byte length: 187

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-10T11:35:31.747Z · raw response hash: sha256:6529e19eb4c125e9bf94e997ea53c292ea8f4d6d0a8f8c25fb400947c088da2e
Source: Coinbase · queried at: 2026-10-10T11:35:31.776Z · raw response hash: sha256:b789090c9bfb50fb607107b15071dfd1cf7ab847667763e5ed7559d10b3c75f6

Maximum comparable-source deviation: not comparable

Neutral Nostr anchor

Event ID: 1af1188099498b7ff20119dd2c47d6742aaee86db19941d76ddb49d8d58c3788
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-10T11:35:31.827Z","evidence_byte_length":187,"evidence_sha256":"sha256:6529e19eb4c125e9bf94e997ea53c292ea8f4d6d0a8f8c25fb400947c088da2e","evidence_url":"https://zambo.dev/api/evidence/6529e19eb4c125e9bf94e997ea53c292ea8f4d6d0a8f8c25fb400947c088da2e","output_sha256":"sha256:0e619b48552fbfaefb59c5c8f3fc91b43514ec13ffe9f1b88cb5ffce20132c1c","receipt_uuid":"e3c1352c-0e38-4c6b-b1dd-dac566b1795c","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.

Embed this receipt

Markdown

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/e3c1352c-0e38-4c6b-b1dd-dac566b1795c/badge.svg)](https://zambo.dev/run/e3c1352c-0e38-4c6b-b1dd-dac566b1795c)

HTML

<a href="https://zambo.dev/run/e3c1352c-0e38-4c6b-b1dd-dac566b1795c"><img src="https://zambo.dev/api/receipt/e3c1352c-0e38-4c6b-b1dd-dac566b1795c/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG