Public work receipt · checkable record

A note in your job log · saved and checkable

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

Sent using Zambo

Saved:
What ran: journal_log

Zambo is the verifiable work layer for AI.

Observed result

source receipt id: b2fd0ab4-1800-4eb3-b3b6-5e11611c08cf source output hash: sha256:4dc74faec10924ebee6ea241df13cda61f230860953cbeb6bf784f09cfefeb32 output: {"status":"logged","provenance_class":"LOGGED BY AGENT","entry":{"entry_id":"8029a50a-cafc-4aa0-84da-92259646e0db","sequence":1,"provenance_class":"LOGGED BY AGENT","tool_name":"job opened: conversion-lane live chain. step 1 source: live_price BTC fetched by agent A (receipts 4e480be9, 83b92990).","redacted_inputs_hash":null,"started_at":"2026-11-08T00:22:08.444Z","completed_at":"2026-11-08T00:22:08.444Z","duration_ms":0,"executor_identity":"conv-lane-agent-a","external_executor":null,"metadata":{},"prev_hash":null,"entry_hash":"sha256:147b3b7fd4ef6690e8ee28b74af33ca8f11f719ec52aca501d82251ab512490c","deleted":false},"attests":"Zambo attests that this record was received, redacted, timestamped, and chained.","does_not_attest":"Zambo did not run or observe the reported action.","verify_url":"https://zambo.dev/api/journal/[private]/verify"} 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-08T00:22:23.469Z; 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
27c69f3d-84f7-487f-b713-559095d96b0e
SHA-256 output hash
sha256:29f684b182b223a4deb593da564fc56ded3f0e1fae746ee2c6cf629fe1889f49
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MDI4MjhhZGVhNGNlYjVlMjYxNDMwMjU4NWViMDVjOWQxNzI1YTMwOTNiNDFkZjk3M2JlZTJhZjM5Y2MyZjc5MCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJsb2dnZWRcIixcInByb3ZlbmFuY2VfY2xhc3NcIjpcIkxPR0dFRCBCWSBBR0VOVFwiLFwiZW50cnlcIjp7XCJlbnRyeV9pZFwiOlwiODAyOWE1MGEtY2FmYy00YWEwLTg0ZGEtOTIyNTk2NDZlMGRiXCIsXCJzZXF1ZW5jZVwiOjEsXCJwcm92ZW5hbmNlX2NsYXNzXCI6XCJMT0dHRUQgQlkgQUdFTlRcIixcInRvb2xfbmFtZVwiOlwiam9iIG9wZW5lZDogY29udmVyc2lvbi1sYW5lIGxpdmUgY2hhaW4uIHN0ZXAgMSBzb3VyY2U6IGxpdmVfcHJpY2UgQlRDIGZldGNoZWQgYnkgYWdlbnQgQSAocmVjZWlwdHMgNGU0ODBiZTksIDgzYjkyOTkwKS5cIixcInJlZGFjdGVkX2lucHV0c19oYXNoXCI6bnVsbCxcInN0YXJ0ZWRfYXRcIjpcIjIwMjYtMTEtMDhUMDA6MjI6MDguNDQ0WlwiLFwiY29tcGxldGVkX2F0XCI6XCIyMDI2LTExLTA4VDAwOjIyOjA4LjQ0NFpcIixcImR1cmF0aW9uX21zXCI6MCxcImV4ZWN1dG9yX2lkZW50aXR5XCI6XCJjb252LWxhbmUtYWdlbnQtYVwiLFwiZXh0ZXJuYWxfZXhlY3V0b3JcIjpudWxsLFwibWV0YWRhdGFcIjp7fSxcInByZXZfaGFzaFwiOm51bGwsXCJlbnRyeV9oYXNoXCI6XCJzaGEyNTY6MTQ3YjNiN2ZkNGVmNjY5MGU4ZWUyOGI3NGFmMzNjYThmMTFmNzE5ZWM1MmFjYTUwMWQ4MjI1MWFiNTEyNDkwY1wiLFwiZGVsZXRlZFwiOmZhbHNlfSxcImF0dGVzdHNcIjpcIlphbWJvIGF0dGVzdHMgdGhhdCB0aGlzIHJlY29yZCB3YXMgcmVjZWl2ZWQsIHJlZGFjdGVkLCB0aW1lc3RhbXBlZCwgYW5kIGNoYWluZWQuXCIsXCJkb2VzX25vdF9hdHRlc3RcIjpcIlphbWJvIGRpZCBub3QgcnVuIG9yIG9ic2VydmUgdGhlIHJlcG9ydGVkIGFjdGlvbi5cIixcInZlcmlmeV91cmxcIjpcImh0dHBzOi8vemFtYm8uZGV2L2FwaS9qb3VybmFsL1twcml2YXRlXS92ZXJpZnlcIn0iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzb3VyY2VfY29tbWl0bWVudF9jaGVja2VkIjp0cnVlLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6NGRjNzRmYWVjMTA5MjRlYmVlNmVhMjQxZGYxM2NkYTYxZjIzMDg2MDk1M2NiZWI2YmY3ODRmMDljZmVmZWIzMiIsInNvdXJjZV9yZWNlaXB0X2lkIjoiYjJmZDBhYjQtMTgwMC00ZWIzLWIzYjYtNWUxMTYxMWMwOGNmIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJqb3VybmFsX2xvZyIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
Timestamp

Bound call context

Receipt schema
0.4
Tool name
journal_log
Tool version
4.0.0
Permission scope
public
Caller type
session
Caller ID
sha256:02828adea4ceb5e2614302585eb05c9d1725a3093b41df973bee2af39cc2f790
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
empty
Evidence SHA-256
unavailable
Byte length
unavailable

Neutral Nostr anchor

Event ID
8f5e69497970c50301500aec94684c5fee943d5e4409112b39e3349bb740199e
Anchor status
published
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-08T00:22:23.469Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:29f684b182b223a4deb593da564fc56ded3f0e1fae746ee2c6cf629fe1889f49","receipt_uuid":"27c69f3d-84f7-487f-b713-559095d96b0e","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/27c69f3d-84f7-487f-b713-559095d96b0e/badge.svg)](https://zambo.dev/run/27c69f3d-84f7-487f-b713-559095d96b0e?ref=badge)

HTML

<a href="https://zambo.dev/run/27c69f3d-84f7-487f-b713-559095d96b0e?ref=badge"><img src="https://zambo.dev/api/receipt/27c69f3d-84f7-487f-b713-559095d96b0e/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

119,601 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.