Verifiable receipt 5d8ee089 - 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":"BTC · $81,600.00 USD\n▼ 2.15% (24h) · Market cap: $1639.63B\n\nLive price via CoinGecko · Wed, 14 Oct 2026 16:16:07 GMT","verify":{"status":"complete","message":"BTC-USD price and source were returned by the live price provider."}}

This is the saved result preview, not proof that the answer was correct.

Check this receipt Run your own

Provenance for every timeline entry

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 this receipt

Share on X ·

Verification checks

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
5d8ee089-1a2d-4217-8b98-8fdced50c3db
SHA-256 output hash
sha256:a56d7055bfc76ff0a405af6ad38e8a16ff3b91d2431a5447edef6c17001c6fe3
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6Y2Y3M2I5YzFjYTBlZTY1NjZkZGU3MmUwNmQzYTRhNzQzYzM3ODA1YWJmOGFjOTBiYWUzNTNkYWJkNTcyOTE4MyIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJleGVjdXRlZCI6dHJ1ZSwiZXhlY3V0ZWRfdG9vbHMiOlsibGl2ZV9wcmljZSJdLCJwcmltYXJ5X3Rvb2wiOiJsaXZlX3ByaWNlIiwicmVzdWx0IjoiQlRDIMK3ICQ4MSw2MDAuMDAgVVNEXG7ilrwgMi4xNSUgKDI0aCkgwrcgTWFya2V0IGNhcDogJDE2MzkuNjNCXG5cbkxpdmUgcHJpY2UgdmlhIENvaW5HZWNrbyDCtyBXZWQsIDE0IE9jdCAyMDI2IDE2OjE2OjA3IEdNVCIsInN0YXR1cyI6ImV4ZWN1dGVkIiwidmVyaWZ5Ijp7Im1lc3NhZ2UiOiJCVEMtVVNEIHByaWNlIGFuZCBzb3VyY2Ugd2VyZSByZXR1cm5lZCBieSB0aGUgbGl2ZSBwcmljZSBwcm92aWRlci4iLCJzdGF0dXMiOiJjb21wbGV0ZSJ9fSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6InphbWJvX3VuaXZlcnNhbCIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
Timestamp

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:cf73b9c1ca0ee6566dde72e06d3a4a743c37805abf8ac90bae353dabd5729183
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:9da09d4cd8768a450949984339525b58cd821126deb224e22a400b5ead3aa445
Byte length
97

Fetch exact evidence bytes

Upstream provenance

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

Neutral Nostr anchor

Event ID
ea173787a0cecef1869cde0a0256a04c7948331958b464536e85988d26252496
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-14T16:16:07.108Z","evidence_byte_length":97,"evidence_sha256":"sha256:9da09d4cd8768a450949984339525b58cd821126deb224e22a400b5ead3aa445","evidence_url":"https://zambo.dev/api/evidence/9da09d4cd8768a450949984339525b58cd821126deb224e22a400b5ead3aa445","output_sha256":"sha256:a56d7055bfc76ff0a405af6ad38e8a16ff3b91d2431a5447edef6c17001c6fe3","receipt_uuid":"5d8ee089-1a2d-4217-8b98-8fdced50c3db","schema_version":"zambo-receipt-anchor/1"}

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

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/5d8ee089-1a2d-4217-8b98-8fdced50c3db/badge.svg)](https://zambo.dev/run/5d8ee089-1a2d-4217-8b98-8fdced50c3db?ref=badge)

HTML

<a href="https://zambo.dev/run/5d8ee089-1a2d-4217-8b98-8fdced50c3db?ref=badge"><img src="https://zambo.dev/api/receipt/5d8ee089-1a2d-4217-8b98-8fdced50c3db/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

43,239 verifiable receipts minted

RUN YOUR OWN FREE CALL →

Run your own calls. Free, 20 free calls per metered tool each day, no account.

Open the interactive receipt view