Verifiable receipt 2b9a1121 - 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":"e6ae37e8-a263-434b-a17c-718bb9b720af","source_output_hash":"sha256:03b24c39db6b650

Observed result

source receipt id: e6ae37e8-a263-434b-a17c-718bb9b720af source output hash: sha256:03b24c39db6b650852591baf0b64d006b2bfc53b22178d85a8d2f2431698cbd1 output: {"status":"executed","primary_tool":"live_price","executed":true,"executed_tools":["live_price"],"result":"SOL · $106.17 USD\n▲ 0.00% (24h) · Market cap: unavailable\n\nLive price via Coinbase · Fri, 16 Oct 2026 14:31:06 GMT","verify":{"status":"complete","message":"SOL-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-16T14:31:13.143Z; 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
2b9a1121-dfff-4816-a49f-df4caafd234e
SHA-256 output hash
sha256:58cf0c7084940b4f1fdd10ce537dbc3f84dd5b0f47d4d8e1c8b02672103005c7
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZDg1MTdmZjBjYzIwMmQxM2ZmMWY0NDcxNzMzNDQ0NjQyOGY0ZGQ1ODI1MzA5YjZmOTc2MWUwZDBlMDYyZmI5OCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJleGVjdXRlZFwiLFwicHJpbWFyeV90b29sXCI6XCJsaXZlX3ByaWNlXCIsXCJleGVjdXRlZFwiOnRydWUsXCJleGVjdXRlZF90b29sc1wiOltcImxpdmVfcHJpY2VcIl0sXCJyZXN1bHRcIjpcIlNPTCDCtyAkMTA2LjE3IFVTRFxcbuKWsiAwLjAwJSAoMjRoKSDCtyBNYXJrZXQgY2FwOiB1bmF2YWlsYWJsZVxcblxcbkxpdmUgcHJpY2UgdmlhIENvaW5iYXNlIMK3IEZyaSwgMTYgT2N0IDIwMjYgMTQ6MzE6MDYgR01UXCIsXCJ2ZXJpZnlcIjp7XCJzdGF0dXNcIjpcImNvbXBsZXRlXCIsXCJtZXNzYWdlXCI6XCJTT0wtVVNEIHByaWNlIGFuZCBzb3VyY2Ugd2VyZSByZXR1cm5lZCBieSB0aGUgbGl2ZSBwcmljZSBwcm92aWRlci5cIn19IiwicmVkYWN0ZWRfcHJvamVjdGlvbiI6dHJ1ZSwic291cmNlX2NvbW1pdG1lbnRfY2hlY2tlZCI6dHJ1ZSwic291cmNlX291dHB1dF9oYXNoIjoic2hhMjU2OjAzYjI0YzM5ZGI2YjY1MDg1MjU5MWJhZjBiNjRkMDA2YjJiZmM1M2IyMjE3OGQ4NWE4ZDJmMjQzMTY5OGNiZDEiLCJzb3VyY2VfcmVjZWlwdF9pZCI6ImU2YWUzN2U4LWEyNjMtNDM0Yi1hMTdjLTcxOGJiOWI3MjBhZiJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiemFtYm9fdW5pdmVyc2FsIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
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:d8517ff0cc202d13ff1f44717334446428f4dd5825309b6f9761e0d0e062fb98
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
226fee6ea8bec052b32cbd06a699101e0ea38e6dd2553e0cfffe02afe1756daa
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-16T14:31:13.143Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:58cf0c7084940b4f1fdd10ce537dbc3f84dd5b0f47d4d8e1c8b02672103005c7","receipt_uuid":"2b9a1121-dfff-4816-a49f-df4caafd234e","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/2b9a1121-dfff-4816-a49f-df4caafd234e/badge.svg)](https://zambo.dev/run/2b9a1121-dfff-4816-a49f-df4caafd234e?ref=badge)

HTML

<a href="https://zambo.dev/run/2b9a1121-dfff-4816-a49f-df4caafd234e?ref=badge"><img src="https://zambo.dev/api/receipt/2b9a1121-dfff-4816-a49f-df4caafd234e/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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