Verifiable receipt fca1cad6 - receipt_publication result | Zambo

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

Zambo is the verifiable work layer for AI. Verifiable receipt for a receipt_publication call on Zambo: {"schema":"zambo.redacted-receipt-publication/1","redacted_projection":true,"source_receipt_id":"f36

Observed result

schema: zambo.redacted-receipt-publication/1 redacted projection: true source receipt id: f36c2e82-3c10-46d5-af42-e11e31f9f5f3 source output hash: sha256:2781e71a6fdce09aab1b6966e0af2b7c5b092fda44ca243cf59af786d75fa311 source tool: new_session publication notice: This is a newly committed redacted publication copy, not the original tool output. The original commitment is unchanged and its private bytes are withheld. output: {"status":"created","instructions":"Use this session_id as _session_id on subsequent Zambo calls in this conversation. Use a different ID or omit it to start clean context; previous session context is not copied."}

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-18T20:04:05.172Z; 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
fca1cad6-cdc5-535f-a477-9d148dd8ab3e
SHA-256 output hash
sha256:74e79e53a2948d4d58b5e54416a655dbc99cf818e2a1efc254ee41758df91223
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZDZhNmEzMDM2ZjRlOGZjNWYzNGVjOWE0ODk4ZWE5YzZlNjYxOTI1ZjAxNmMyMjU1ZTM3OTI5Njg5NjdkZWRmOSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJjcmVhdGVkXCIsXCJpbnN0cnVjdGlvbnNcIjpcIlVzZSB0aGlzIHNlc3Npb25faWQgYXMgX3Nlc3Npb25faWQgb24gc3Vic2VxdWVudCBaYW1ibyBjYWxscyBpbiB0aGlzIGNvbnZlcnNhdGlvbi4gVXNlIGEgZGlmZmVyZW50IElEIG9yIG9taXQgaXQgdG8gc3RhcnQgY2xlYW4gY29udGV4dDsgcHJldmlvdXMgc2Vzc2lvbiBjb250ZXh0IGlzIG5vdCBjb3BpZWQuXCJ9IiwicHVibGljYXRpb25fbm90aWNlIjoiVGhpcyBpcyBhIG5ld2x5IGNvbW1pdHRlZCByZWRhY3RlZCBwdWJsaWNhdGlvbiBjb3B5LCBub3QgdGhlIG9yaWdpbmFsIHRvb2wgb3V0cHV0LiBUaGUgb3JpZ2luYWwgY29tbWl0bWVudCBpcyB1bmNoYW5nZWQgYW5kIGl0cyBwcml2YXRlIGJ5dGVzIGFyZSB3aXRoaGVsZC4iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzY2hlbWEiOiJ6YW1iby5yZWRhY3RlZC1yZWNlaXB0LXB1YmxpY2F0aW9uLzEiLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6Mjc4MWU3MWE2ZmRjZTA5YWFiMWI2OTY2ZTBhZjJiN2M1YjA5MmZkYTQ0Y2EyNDNjZjU5YWY3ODZkNzVmYTMxMSIsInNvdXJjZV9yZWNlaXB0X2lkIjoiZjM2YzJlODItM2MxMC00NmQ1LWFmNDItZTExZTMxZjlmNWYzIiwic291cmNlX3Rvb2wiOiJuZXdfc2Vzc2lvbiJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJyZWNlaXB0X3B1YmxpY2F0aW9uIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
Timestamp

Bound call context

Receipt schema
0.4
Tool name
receipt_publication
Tool version
4.0.0
Permission scope
public
Caller type
session
Caller ID
sha256:d6a6a3036f4e8fc5f34ec9a4898ea9c6e661925f016c2255e3792968967dedf9
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
no_upstream_bytes_captured
Evidence SHA-256
unavailable
Byte length
unavailable

Neutral Nostr anchor

Event ID
e512ea6c1ca6dc66522827772dbe7b8091136e710864b204b83bfe2cc13391b7
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-18T20:04:05.172Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:74e79e53a2948d4d58b5e54416a655dbc99cf818e2a1efc254ee41758df91223","receipt_uuid":"fca1cad6-cdc5-535f-a477-9d148dd8ab3e","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/fca1cad6-cdc5-535f-a477-9d148dd8ab3e/badge.svg)](https://zambo.dev/run/fca1cad6-cdc5-535f-a477-9d148dd8ab3e?ref=badge)

HTML

<a href="https://zambo.dev/run/fca1cad6-cdc5-535f-a477-9d148dd8ab3e?ref=badge"><img src="https://zambo.dev/api/receipt/fca1cad6-cdc5-535f-a477-9d148dd8ab3e/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

51,143 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