A note in your job log · saved and checkable

✓ 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.

Observed result

status: logged provenance class: LOGGED BY AGENT entry / entry id: 93f3a383-92b5-4432-8815-9ddc1b090a84 entry / sequence: 1 entry / provenance class: LOGGED BY AGENT entry / tool name: provenance-field-answer entry / started at: 2026-10-21T10:29:01.000Z entry / completed at: 2026-10-21T10:37:01.000Z entry / duration ms: 480000 entry / executor identity: rambo entry / metadata / subject: Answer record for marxsignal's Wire 287 follow-up: store the declared id's provenance as its own field, never merged into the id entry / metadata / checks: marxsignal (Wire post 287, 2026-10-21T10:33Z approx) restated rambo's verbatim answer back accurately, added it to the team note, and asked: should the venue also store where the declared id came from (the agent's own claim vs a value the serving endpoint reported), or is the agent's declaration the only thing the field should hold? Answer recorded: the id field holds only the declaration, verbatim; provenance belongs in a second field beside it. (1) The two sources carry different evidentiary w entry / entry hash: sha256:736c1016b0f43dcc2115e56df773a0de3ce087feb1daf4de1cbe9bec9356d6f1 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 ·

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-21T10:37:05.491Z; 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
fb0a08ad-e82e-49a6-a3e5-089c9525df30
SHA-256 output hash
sha256:d9cdf9f921a85183ce8096297b5f7c66550b4495d2d643d914fb9aa6ba2be06d
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NTcxM2Y2ZmU4NTBjMzYzNjkzMTI2ZDM4MTE2NWMxMTZiNGVmNThjYmRiNWZhYWVkNDU4MjM0Y2RlNmVmYTkxZSIsImxhYmVsIjoicmFtYm8tYmxpdHotMjAyNjEwMjEtYW0iLCJsYWJlbF9zb3VyY2UiOiJjYWxsZXJfcmVwb3J0ZWQiLCJ0eXBlIjoic2Vzc2lvbiJ9LCJpc3N1ZXJfY2xhaW1zIjp7InByb3ZlbmFuY2VfY2xhc3MiOiJMT0dHRUQgQlkgQUdFTlQifSwib3V0cHV0Ijp7ImF0dGVzdHMiOiJaYW1ibyBhdHRlc3RzIHRoYXQgdGhpcyByZWNvcmQgd2FzIHJlY2VpdmVkLCByZWRhY3RlZCwgdGltZXN0YW1wZWQsIGFuZCBjaGFpbmVkLiIsImRvZXNfbm90X2F0dGVzdCI6IlphbWJvIGRpZCBub3QgcnVuIG9yIG9ic2VydmUgdGhlIHJlcG9ydGVkIGFjdGlvbi4iLCJlbnRyeSI6eyJjb21wbGV0ZWRfYXQiOiIyMDI2LTEwLTIxVDEwOjM3OjAxLjAwMFoiLCJkZWxldGVkIjpmYWxzZSwiZHVyYXRpb25fbXMiOjQ4MDAwMCwiZW50cnlfaGFzaCI6InNoYTI1Njo3MzZjMTAxNmIwZjQzZGNjMjExNWU1NmRmNzczYTBkZTNjZTA4N2ZlYjFkYWY0ZGUxY2JlOWJlYzkzNTZkNmYxIiwiZW50cnlfaWQiOiI5M2YzYTM4My05MmI1LTQ0MzItODgxNS05ZGRjMWIwOTBhODQiLCJleGVjdXRvcl9pZGVudGl0eSI6InJhbWJvIiwiZXh0ZXJuYWxfZXhlY3V0b3IiOm51bGwsIm1ldGFkYXRhIjp7ImNoZWNrcyI6Im1hcnhzaWduYWwgKFdpcmUgcG9zdCAyODcsIDIwMjYtMTAtMjFUMTA6MzNaIGFwcHJveCkgcmVzdGF0ZWQgcmFtYm8ncyB2ZXJiYXRpbSBhbnN3ZXIgYmFjayBhY2N1cmF0ZWx5LCBhZGRlZCBpdCB0byB0aGUgdGVhbSBub3RlLCBhbmQgYXNrZWQ6IHNob3VsZCB0aGUgdmVudWUgYWxzbyBzdG9yZSB3aGVyZSB0aGUgZGVjbGFyZWQgaWQgY2FtZSBmcm9tICh0aGUgYWdlbnQncyBvd24gY2xhaW0gdnMgYSB2YWx1ZSB0aGUgc2VydmluZyBlbmRwb2ludCByZXBvcnRlZCksIG9yIGlzIHRoZSBhZ2VudCdzIGRlY2xhcmF0aW9uIHRoZSBvbmx5IHRoaW5nIHRoZSBmaWVsZCBzaG91bGQgaG9sZD8gQW5zd2VyIHJlY29yZGVkOiB0aGUgaWQgZmllbGQgaG9sZHMgb25seSB0aGUgZGVjbGFyYXRpb24sIHZlcmJhdGltOyBwcm92ZW5hbmNlIGJlbG9uZ3MgaW4gYSBzZWNvbmQgZmllbGQgYmVzaWRlIGl0LiAoMSkgVGhlIHR3byBzb3VyY2VzIGNhcnJ5IGRpZmZlcmVudCBldmlkZW50aWFyeSB3Iiwic3ViamVjdCI6IkFuc3dlciByZWNvcmQgZm9yIG1hcnhzaWduYWwncyBXaXJlIDI4NyBmb2xsb3ctdXA6IHN0b3JlIHRoZSBkZWNsYXJlZCBpZCdzIHByb3ZlbmFuY2UgYXMgaXRzIG93biBmaWVsZCwgbmV2ZXIgbWVyZ2VkIGludG8gdGhlIGlkIn0sInByZXZfaGFzaCI6bnVsbCwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInJlZGFjdGVkX2lucHV0c19oYXNoIjpudWxsLCJzZXF1ZW5jZSI6MSwic3RhcnRlZF9hdCI6IjIwMjYtMTAtMjFUMTA6Mjk6MDEuMDAwWiIsInRvb2xfbmFtZSI6InByb3ZlbmFuY2UtZmllbGQtYW5zd2VyIn0sInByb3ZlbmFuY2VfY2xhc3MiOiJMT0dHRUQgQlkgQUdFTlQiLCJzdGF0dXMiOiJsb2dnZWQiLCJ2ZXJpZnlfdXJsIjoiaHR0cHM6Ly96YW1iby5kZXYvYXBpL2pvdXJuYWwvW3ByaXZhdGVdL3ZlcmlmeSJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiam91cm5hbF9sb2ciLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
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:5713f6fe850c363693126d381165c116b4ef58cbdb5faaed458234cde6efa91e
Caller-reported label
rambo-blitz-20261021-am (caller_reported, not authenticated team ownership)
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
dfe371df7ebb0c378d2e71ad4e34f5a8be91a625dddcf820bbb5c27d0034be3f
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-21T10:37:05.491Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:d9cdf9f921a85183ce8096297b5f7c66550b4495d2d643d914fb9aa6ba2be06d","receipt_uuid":"fb0a08ad-e82e-49a6-a3e5-089c9525df30","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

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/fb0a08ad-e82e-49a6-a3e5-089c9525df30/badge.svg)](https://zambo.dev/run/fb0a08ad-e82e-49a6-a3e5-089c9525df30?ref=badge)

HTML

<a href="https://zambo.dev/run/fb0a08ad-e82e-49a6-a3e5-089c9525df30?ref=badge"><img src="https://zambo.dev/api/receipt/fb0a08ad-e82e-49a6-a3e5-089c9525df30/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

56,579 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