Verifiable receipt d38e5928 - code_review 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 code_review call on Zambo: {"overall_score":40,"language":"javascript","issues":[{"severity":"medium","type":"readability","line_hint":

Observed result

overall score: 40 language: javascript issues 1 / severity: medium issues 1 / type: readability issues 1 / line hint: 1 issues 1 / description: Multiple statements on a single line reduce readability and make debugging harder. issues 1 / fix: Split the code into separate lines: one for the function definition and one for the console.log call. issues 2 / severity: low issues 2 / type: style issues 2 / line hint: 1 issues 2 / description: Lack of whitespace around operators and after commas is inconsistent with common JavaScript style guides (like Prettier or Standard). issues 2 / fix: Add spaces around the arrow function and after the comma in the function call: `const sum = (a, b) => a + b;` and `console.log(sum(1, 2));`. issues 3 / severity: low issues 3 / type: readability issues 3 / line hint: 1 issues 3 / description: The function `sum` is defined but only used once immediately. In a larger context, this might be fine, but here it adds unnecessary abstraction for a simple operation. issues 3 / fix: Consider inlining the operation if the function is not reused: `console.log(1 + 2);`. quick wins 1: Add proper formatting and whitespace. quick wins 2: Split statements onto separate lines. refactor suggestions 1: If this is part of a larger module, ensure the function is exported or used appropriately. refactor suggestions 2: Add JSDoc comments for the function if it is intended for reuse. verdict: The code is functionally correct but lacks basic formatting and readability standards. It should be reformatted for clarity and maintainability.

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 ·

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-19T03:04:31.092Z; 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
d38e5928-f948-4c5d-9267-44c46f440521
SHA-256 output hash
sha256:55f0ab9ca929a6588edd3463fe473d54533364f035cbea091d813e8447d271d5
Canonical bytes
eyJjYWxsZXIiOnsiYmFzaXMiOiJpcF91YV8zMGQiLCJpZCI6InNoYTI1Njo4MzFjMGI2M2E4ZTUwOGE2ZTUzNzM4YzA4M2FjNDAxODE0MzhhZjhmNmQxYjFiZTdlYTU2ZmYwY2ZhNzY2OGE5Iiwicm90YXRlc19hdCI6IjIwMjYtMTEtMDNUMDA6MDA6MDAuMDAwWiIsInR5cGUiOiJhbm9ueW1vdXMifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7Imlzc3VlcyI6W3siZGVzY3JpcHRpb24iOiJNdWx0aXBsZSBzdGF0ZW1lbnRzIG9uIGEgc2luZ2xlIGxpbmUgcmVkdWNlIHJlYWRhYmlsaXR5IGFuZCBtYWtlIGRlYnVnZ2luZyBoYXJkZXIuIiwiZml4IjoiU3BsaXQgdGhlIGNvZGUgaW50byBzZXBhcmF0ZSBsaW5lczogb25lIGZvciB0aGUgZnVuY3Rpb24gZGVmaW5pdGlvbiBhbmQgb25lIGZvciB0aGUgY29uc29sZS5sb2cgY2FsbC4iLCJsaW5lX2hpbnQiOiIxIiwic2V2ZXJpdHkiOiJtZWRpdW0iLCJ0eXBlIjoicmVhZGFiaWxpdHkifSx7ImRlc2NyaXB0aW9uIjoiTGFjayBvZiB3aGl0ZXNwYWNlIGFyb3VuZCBvcGVyYXRvcnMgYW5kIGFmdGVyIGNvbW1hcyBpcyBpbmNvbnNpc3RlbnQgd2l0aCBjb21tb24gSmF2YVNjcmlwdCBzdHlsZSBndWlkZXMgKGxpa2UgUHJldHRpZXIgb3IgU3RhbmRhcmQpLiIsImZpeCI6IkFkZCBzcGFjZXMgYXJvdW5kIHRoZSBhcnJvdyBmdW5jdGlvbiBhbmQgYWZ0ZXIgdGhlIGNvbW1hIGluIHRoZSBmdW5jdGlvbiBjYWxsOiBgY29uc3Qgc3VtID0gKGEsIGIpID0+IGEgKyBiO2AgYW5kIGBjb25zb2xlLmxvZyhzdW0oMSwgMikpO2AuIiwibGluZV9oaW50IjoiMSIsInNldmVyaXR5IjoibG93IiwidHlwZSI6InN0eWxlIn0seyJkZXNjcmlwdGlvbiI6IlRoZSBmdW5jdGlvbiBgc3VtYCBpcyBkZWZpbmVkIGJ1dCBvbmx5IHVzZWQgb25jZSBpbW1lZGlhdGVseS4gSW4gYSBsYXJnZXIgY29udGV4dCwgdGhpcyBtaWdodCBiZSBmaW5lLCBidXQgaGVyZSBpdCBhZGRzIHVubmVjZXNzYXJ5IGFic3RyYWN0aW9uIGZvciBhIHNpbXBsZSBvcGVyYXRpb24uIiwiZml4IjoiQ29uc2lkZXIgaW5saW5pbmcgdGhlIG9wZXJhdGlvbiBpZiB0aGUgZnVuY3Rpb24gaXMgbm90IHJldXNlZDogYGNvbnNvbGUubG9nKDEgKyAyKTtgLiIsImxpbmVfaGludCI6IjEiLCJzZXZlcml0eSI6ImxvdyIsInR5cGUiOiJyZWFkYWJpbGl0eSJ9XSwibGFuZ3VhZ2UiOiJqYXZhc2NyaXB0Iiwib3ZlcmFsbF9zY29yZSI6NDAsInF1aWNrX3dpbnMiOlsiQWRkIHByb3BlciBmb3JtYXR0aW5nIGFuZCB3aGl0ZXNwYWNlLiIsIlNwbGl0IHN0YXRlbWVudHMgb250byBzZXBhcmF0ZSBsaW5lcy4iXSwicmVmYWN0b3Jfc3VnZ2VzdGlvbnMiOlsiSWYgdGhpcyBpcyBwYXJ0IG9mIGEgbGFyZ2VyIG1vZHVsZSwgZW5zdXJlIHRoZSBmdW5jdGlvbiBpcyBleHBvcnRlZCBvciB1c2VkIGFwcHJvcHJpYXRlbHkuIiwiQWRkIEpTRG9jIGNvbW1lbnRzIGZvciB0aGUgZnVuY3Rpb24gaWYgaXQgaXMgaW50ZW5kZWQgZm9yIHJldXNlLiJdLCJzZWN1cml0eV9mbGFncyI6W10sInZlcmRpY3QiOiJUaGUgY29kZSBpcyBmdW5jdGlvbmFsbHkgY29ycmVjdCBidXQgbGFja3MgYmFzaWMgZm9ybWF0dGluZyBhbmQgcmVhZGFiaWxpdHkgc3RhbmRhcmRzLiBJdCBzaG91bGQgYmUgcmVmb3JtYXR0ZWQgZm9yIGNsYXJpdHkgYW5kIG1haW50YWluYWJpbGl0eS4ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiY29kZV9yZXZpZXciLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
Timestamp

Bound call context

Receipt schema
0.4
Tool name
code_review
Tool version
4.0.0
Permission scope
public
Caller type
anonymous
Caller ID
sha256:831c0b63a8e508a6e53738c083ac40181438af8f6d1b1be7ea56ff0cfa7668a9
Caller basis
ip_ua_30d
Caller rotates at
2026-11-03T00:00:00.000Z
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
e8027bf1a316104b12d31708318aef2a8bf46e8540792dcbabd0e1b21a0268eb
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-19T03:04:31.092Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:55f0ab9ca929a6588edd3463fe473d54533364f035cbea091d813e8447d271d5","receipt_uuid":"d38e5928-f948-4c5d-9267-44c46f440521","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/d38e5928-f948-4c5d-9267-44c46f440521/badge.svg)](https://zambo.dev/run/d38e5928-f948-4c5d-9267-44c46f440521?ref=badge)

HTML

<a href="https://zambo.dev/run/d38e5928-f948-4c5d-9267-44c46f440521?ref=badge"><img src="https://zambo.dev/api/receipt/d38e5928-f948-4c5d-9267-44c46f440521/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

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