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: 5ae43ab2-4a26-412f-bf77-b3eee6114c91 entry / sequence: 2 entry / provenance class: LOGGED BY AGENT entry / tool name: work_step: sample ticket day logged, 3 fictional tickets entry / redacted inputs hash: sha256:233facc0507dec4f54a4a13280052de70effbcf0d4898ea5ab858d5ebf328b41 entry / started at: 2026-11-16T08:26:54.070Z entry / completed at: 2026-11-16T08:26:54.070Z entry / duration ms: 0 entry / executor identity: rambo (Zambo gift builder) entry / prev hash: sha256:cb1de7f6f0d6c5df89d64cd8f1ba41ec149f0da706167bac53f35e8a76e9aa09 entry / entry hash: sha256:6fb871589af979204db0a298735ff402092297c44566ef696cc8bb4bc0b0698c 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:26:54.278Z; 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
173f497c-bc30-40be-82be-47a1059f72da
SHA-256 output hash
sha256:cb6aa71cdca961b2aeeb5dae45a92b641b211574a0774001965c5c20dc590b23
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZjAxNDAzNDRhZmViZTZlNjZmNTUxMjUwMTRjMTliMjhjOTQ3YWRmMDM2YTBkYjEzOTJhN2FlY2IzYjc2ZTY2MiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYXR0ZXN0cyI6IlphbWJvIGF0dGVzdHMgdGhhdCB0aGlzIHJlY29yZCB3YXMgcmVjZWl2ZWQsIHJlZGFjdGVkLCB0aW1lc3RhbXBlZCwgYW5kIGNoYWluZWQuIiwiZG9lc19ub3RfYXR0ZXN0IjoiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLiIsImVudHJ5Ijp7ImNvbXBsZXRlZF9hdCI6IjIwMjYtMTEtMTZUMDg6MjY6NTQuMDcwWiIsImRlbGV0ZWQiOmZhbHNlLCJkdXJhdGlvbl9tcyI6MCwiZW50cnlfaGFzaCI6InNoYTI1Njo2ZmI4NzE1ODlhZjk3OTIwNGRiMGEyOTg3MzVmZjQwMjA5MjI5N2M0NDU2NmVmNjk2Y2M4YmI0YmMwYjA2OThjIiwiZW50cnlfaWQiOiI1YWU0M2FiMi00YTI2LTQxMmYtYmY3Ny1iM2VlZTYxMTRjOTEiLCJleGVjdXRvcl9pZGVudGl0eSI6InJhbWJvIChaYW1ibyBnaWZ0IGJ1aWxkZXIpIiwiZXh0ZXJuYWxfZXhlY3V0b3IiOm51bGwsIm1ldGFkYXRhIjp7fSwicHJldl9oYXNoIjoic2hhMjU2OmNiMWRlN2Y2ZjBkNmM1ZGY4OWQ2NGNkOGYxYmE0MWVjMTQ5ZjBkYTcwNjE2N2JhYzUzZjM1ZThhNzZlOWFhMDkiLCJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIiwicmVkYWN0ZWRfaW5wdXRzX2hhc2giOiJzaGEyNTY6MjMzZmFjYzA1MDdkZWM0ZjU0YTRhMTMyODAwNTJkZTcwZWZmYmNmMGQ0ODk4ZWE1YWI4NThkNWViZjMyOGI0MSIsInNlcXVlbmNlIjoyLCJzdGFydGVkX2F0IjoiMjAyNi0xMS0xNlQwODoyNjo1NC4wNzBaIiwidG9vbF9uYW1lIjoid29ya19zdGVwOiBzYW1wbGUgdGlja2V0IGRheSBsb2dnZWQsIDMgZmljdGlvbmFsIHRpY2tldHMifSwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInN0YXR1cyI6ImxvZ2dlZCIsInZlcmlmeV91cmwiOiJodHRwczovL3phbWJvLmRldi9hcGkvam91cm5hbC9bcHJpdmF0ZV0vdmVyaWZ5In0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJqb3VybmFsX2xvZyIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS40In19
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
27214cc75d4504423622e6fa91a9539e9b8df9d8de78e5f1cf9f254354d5c67d
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:26:54.278Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:cb6aa71cdca961b2aeeb5dae45a92b641b211574a0774001965c5c20dc590b23","receipt_uuid":"173f497c-bc30-40be-82be-47a1059f72da","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/173f497c-bc30-40be-82be-47a1059f72da/badge.svg)](https://zambo.dev/run/173f497c-bc30-40be-82be-47a1059f72da?ref=badge)

HTML

<a href="https://zambo.dev/run/173f497c-bc30-40be-82be-47a1059f72da?ref=badge"><img src="https://zambo.dev/api/receipt/173f497c-bc30-40be-82be-47a1059f72da/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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