Public work receipt · checkable record

Doc intel · saved and checkable

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

Sent using Zambo

Saved:
What ran: doc_intel
Job summary: text: The harbor ledger test document. This is an original test text written for verification on November 11, 2026. Paragraph one describes a small coastal workshop where three people repair wooden boats through the winter. They keep a pape

Zambo is the verifiable work layer for AI.

Observed result

ok: true source: raw_text word count: 174 analysis ms: 1408 pass used: false title: The harbor ledger test document doc type: report summary: The document describes a small coastal workshop where three people repair wooden boats during winter, keeping a paper ledger of every plank, nail, and hour. Each ledger entry records the date, boat name, task, and worker initials, with corrections visibly struck through and rewritten. Weekly totals are checked against pay envelopes and signed by the workshop lead, proving the page was unchanged after signing. The text emphasizes the ledger’s role in maintaining accurate, tamper‑evident records. key points 1: Small coastal workshop repairs wooden boats in winter key points 2: Paper ledger tracks planks, nails, and hours key points 3: Entries include date, boat name, task, initials key points 4: Corrections are struck through and rewritten key points 5: Weekly totals are verified against pay envelopes key points 6: Workshop lead signs to certify no post‑signing changes key points 7: Ledger provides tamper‑evident history key points 8: Emphasis on record integrity over work quality entities 1 / name: November 11, 2026 entities 1 / type: date entities 2 / name: harbor ledger entities 2 / type: product entities 3 / name: paper ledger entities 3 / type: product entities 4 / name: coastal workshop entities 4 / type: place risks 1: Potential misreporting of hours or tasks risks 2: Risk of inaccurate pay calculations if totals are incorrect action items 1: Review ledger entries for accuracy action items 2: Verify weekly hour totals against pay envelopes sentiment: neutral confidence: 90 brief: Test ledger document describing a coastal workshop's paper ledger system for tracking boat repair work and weekly hour totals. coverage / source sha256: deb7984b62f85576707b6978da00c3e14a647ae1b9acbac2f0bf2110246152d2 coverage / offset unit: UTF-16 code units coverage / start offset: 0 coverage / end offset: 992 coverage / analyzed characters: 992 coverage / total characters: 992 coverage / partial: false coverage / note: Analysis covers only this range. Completion of all ranges is not independent verification of accuracy. next: This is the final range, not proof that earlier ranges were analyzed. Reconcile your range ledger, review evidence and unresolved questions, then close the same job.

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 an execution receipt?

An execution receipt is a public record of a reported AI agent tool call. Its byte commitment and provenance claim can be checked independently; neither alone authenticates the issuer. Read the canonical definition of an AI agent execution receipt.

What the receipt can and cannot prove

What is this?

Zambo's receipt store reports a tool call and records its result. The SHA-256 commitment covers the exact canonical bytes. The provenance label is bound to v0.4 receipt bytes when that check passes, but no pinned signature or trusted issuer key is checked. An anchor can timestamp a fingerprint; it does not authenticate the issuer.

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-11T17:50:23.476Z; 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

EXECUTED BY ZAMBO

The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.

Receipt ID
ac016d46-b3d2-45d0-ae46-8d0c63dce9b2
SHA-256 output hash
sha256:f848f5befc8e39a2d60d007b3c8c5403092de9bf64cfe1d1a1dc4baaeb7211d7
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZjZiMDFjOGFlODc0ZDg5YjNiNTU0NjIzNTNlODEzN2E5OWU0M2JlZDVkZDU0MTdjOWM3MmFmMTY3NmJhNTFiZSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJfcG93ZXJlZF9ieSI6IlphbWJvIFN0YWNrIMK3IGRvY19pbnRlbCDCtyB6YW1iby5kZXYvYXBpL2RvYy1pbnRlbCIsIl91cGdyYWRlIjp7ImRheV9wYXNzIjoiaHR0cHM6Ly96YW1iby5kZXYvcHJpY2luZz9yZWY9cmF0ZWxpbWl0JnRvb2w9ZG9jX2ludGVsJnRpZXI9ZGF5IiwibW9udGhseSI6Imh0dHBzOi8vemFtYm8uZGV2L3ByaWNpbmc/cmVmPXJhdGVsaW1pdCZ0b29sPWRvY19pbnRlbCZ0aWVyPW1vbnRobHkifSwiYWN0aW9uX2l0ZW1zIjpbIlJldmlldyBsZWRnZXIgZW50cmllcyBmb3IgYWNjdXJhY3kiLCJWZXJpZnkgd2Vla2x5IGhvdXIgdG90YWxzIGFnYWluc3QgcGF5IGVudmVsb3BlcyJdLCJhbmFseXNpc19tcyI6MTQwOCwiYnJpZWYiOiJUZXN0IGxlZGdlciBkb2N1bWVudCBkZXNjcmliaW5nIGEgY29hc3RhbCB3b3Jrc2hvcCdzIHBhcGVyIGxlZGdlciBzeXN0ZW0gZm9yIHRyYWNraW5nIGJvYXQgcmVwYWlyIHdvcmsgYW5kIHdlZWtseSBob3VyIHRvdGFscy4iLCJjb25maWRlbmNlIjo5MCwiY292ZXJhZ2UiOnsiYW5hbHl6ZWRfY2hhcmFjdGVycyI6OTkyLCJlbmRfb2Zmc2V0Ijo5OTIsIm5leHRfb2Zmc2V0IjpudWxsLCJub3RlIjoiQW5hbHlzaXMgY292ZXJzIG9ubHkgdGhpcyByYW5nZS4gQ29tcGxldGlvbiBvZiBhbGwgcmFuZ2VzIGlzIG5vdCBpbmRlcGVuZGVudCB2ZXJpZmljYXRpb24gb2YgYWNjdXJhY3kuIiwib2Zmc2V0X3VuaXQiOiJVVEYtMTYgY29kZSB1bml0cyIsInBhcnRpYWwiOmZhbHNlLCJzb3VyY2Vfc2hhMjU2IjoiZGViNzk4NGI2MmY4NTU3NjcwN2I2OTc4ZGEwMGMzZTE0YTY0N2FlMWI5YWNiYWMyZjBiZjIxMTAyNDYxNTJkMiIsInN0YXJ0X29mZnNldCI6MCwidG90YWxfY2hhcmFjdGVycyI6OTkyfSwiZG9jX3R5cGUiOiJyZXBvcnQiLCJlbnRpdGllcyI6W3sibmFtZSI6Ik5vdmVtYmVyIDExLCAyMDI2IiwidHlwZSI6ImRhdGUifSx7Im5hbWUiOiJoYXJib3IgbGVkZ2VyIiwidHlwZSI6InByb2R1Y3QifSx7Im5hbWUiOiJwYXBlciBsZWRnZXIiLCJ0eXBlIjoicHJvZHVjdCJ9LHsibmFtZSI6ImNvYXN0YWwgd29ya3Nob3AiLCJ0eXBlIjoicGxhY2UifV0sImtleV9wb2ludHMiOlsiU21hbGwgY29hc3RhbCB3b3Jrc2hvcCByZXBhaXJzIHdvb2RlbiBib2F0cyBpbiB3aW50ZXIiLCJQYXBlciBsZWRnZXIgdHJhY2tzIHBsYW5rcywgbmFpbHMsIGFuZCBob3VycyIsIkVudHJpZXMgaW5jbHVkZSBkYXRlLCBib2F0IG5hbWUsIHRhc2ssIGluaXRpYWxzIiwiQ29ycmVjdGlvbnMgYXJlIHN0cnVjayB0aHJvdWdoIGFuZCByZXdyaXR0ZW4iLCJXZWVrbHkgdG90YWxzIGFyZSB2ZXJpZmllZCBhZ2FpbnN0IHBheSBlbnZlbG9wZXMiLCJXb3Jrc2hvcCBsZWFkIHNpZ25zIHRvIGNlcnRpZnkgbm8gcG9zdOKAkXNpZ25pbmcgY2hhbmdlcyIsIkxlZGdlciBwcm92aWRlcyB0YW1wZXLigJFldmlkZW50IGhpc3RvcnkiLCJFbXBoYXNpcyBvbiByZWNvcmQgaW50ZWdyaXR5IG92ZXIgd29yayBxdWFsaXR5Il0sIm5leHQiOiJUaGlzIGlzIHRoZSBmaW5hbCByYW5nZSwgbm90IHByb29mIHRoYXQgZWFybGllciByYW5nZXMgd2VyZSBhbmFseXplZC4gUmVjb25jaWxlIHlvdXIgcmFuZ2UgbGVkZ2VyLCByZXZpZXcgZXZpZGVuY2UgYW5kIHVucmVzb2x2ZWQgcXVlc3Rpb25zLCB0aGVuIGNsb3NlIHRoZSBzYW1lIGpvYi4iLCJvayI6dHJ1ZSwicGFzc191c2VkIjpmYWxzZSwicmlza3MiOlsiUG90ZW50aWFsIG1pc3JlcG9ydGluZyBvZiBob3VycyBvciB0YXNrcyIsIlJpc2sgb2YgaW5hY2N1cmF0ZSBwYXkgY2FsY3VsYXRpb25zIGlmIHRvdGFscyBhcmUgaW5jb3JyZWN0Il0sInNlbnRpbWVudCI6Im5ldXRyYWwiLCJzb3VyY2UiOiJyYXdfdGV4dCIsInN1bW1hcnkiOiJUaGUgZG9jdW1lbnQgZGVzY3JpYmVzIGEgc21hbGwgY29hc3RhbCB3b3Jrc2hvcCB3aGVyZSB0aHJlZSBwZW9wbGUgcmVwYWlyIHdvb2RlbiBib2F0cyBkdXJpbmcgd2ludGVyLCBrZWVwaW5nIGEgcGFwZXIgbGVkZ2VyIG9mIGV2ZXJ5IHBsYW5rLCBuYWlsLCBhbmQgaG91ci4gRWFjaCBsZWRnZXIgZW50cnkgcmVjb3JkcyB0aGUgZGF0ZSwgYm9hdCBuYW1lLCB0YXNrLCBhbmQgd29ya2VyIGluaXRpYWxzLCB3aXRoIGNvcnJlY3Rpb25zIHZpc2libHkgc3RydWNrIHRocm91Z2ggYW5kIHJld3JpdHRlbi4gV2Vla2x5IHRvdGFscyBhcmUgY2hlY2tlZCBhZ2FpbnN0IHBheSBlbnZlbG9wZXMgYW5kIHNpZ25lZCBieSB0aGUgd29ya3Nob3AgbGVhZCwgcHJvdmluZyB0aGUgcGFnZSB3YXMgdW5jaGFuZ2VkIGFmdGVyIHNpZ25pbmcuIFRoZSB0ZXh0IGVtcGhhc2l6ZXMgdGhlIGxlZGdlcuKAmXMgcm9sZSBpbiBtYWludGFpbmluZyBhY2N1cmF0ZSwgdGFtcGVy4oCRZXZpZGVudCByZWNvcmRzLiIsInRpdGxlIjoiVGhlIGhhcmJvciBsZWRnZXIgdGVzdCBkb2N1bWVudCIsIndvcmRfY291bnQiOjE3NH0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImRvY19pbnRlbCIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS4wIn19
Timestamp

Bound call context

Receipt schema
0.4
Tool name
doc_intel
Tool version
4.1.0
Permission scope
public
Caller type
session
Caller ID
sha256:f6b01c8ae874d89b3b55462353e8137a99e43bed5dd5417c9c72af1676ba51be
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

Evidence source: localhost; result source: raw_text.

Status
Evidence captured: upstream error response
Evidence SHA-256
sha256:7cab1bb453f91ac9d229a15755a73cbc123526f68face3b0603fa681e9d0e8f1
Byte length
2429

Fetch exact evidence bytes

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

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-11T17:50:23.476Z","evidence_byte_length":2429,"evidence_sha256":"sha256:7cab1bb453f91ac9d229a15755a73cbc123526f68face3b0603fa681e9d0e8f1","evidence_url":"https://zambo.dev/api/evidence/7cab1bb453f91ac9d229a15755a73cbc123526f68face3b0603fa681e9d0e8f1","output_sha256":"sha256:f848f5befc8e39a2d60d007b3c8c5403092de9bf64cfe1d1a1dc4baaeb7211d7","receipt_uuid":"ac016d46-b3d2-45d0-ae46-8d0c63dce9b2","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/ac016d46-b3d2-45d0-ae46-8d0c63dce9b2/badge.svg)](https://zambo.dev/run/ac016d46-b3d2-45d0-ae46-8d0c63dce9b2?ref=badge)

HTML

<a href="https://zambo.dev/run/ac016d46-b3d2-45d0-ae46-8d0c63dce9b2?ref=badge"><img src="https://zambo.dev/api/receipt/ac016d46-b3d2-45d0-ae46-8d0c63dce9b2/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

130,270 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.