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: bb416713-805f-4be4-953b-e7293e4a6554 entry / sequence: 1 entry / provenance class: LOGGED BY AGENT entry / tool name: bulletproof_spine_probe entry / redacted inputs hash: sha256:597bcaf5b4b0f15c420f546009f783208bd05203299501584127b555bc0cbd26 entry / started at: 2026-11-17T21:23:24.246Z entry / completed at: 2026-11-17T21:23:24.246Z entry / duration ms: 0 entry / executor identity: bulletproof-stranger entry / entry hash: sha256:e920d983afbafe41a9e76a1f1fd3cc3dd44b13662cd29fa0dcd2a7b5a1ed90e0 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 going when you need it

Every tool is free once a day, plus 3 continue calls. Continue for 24 hours with one Day Pass payment.

Day Pass · $0.99 for 24 hours

Compare longer access

Zambo does not start a payment automatically. You choose when to continue.

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-17T21:23:24.476Z; 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
bb2ec020-e8a6-41b0-a8d7-0a05ba798605
SHA-256 output hash
sha256:1509154a7bd3dc645f22f83cb08ded817cfcd840722dc5807959e711caf4889f
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YWMxNjc2ODlhZDAxOTE1NTViZWFhNGMwYmMzMDA4MmUzM2E4ODRjNWVkNWI2ZGJhOWM1NzMyZjQwYzQxOTU5MSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYXR0ZXN0cyI6IlphbWJvIGF0dGVzdHMgdGhhdCB0aGlzIHJlY29yZCB3YXMgcmVjZWl2ZWQsIHJlZGFjdGVkLCB0aW1lc3RhbXBlZCwgYW5kIGNoYWluZWQuIiwiZG9lc19ub3RfYXR0ZXN0IjoiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLiIsImVudHJ5Ijp7ImNvbXBsZXRlZF9hdCI6IjIwMjYtMTEtMTdUMjE6MjM6MjQuMjQ2WiIsImRlbGV0ZWQiOmZhbHNlLCJkdXJhdGlvbl9tcyI6MCwiZW50cnlfaGFzaCI6InNoYTI1NjplOTIwZDk4M2FmYmFmZTQxYTllNzZhMWYxZmQzY2MzZGQ0NGIxMzY2MmNkMjlmYTBkY2QyYTdiNWExZWQ5MGUwIiwiZW50cnlfaWQiOiJiYjQxNjcxMy04MDVmLTRiZTQtOTUzYi1lNzI5M2U0YTY1NTQiLCJleGVjdXRvcl9pZGVudGl0eSI6ImJ1bGxldHByb29mLXN0cmFuZ2VyIiwiZXh0ZXJuYWxfZXhlY3V0b3IiOm51bGwsIm1ldGFkYXRhIjp7fSwicHJldl9oYXNoIjpudWxsLCJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIiwicmVkYWN0ZWRfaW5wdXRzX2hhc2giOiJzaGEyNTY6NTk3YmNhZjViNGIwZjE1YzQyMGY1NDYwMDlmNzgzMjA4YmQwNTIwMzI5OTUwMTU4NDEyN2I1NTViYzBjYmQyNiIsInNlcXVlbmNlIjoxLCJzdGFydGVkX2F0IjoiMjAyNi0xMS0xN1QyMToyMzoyNC4yNDZaIiwidG9vbF9uYW1lIjoiYnVsbGV0cHJvb2Zfc3BpbmVfcHJvYmUifSwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInN0YXR1cyI6ImxvZ2dlZCIsInZlcmlmeV91cmwiOiJodHRwczovL3phbWJvLmRldi9hcGkvam91cm5hbC9bcHJpdmF0ZV0vdmVyaWZ5In0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJqb3VybmFsX2xvZyIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS40In19
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:ac167689ad0191555beaa4c0bc30082e33a884c5ed5b6dba9c5732f40c419591
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
8210022ae5759501e6ba06d5f7a9f1f54ab9d42faa2e6b4a6ada81dce0202d8b
Anchor status
published
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-17T21:23:24.476Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:1509154a7bd3dc645f22f83cb08ded817cfcd840722dc5807959e711caf4889f","receipt_uuid":"bb2ec020-e8a6-41b0-a8d7-0a05ba798605","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/bb2ec020-e8a6-41b0-a8d7-0a05ba798605/badge.svg)](https://zambo.dev/run/bb2ec020-e8a6-41b0-a8d7-0a05ba798605?ref=badge)

HTML

<a href="https://zambo.dev/run/bb2ec020-e8a6-41b0-a8d7-0a05ba798605?ref=badge"><img src="https://zambo.dev/api/receipt/bb2ec020-e8a6-41b0-a8d7-0a05ba798605/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

145,567 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.