Verifiable receipt ec580cca - 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":"31e5a078-e183-4ce2-8e47-702799e98387","source_output_hash":"sha256:7687be0a6231b99

Observed result

source receipt id: 31e5a078-e183-4ce2-8e47-702799e98387 source output hash: sha256:7687be0a6231b997938bb0f46aad83143ec42ffbcd7ce2b1d0c48bb17a142083 output: {"status":"executed","primary_tool":"live_price","executed":true,"executed_tools":["live_price"],"result":"BTC · $81,584.00 USD\n▼ 0.88% (24h) · Market cap: $1639.88B\n\nLive price via CoinGecko · Fri, 16 Oct 2026 15:50:40 GMT","verify":{"status":"complete","message":"BTC-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.578Z; 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
ec580cca-966b-4a7e-8a80-3b5d6228c9a3
SHA-256 output hash
sha256:b37df2b4919c8cb6f0c52c49d734b5a20a68bacd3be7f98188319289e2421e90
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MmZjZDM0MmNmZmRhNTcxMjAxMDI2MDA2ZDA1Mjg5ZGRmNjA4Njg3ZDZjZTgzYWY4YzM5NmVkN2VlOTViNDIxMSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJleGVjdXRlZFwiLFwicHJpbWFyeV90b29sXCI6XCJsaXZlX3ByaWNlXCIsXCJleGVjdXRlZFwiOnRydWUsXCJleGVjdXRlZF90b29sc1wiOltcImxpdmVfcHJpY2VcIl0sXCJyZXN1bHRcIjpcIkJUQyDCtyAkODEsNTg0LjAwIFVTRFxcbuKWvCAwLjg4JSAoMjRoKSDCtyBNYXJrZXQgY2FwOiAkMTYzOS44OEJcXG5cXG5MaXZlIHByaWNlIHZpYSBDb2luR2Vja28gwrcgRnJpLCAxNiBPY3QgMjAyNiAxNTo1MDo0MCBHTVRcIixcInZlcmlmeVwiOntcInN0YXR1c1wiOlwiY29tcGxldGVcIixcIm1lc3NhZ2VcIjpcIkJUQy1VU0QgcHJpY2UgYW5kIHNvdXJjZSB3ZXJlIHJldHVybmVkIGJ5IHRoZSBsaXZlIHByaWNlIHByb3ZpZGVyLlwifX0iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzb3VyY2VfY29tbWl0bWVudF9jaGVja2VkIjp0cnVlLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6NzY4N2JlMGE2MjMxYjk5NzkzOGJiMGY0NmFhZDgzMTQzZWM0MmZmYmNkN2NlMmIxZDBjNDhiYjE3YTE0MjA4MyIsInNvdXJjZV9yZWNlaXB0X2lkIjoiMzFlNWEwNzgtZTE4My00Y2UyLThlNDctNzAyNzk5ZTk4Mzg3In0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ6YW1ib191bml2ZXJzYWwiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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
09150737b6870b76539c40bb253b5cca16c5f512e05cedfab148fa78cbc61ee7
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.578Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:b37df2b4919c8cb6f0c52c49d734b5a20a68bacd3be7f98188319289e2421e90","receipt_uuid":"ec580cca-966b-4a7e-8a80-3b5d6228c9a3","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/ec580cca-966b-4a7e-8a80-3b5d6228c9a3/badge.svg)](https://zambo.dev/run/ec580cca-966b-4a7e-8a80-3b5d6228c9a3?ref=badge)

HTML

<a href="https://zambo.dev/run/ec580cca-966b-4a7e-8a80-3b5d6228c9a3?ref=badge"><img src="https://zambo.dev/api/receipt/ec580cca-966b-4a7e-8a80-3b5d6228c9a3/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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