Public work receipt · checkable record

Proof loop fix · saved and checkable

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

Sent using Zambo

Saved:
What ran: proof_loop_fix

Zambo is the verifiable work layer for AI.

Observed result

source receipt id: f94c53a2-582c-4263-88f8-490549172cd1 source output hash: sha256:80947881c53105b3bafb4d979e93b05d4aedff5931562f4e4639184cb888632c output: {"observation_withheld":true,"node_type":"fix","observation_commitment":"e73737aceaaf9129ee3f41ca60b31201bb06662a25519b8b29ff4fd2fd40bcc5"} 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-18T00:08:29.389Z; 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
c1715c48-46a8-4a3e-85f4-ae95012b94da
SHA-256 output hash
sha256:954278e192db205c8cbe876fb59a3a53c2a6644a4bf163478b283f87fe66230a
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NzY2N2QzMzVmZDE5MDRjNTFiMjYyMDliODNkYmM2MTc4OWM1YmJjM2Y1ZjhkNzU3NzllMDY2ZDQ0ZTRhMGMwYSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wib2JzZXJ2YXRpb25fd2l0aGhlbGRcIjp0cnVlLFwibm9kZV90eXBlXCI6XCJmaXhcIixcIm9ic2VydmF0aW9uX2NvbW1pdG1lbnRcIjpcImU3MzczN2FjZWFhZjkxMjllZTNmNDFjYTYwYjMxMjAxYmIwNjY2MmEyNTUxOWI4YjI5ZmY0ZmQyZmQ0MGJjYzVcIn0iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzb3VyY2VfY29tbWl0bWVudF9jaGVja2VkIjp0cnVlLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6ODA5NDc4ODFjNTMxMDViM2JhZmI0ZDk3OWU5M2IwNWQ0YWVkZmY1OTMxNTYyZjRlNDYzOTE4NGNiODg4NjMyYyIsInNvdXJjZV9yZWNlaXB0X2lkIjoiZjk0YzUzYTItNTgyYy00MjYzLTg4ZjgtNDkwNTQ5MTcyY2QxIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6InByb29mX2xvb3BfZml4Iiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4xLjQifX0=
Timestamp

Bound call context

Receipt schema
0.4
Tool name
proof_loop_fix
Tool version
4.1.4
Permission scope
public
Caller type
session
Caller ID
sha256:7667d335fd1904c51b26209b83dbc61789c5bbc3f5f8d75779e066d44e4a0c0a
Declared side effects
none
Side-effects schema
zambo-side-effects/1
Declaration hash
sha256:45aad38f3aa982b9aafe92ecb416ebe98791eddbaf8ab6df0bd08605b7c1bfee

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
af94c90f230f495b9abaf80a7136361410d4c5cdca3a6e4713cf91e19f5c28f6
Anchor status
published
Public key
e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-18T00:08:29.389Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:954278e192db205c8cbe876fb59a3a53c2a6644a4bf163478b283f87fe66230a","receipt_uuid":"c1715c48-46a8-4a3e-85f4-ae95012b94da","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/c1715c48-46a8-4a3e-85f4-ae95012b94da/badge.svg)](https://zambo.dev/run/c1715c48-46a8-4a3e-85f4-ae95012b94da?ref=badge)

HTML

<a href="https://zambo.dev/run/c1715c48-46a8-4a3e-85f4-ae95012b94da?ref=badge"><img src="https://zambo.dev/api/receipt/c1715c48-46a8-4a3e-85f4-ae95012b94da/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

146,954 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.