Verifiable receipt fcd51425 - 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,692.00 USD\n▼ 1.97% (24h) · Market cap: $1642.15B\n\nLive price via CoinGecko · Thu, 08 Oct 2026 21:07:47 GMT","verify":{"status":"complete","message":"BTC-USD price and source were returned by the live price provider."}}

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

Committed provenance claim

EXECUTED BY ZAMBO

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

Receipt ID
fcd51425-0e00-401b-bf92-6e5790808251
SHA-256 output hash
sha256:f36187e993fcbac362061bd2cfde9dc125d6e19fc2f4141449a7e711182cb6ae
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MTg4NzgwYmEwY2I4OGNjNTU3YTIzN2U3NjkzNzA3ODVjOWQ0NTE3MThjYTBlMThmMzA2Yjg4NThjN2M5NDU3ZSIsInR5cGUiOiJhbm9ueW1vdXMifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7ImV4ZWN1dGVkIjp0cnVlLCJleGVjdXRlZF90b29scyI6WyJsaXZlX3ByaWNlIl0sInByaW1hcnlfdG9vbCI6ImxpdmVfcHJpY2UiLCJyZXN1bHQiOiJCVEMgwrcgJDgxLDY5Mi4wMCBVU0RcbuKWvCAxLjk3JSAoMjRoKSDCtyBNYXJrZXQgY2FwOiAkMTY0Mi4xNUJcblxuTGl2ZSBwcmljZSB2aWEgQ29pbkdlY2tvIMK3IFRodSwgMDggT2N0IDIwMjYgMjE6MDc6NDcgR01UIiwic3RhdHVzIjoiZXhlY3V0ZWQiLCJ2ZXJpZnkiOnsibWVzc2FnZSI6IkJUQy1VU0QgcHJpY2UgYW5kIHNvdXJjZSB3ZXJlIHJldHVybmVkIGJ5IHRoZSBsaXZlIHByaWNlIHByb3ZpZGVyLiIsInN0YXR1cyI6ImNvbXBsZXRlIn19LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiemFtYm9fdW5pdmVyc2FsIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
Timestamp

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:188780ba0cb88cc557a237e769370785c9d451718ca0e18f306b8858c7c9457e
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:06c54e4a4d3962377daeaa20e731e87768ae117434a95f9fb36b0b2c0b3c8154
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.

Neutral Nostr anchor

Event ID
22bb80eea9a1d508b2218a595728a7c7501d398a433c36a1fbbf9c7564912158
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-08T21:07:47.397Z","evidence_byte_length":98,"evidence_sha256":"sha256:06c54e4a4d3962377daeaa20e731e87768ae117434a95f9fb36b0b2c0b3c8154","evidence_url":"https://zambo.dev/api/evidence/06c54e4a4d3962377daeaa20e731e87768ae117434a95f9fb36b0b2c0b3c8154","output_sha256":"sha256:f36187e993fcbac362061bd2cfde9dc125d6e19fc2f4141449a7e711182cb6ae","receipt_uuid":"fcd51425-0e00-401b-bf92-6e5790808251","schema_version":"zambo-receipt-anchor/1"}

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

Check this hash yourself

Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. Signature and chain remain NOT CHECKED unless a real signature verifier or chain proof is supplied. There is no combined “verified” verdict. 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/fcd51425-0e00-401b-bf92-6e5790808251/badge.svg)](https://zambo.dev/run/fcd51425-0e00-401b-bf92-6e5790808251)

HTML

<a href="https://zambo.dev/run/fcd51425-0e00-401b-bf92-6e5790808251"><img src="https://zambo.dev/api/receipt/fcd51425-0e00-401b-bf92-6e5790808251/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

40,706 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