Verifiable receipt 0bef8a5e - zambo_universal result | Zambo

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

Saved:
What was asked: The request recorded for this receipt.

Zambo is the verifiable work layer for AI.

Zambo is the verifiable work layer for AI. Verifiable receipt for a zambo_universal call on Zambo: {"source_receipt_id":"206142b9-4f05-4536-b6e1-6047ee451a03","source_output_hash":"sha256:1c2dfee63157208

Observed result

source receipt id: 206142b9-4f05-4536-b6e1-6047ee451a03 source output hash: sha256:1c2dfee6315720827a88d78dd01f9d03174ee52918a014cee7fd3fc30d369276 output: {"status":"executed","primary_tool":"live_price","executed":true,"executed_tools":["live_price"],"result":"ETH · $2,441.63 USD\n▲ 0.18% (24h) · Market cap: $298.17B\n\nLive price via CoinGecko · Fri, 16 Oct 2026 15:50:43 GMT","verify":{"status":"complete","message":"ETH-USD price and source were returned by the live price provider."}} 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 ·

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-10-16T15:50:48.800Z; 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
0bef8a5e-b34a-422d-8f54-f26f492e1507
SHA-256 output hash
sha256:c9e8110d66f7e33050d9c13b181a036321831f3092dffe411ad37f10eea4f0c3
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MmZjZDM0MmNmZmRhNTcxMjAxMDI2MDA2ZDA1Mjg5ZGRmNjA4Njg3ZDZjZTgzYWY4YzM5NmVkN2VlOTViNDIxMSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJleGVjdXRlZFwiLFwicHJpbWFyeV90b29sXCI6XCJsaXZlX3ByaWNlXCIsXCJleGVjdXRlZFwiOnRydWUsXCJleGVjdXRlZF90b29sc1wiOltcImxpdmVfcHJpY2VcIl0sXCJyZXN1bHRcIjpcIkVUSCDCtyAkMiw0NDEuNjMgVVNEXFxu4payIDAuMTglICgyNGgpIMK3IE1hcmtldCBjYXA6ICQyOTguMTdCXFxuXFxuTGl2ZSBwcmljZSB2aWEgQ29pbkdlY2tvIMK3IEZyaSwgMTYgT2N0IDIwMjYgMTU6NTA6NDMgR01UXCIsXCJ2ZXJpZnlcIjp7XCJzdGF0dXNcIjpcImNvbXBsZXRlXCIsXCJtZXNzYWdlXCI6XCJFVEgtVVNEIHByaWNlIGFuZCBzb3VyY2Ugd2VyZSByZXR1cm5lZCBieSB0aGUgbGl2ZSBwcmljZSBwcm92aWRlci5cIn19IiwicmVkYWN0ZWRfcHJvamVjdGlvbiI6dHJ1ZSwic291cmNlX2NvbW1pdG1lbnRfY2hlY2tlZCI6dHJ1ZSwic291cmNlX291dHB1dF9oYXNoIjoic2hhMjU2OjFjMmRmZWU2MzE1NzIwODI3YTg4ZDc4ZGQwMWY5ZDAzMTc0ZWU1MjkxOGEwMTRjZWU3ZmQzZmMzMGQzNjkyNzYiLCJzb3VyY2VfcmVjZWlwdF9pZCI6IjIwNjE0MmI5LTRmMDUtNDUzNi1iNmUxLTYwNDdlZTQ1MWEwMyJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiemFtYm9fdW5pdmVyc2FsIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:2fcd342cffda571201026006d05289ddf608687d6ce83af8c396ed7ee95b4211
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
no_upstream_bytes_captured
Evidence SHA-256
unavailable
Byte length
unavailable

Neutral Nostr anchor

Event ID
0b4387782d66fc1e35de9d62d27153a06bef3d07346b62426f1dd3962e20adb5
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-16T15:50:48.800Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:c9e8110d66f7e33050d9c13b181a036321831f3092dffe411ad37f10eea4f0c3","receipt_uuid":"0bef8a5e-b34a-422d-8f54-f26f492e1507","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/0bef8a5e-b34a-422d-8f54-f26f492e1507/badge.svg)](https://zambo.dev/run/0bef8a5e-b34a-422d-8f54-f26f492e1507?ref=badge)

HTML

<a href="https://zambo.dev/run/0bef8a5e-b34a-422d-8f54-f26f492e1507?ref=badge"><img src="https://zambo.dev/api/receipt/0bef8a5e-b34a-422d-8f54-f26f492e1507/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

48,447 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