Verifiable receipt d1849300 - 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":"bcf
Observed result
schema: zambo.redacted-receipt-publication/1 redacted projection: true source receipt id: bcfc11ee-ed2a-4e45-a014-e3b6dfe4f091 source output hash: sha256:7192f53e4a9445c38bee81dba80972980882d03c45a7c0c73b4ec153e090c367 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
This page shows the result and when it was saved. Use the receipt checker to see whether the saved result has changed.
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.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
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-18T15:21:37.357Z; external immutability is not checked
Get proof like this from your own 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
d1849300-29c1-57c3-ae07-900ac5b29f33- SHA-256 output hash
sha256:4dd0e5004e1bbe12f2efdc02ea1714741a1ab0ddf26790fc778d927d2a4c50a4- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6M2I3ZjZkNTBkYWNhYTUwODE1ZjVlZGQ2M2EwZmJmMjhjMzY4OTVkNTUwNzM3NzQxY2I0NDVmMDkyMWRiYmVjMSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJjcmVhdGVkXCIsXCJpbnN0cnVjdGlvbnNcIjpcIlVzZSB0aGlzIHNlc3Npb25faWQgYXMgX3Nlc3Npb25faWQgb24gc3Vic2VxdWVudCBaYW1ibyBjYWxscyBpbiB0aGlzIGNvbnZlcnNhdGlvbi4gVXNlIGEgZGlmZmVyZW50IElEIG9yIG9taXQgaXQgdG8gc3RhcnQgY2xlYW4gY29udGV4dDsgcHJldmlvdXMgc2Vzc2lvbiBjb250ZXh0IGlzIG5vdCBjb3BpZWQuXCJ9IiwicHVibGljYXRpb25fbm90aWNlIjoiVGhpcyBpcyBhIG5ld2x5IGNvbW1pdHRlZCByZWRhY3RlZCBwdWJsaWNhdGlvbiBjb3B5LCBub3QgdGhlIG9yaWdpbmFsIHRvb2wgb3V0cHV0LiBUaGUgb3JpZ2luYWwgY29tbWl0bWVudCBpcyB1bmNoYW5nZWQgYW5kIGl0cyBwcml2YXRlIGJ5dGVzIGFyZSB3aXRoaGVsZC4iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzY2hlbWEiOiJ6YW1iby5yZWRhY3RlZC1yZWNlaXB0LXB1YmxpY2F0aW9uLzEiLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6NzE5MmY1M2U0YTk0NDVjMzhiZWU4MWRiYTgwOTcyOTgwODgyZDAzYzQ1YTdjMGM3M2I0ZWMxNTNlMDkwYzM2NyIsInNvdXJjZV9yZWNlaXB0X2lkIjoiYmNmYzExZWUtZWQyYS00ZTQ1LWEwMTQtZTNiNmRmZTRmMDkxIiwic291cmNlX3Rvb2wiOiJuZXdfc2Vzc2lvbiJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJyZWNlaXB0X3B1YmxpY2F0aW9uIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=- 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:3b7f6d50dacaa50815f5edd63a0fbf28c36895d550737741cb445f0921dbbec1- 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
5431ae4fe373011da15773b2bbf53c64cbf169f4ed1a2df11aaa8f1d8323ee7e- 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-18T15:21:37.357Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:4dd0e5004e1bbe12f2efdc02ea1714741a1ab0ddf26790fc778d927d2a4c50a4","receipt_uuid":"d1849300-29c1-57c3-ae07-900ac5b29f33","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
[](https://zambo.dev/run/d1849300-29c1-57c3-ae07-900ac5b29f33?ref=badge)
HTML
<a href="https://zambo.dev/run/d1849300-29c1-57c3-ae07-900ac5b29f33?ref=badge"><img src="https://zambo.dev/api/receipt/d1849300-29c1-57c3-ae07-900ac5b29f33/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
50,484 verifiable receipts minted
Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.