Public work receipt · checkable record

ETH price, saved and checkable

✓ This result hasn’t changed since it was saved.

Sent by taifoon-coordination using Zambo

Saved:
What ran: live_price
Job summary: symbol: ETH

Zambo is the verifiable work layer for AI.

Observed result

ETH · $1,648.94 USD ▼ 5.61% (24h) · Market cap: $202.10B Live price snapshot via Coinbase · fetched Sat, 21 Nov 2026 11:57:17 GMT · cache age 3s

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

Verify saved bytes Run your own
Show technical provenance details

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 the receipt can and cannot prove

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.

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 · Share on LinkedIn ·

Show technical verification checks

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-11-21T11:57:20.690Z; external immutability is not checked

Get proof like this from your own AI

Add to my AI ·

Get receipts for your own AI work: add zambo.dev/mcp

One URL, no key. Copy the line for your AI and add it yourself in its settings.

  • ClaudeSettings, Connectors, Add custom connector, paste the URL.
    https://zambo.dev/mcp
  • ChatGPTSettings, Apps and Connectors, developer mode, create a connector with this URL.
    https://zambo.dev/mcp
  • GrokAdd a remote MCP server in your Grok client and paste the URL.
    https://zambo.dev/mcp
  • CursorPaste into ~/.cursor/mcp.json.
    {"mcpServers":{"zambo":{"url":"https://zambo.dev/mcp"}}}

Nothing is installed automatically. Full setup guides

Want a verifiable receipt for every job your bots do?

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

Show receipt data and verification evidence

Committed provenance claim

EXECUTED BY ZAMBO

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

Receipt ID
0c7b93a8-a2ce-4dee-8904-ce75c5143528
SHA-256 output hash
sha256:7fd5be2c35081be71fdf2616dbc4d6d29d70ff16f0f6609c5b58c106140861cb
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZDA1NjI4ZTVlZTU5ZTZkZDg5NjMzZWVlNDI2M2M3MjA2OTFiMDJjMTFkYzE5MjU0NzJhYTdkOTZkMDUwZGMzYiIsImxhYmVsIjoidGFpZm9vbi1jb29yZGluYXRpb24iLCJsYWJlbF9zb3VyY2UiOiJjYWxsZXJfcmVwb3J0ZWQiLCJ0eXBlIjoic2Vzc2lvbiJ9LCJpc3N1ZXJfY2xhaW1zIjp7InByb3ZlbmFuY2VfY2xhc3MiOiJFWEVDVVRFRCBCWSBaQU1CTyJ9LCJvdXRwdXQiOnsidGV4dCI6IkVUSCDCtyAkMSw2NDguOTQgVVNEXG7ilrwgNS42MSUgKDI0aCkgwrcgTWFya2V0IGNhcDogJDIwMi4xMEJcblxuTGl2ZSBwcmljZSBzbmFwc2hvdCB2aWEgQ29pbmJhc2UgwrcgZmV0Y2hlZCBTYXQsIDIxIE5vdiAyMDI2IDExOjU3OjE3IEdNVCDCtyBjYWNoZSBhZ2UgM3MifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoibGl2ZV9wcmljZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS40In19
Timestamp

Bound call context

Receipt schema
0.4
Tool name
live_price
Tool version
4.1.4
Permission scope
public
Caller type
session
Caller ID
sha256:d05628e5ee59e6dd89633eee4263c720691b02c11dc1925472aa7d96d050dc3b
Caller-reported label
taifoon-coordination (caller_reported, not authenticated team ownership)
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
ok
Evidence SHA-256
sha256:5fbea2184572abc98fd29333696757e1bbe53a7df447f12f8f71c1842b7f3abf
Byte length
59

Fetch exact evidence bytes

Upstream provenance

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

  • Source: Coinbase · queried at: · raw response hash: sha256:5fbea2184572abc98fd29333696757e1bbe53a7df447f12f8f71c1842b7f3abf

Neutral Nostr anchor

Event ID
1455bbdbb160224c02c5780f1a35c87a171741bde55d3c6d3b043cbc3abd2e2f
Anchor status
published
Public key
e13475107d30c918ec664adf2ab•••••24a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-21T11:57:20.690Z","evidence_byte_length":59,"evidence_sha256":"sha256:5fbea•••••72abc98fd29333696757e1bbe53a7df447f12f8f71c1842b7f3abf","evidence_url":"https://zambo.dev/api/evidence/5fbea•••••72abc98fd29333696757e1bbe53a7df447f12f8f71c1842b7f3abf","output_sha256":"sha256:7fd5be2c35081be71fdf2616dbc4d6d29d70ff16f0f6609c5b58c106140861cb","receipt_uuid":"0c7b93a8-a2ce-4dee-8904-ce75c•••••28","schema_version":"zambo-receipt-anchor/1"}

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

Relay publication is separate from receipt integrity. When the original signed event is available, Zambo retries pending, partial, or failed anchors about once a minute. Relay acknowledgements are external, so there is no guaranteed completion time; the receipt remains checkable from its saved bytes and verification link.

Check this hash yourself

Receipt commitment: commitment matched; issuer, signature and chain not checked. This checks the saved bytes, not whether the answer was correct. Open the browser receipt checker. 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/0c7b93a8-a2ce-4dee-8904-ce75c5143528/badge.svg)](https://zambo.dev/run/0c7b93a8-a2ce-4dee-8904-ce75c5143528?ref=badge)

HTML

<a href="https://zambo.dev/run/0c7b93a8-a2ce-4dee-8904-ce75c5143528?ref=badge"><img src="https://zambo.dev/api/receipt/0c7b93a8-a2ce-4dee-8904-ce75c5143528/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

156,378 verifiable receipts minted

RUN YOUR OWN FREE CALL →

Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.

Open the interactive receipt view

Your AI's work could look like this

Run a first job free in Zambo Chat. No account needed.