Public work receipt · checkable record

CRYPTO price, saved and checkable

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

Sent using Zambo

Saved:
What ran: live_price

Zambo is the verifiable work layer for AI.

Observed result

source receipt id: 30ea8f84-7dbb-445d-b9ac-47b8b7bfd505 source output hash: sha256:bd4b79452e740ab2bd1aaa2152bd76cdbe7ca2829da21c9fc213b4c0fc6c9aaf output: ETH · $1,768.49 USD ▼ 8.22% (24h) · Market cap: $212.71B Live price snapshot via Coinbase · fetched Sun, 15 Nov 2026 00:00:09 GMT · cache age 0s redacted projection: true source commitment checked: true

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

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

This is a verifiable receipt for a journal entry. It confirms receipt, redaction, timestamping, and chaining. It does not attest to execution.

What the receipt can and cannot prove

What is this?

Zambo's receipt store reports a journal entry from an agent or local hook. The SHA-256 commitment covers the receipt bytes. The provenance label is only a claim, not proof of issuer identity or that the reported action happened.

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-15T00:00:12.118Z; 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

LOGGED BY AGENT

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

Receipt ID
7a9bd2bd-814d-406c-8911-508c77fbb6d0
SHA-256 output hash
sha256:41cf54434692b15a5301771127d4f20d6f0e5a7d53b758632780c98a340bbfdf
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZGVjZDA1MTAwYzNlZjFmNDI0ZGE2MDUyYzFmOTI3MzNmMjA4NWZkYjNiYWNlMTBlZTU3NzkzMTExOTdlOTIxNSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0IjoiRVRIIMK3ICQxLDc2OC40OSBVU0RcbuKWvCA4LjIyJSAoMjRoKSDCtyBNYXJrZXQgY2FwOiAkMjEyLjcxQlxuXG5MaXZlIHByaWNlIHNuYXBzaG90IHZpYSBDb2luYmFzZSDCtyBmZXRjaGVkIFN1biwgMTUgTm92IDIwMjYgMDA6MDA6MDkgR01UIMK3IGNhY2hlIGFnZSAwcyIsInJlZGFjdGVkX3Byb2plY3Rpb24iOnRydWUsInNvdXJjZV9jb21taXRtZW50X2NoZWNrZWQiOnRydWUsInNvdXJjZV9vdXRwdXRfaGFzaCI6InNoYTI1NjpiZDRiNzk0NTJlNzQwYWIyYmQxYWFhMjE1MmJkNzZjZGJlN2NhMjgyOWRhMjFjOWZjMjEzYjRjMGZjNmM5YWFmIiwic291cmNlX3JlY2VpcHRfaWQiOiIzMGVhOGY4NC03ZGJiLTQ0NWQtYjlhYy00N2I4YjdiZmQ1MDUifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoibGl2ZV9wcmljZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS40In19
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:decd05100c3ef1f424da6052c1f92733f2085fdb3bace10ee5779311197e9215
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
empty
Evidence SHA-256
unavailable
Byte length
unavailable

Neutral Nostr anchor

Event ID
baf01ad38e4578874f71a0f68df5f46ab3943b0c4e5d82f5e04b567fd5c978d7
Anchor status
published
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-15T00:00:12.118Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:41cf54434692b15a5301771127d4f20d6f0e5a7d53b758632780c98a340bbfdf","receipt_uuid":"7a9bd2bd-814d-406c-8911-508c77fbb6d0","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. 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/7a9bd2bd-814d-406c-8911-508c77fbb6d0/badge.svg)](https://zambo.dev/run/7a9bd2bd-814d-406c-8911-508c77fbb6d0?ref=badge)

HTML

<a href="https://zambo.dev/run/7a9bd2bd-814d-406c-8911-508c77fbb6d0?ref=badge"><img src="https://zambo.dev/api/receipt/7a9bd2bd-814d-406c-8911-508c77fbb6d0/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

143,613 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.