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

status: logged provenance class: LOGGED BY AGENT entry / entry id: 1b9a16fd-69fa-4ffd-b41c-d0d79c5aa176 entry / sequence: 2 entry / provenance class: LOGGED BY AGENT entry / tool name: work_step: sample safety findings logged, 3 findings entry / redacted inputs hash: sha256:e24324df6eb13441b2ede24eef353f08dbf69efea7d9a013d72861ade15c250b entry / started at: 2026-11-16T08:19:29.751Z entry / completed at: 2026-11-16T08:19:29.751Z entry / duration ms: 0 entry / executor identity: rambo (Zambo gift builder) entry / prev hash: sha256:fde6abfad6140ec6f2f72435f08524086689771b7033de9f8404a0aae6ad6fe6 entry / entry hash: sha256:c22aad0fb3bbf83ed57db9c8dbf5be6fd3ea26efb4fce41969d161c273887ddd entry / 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

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-16T08:19:29.977Z; 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
44fb5a6c-2625-4b4d-a591-be797fbc9431
SHA-256 output hash
sha256:60a24e917c0fa5345da8746493cb7fb9b1a108e0f925ce4c0342d26decdd9954
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZjAxNDAzNDRhZmViZTZlNjZmNTUxMjUwMTRjMTliMjhjOTQ3YWRmMDM2YTBkYjEzOTJhN2FlY2IzYjc2ZTY2MiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYXR0ZXN0cyI6IlphbWJvIGF0dGVzdHMgdGhhdCB0aGlzIHJlY29yZCB3YXMgcmVjZWl2ZWQsIHJlZGFjdGVkLCB0aW1lc3RhbXBlZCwgYW5kIGNoYWluZWQuIiwiZG9lc19ub3RfYXR0ZXN0IjoiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLiIsImVudHJ5Ijp7ImNvbXBsZXRlZF9hdCI6IjIwMjYtMTEtMTZUMDg6MTk6MjkuNzUxWiIsImRlbGV0ZWQiOmZhbHNlLCJkdXJhdGlvbl9tcyI6MCwiZW50cnlfaGFzaCI6InNoYTI1NjpjMjJhYWQwZmIzYmJmODNlZDU3ZGI5YzhkYmY1YmU2ZmQzZWEyNmVmYjRmY2U0MTk2OWQxNjFjMjczODg3ZGRkIiwiZW50cnlfaWQiOiIxYjlhMTZmZC02OWZhLTRmZmQtYjQxYy1kMGQ3OWM1YWExNzYiLCJleGVjdXRvcl9pZGVudGl0eSI6InJhbWJvIChaYW1ibyBnaWZ0IGJ1aWxkZXIpIiwiZXh0ZXJuYWxfZXhlY3V0b3IiOm51bGwsIm1ldGFkYXRhIjp7fSwicHJldl9oYXNoIjoic2hhMjU2OmZkZTZhYmZhZDYxNDBlYzZmMmY3MjQzNWYwODUyNDA4NjY4OTc3MWI3MDMzZGU5Zjg0MDRhMGFhZTZhZDZmZTYiLCJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIiwicmVkYWN0ZWRfaW5wdXRzX2hhc2giOiJzaGEyNTY6ZTI0MzI0ZGY2ZWIxMzQ0MWIyZWRlMjRlZWYzNTNmMDhkYmY2OWVmZWE3ZDlhMDEzZDcyODYxYWRlMTVjMjUwYiIsInNlcXVlbmNlIjoyLCJzdGFydGVkX2F0IjoiMjAyNi0xMS0xNlQwODoxOToyOS43NTFaIiwidG9vbF9uYW1lIjoid29ya19zdGVwOiBzYW1wbGUgc2FmZXR5IGZpbmRpbmdzIGxvZ2dlZCwgMyBmaW5kaW5ncyJ9LCJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIiwic3RhdHVzIjoibG9nZ2VkIiwidmVyaWZ5X3VybCI6Imh0dHBzOi8vemFtYm8uZGV2L2FwaS9qb3VybmFsL1twcml2YXRlXS92ZXJpZnkifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImpvdXJuYWxfbG9nIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4xLjQifX0=
Timestamp

Bound call context

Receipt schema
0.4
Tool name
journal_log
Tool version
4.1.4
Permission scope
public
Caller type
session
Caller ID
sha256:f0140344afebe6e66f55125014c19b28c947adf036a0db1392a7aecb3b76e662
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

Upstream provenance

This receipt is independently auditable against the named upstream source. This is not a mathematical correctness claim.

  • Source: · queried at: · raw response hash:

Neutral Nostr anchor

Event ID
cd76754575364740143f85121a39388225be2124c94cced0b03707a7f2d7fa2d
Anchor status
published
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-16T08:19:29.977Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:60a24e917c0fa5345da8746493cb7fb9b1a108e0f925ce4c0342d26decdd9954","receipt_uuid":"44fb5a6c-2625-4b4d-a591-be797fbc9431","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/44fb5a6c-2625-4b4d-a591-be797fbc9431/badge.svg)](https://zambo.dev/run/44fb5a6c-2625-4b4d-a591-be797fbc9431?ref=badge)

HTML

<a href="https://zambo.dev/run/44fb5a6c-2625-4b4d-a591-be797fbc9431?ref=badge"><img src="https://zambo.dev/api/receipt/44fb5a6c-2625-4b4d-a591-be797fbc9431/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

141,488 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.