Verifiable receipt 7bab73ea - contract_scan 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 contract_scan call on Zambo: {"risk_level":"high","red_flags":[{"clause":"Party A shall deliver software by December 1, 2026.","issue":

Observed result

risk level: high red flags 1 / clause: Party A shall deliver software by December 1, 2026. red flags 1 / issue: The definition of 'deliver' is undefined. It is unclear if this means source code transfer, deployment to a server, or passing acceptance tests. This ambiguity can lead to disputes over whether the obligation was met. red flags 1 / severity: high red flags 1 / suggested fix: Define 'Delivery' explicitly, e.g., 'Delivery means the transfer of all source code, documentation, and binaries to Party B's designated repository, followed by successful execution of the agreed-upon acceptance test suite.' red flags 2 / clause: Failure to deliver incurs a 10% penalty per week. red flags 2 / issue: The base amount for the 10% penalty is not specified (10% of what? Contract value? Remaining balance?). Additionally, there is no cap on the penalty, which could theoretically exceed the total contract value, creating unlimited liability. red flags 2 / severity: critical red flags 2 / suggested fix: Specify the base amount (e.g., '10% of the total Contract Price') and add a cap (e.g., 'provided that the total penalty shall not exceed 50% of the total Contract Price'). red flags 3 / clause: This Agreement is entered into between Party A and Party B. red flags 3 / issue: The roles are not defined. It is unclear which party is the client and which is the vendor. If you are the 'signing party' and you are Party A, you are the one delivering. If you are Party B, you are the one receiving. The risk profile depends entirely on which side you are on, but the contract text itself lacks clarity on obligations beyond delivery. red flags 3 / severity: medium red flags 3 / suggested fix: Clearly identify Party A as the 'Vendor' and Party B as the 'Client' and define their respective roles in a preamble or definitions section. negotiation points 1: Define the specific criteria for 'Delivery' to avoid subjective disputes. negotiation points 2: Cap the cumulative penalty to a reasonable percentage of the total contract value. negotiation points 3: Clarify the base amount for the penalty calculation. negotiation points 4: Add a force majeure clause to protect against delays caused by events beyond reasonable control. plain english summary: Party A must hand over software by December 1, 2026. If they are late, they owe a penalty of 10% for every week of delay. The contract does not say what 10% is calculated on, nor does it limit how much total penalty can be charged. what you can push back on 1: The lack of a cap on the penalty fee. what you can push back on 2: The undefined base amount for the penalty calculation. what you can push back on 3: The vague definition of 'deliver' which could be interpreted broadly. overall verdict: This contract is dangerous due to the uncapped and undefined penalty clause. The 10% weekly penalty could quickly become unmanageable if the base amount is high or if the delay extends. The ambiguity in 'delivery' also creates significant legal risk. Do not sign without clarifying the penalty base, adding a cap, and defining delivery milestones. disclaimer: AI analysis — not legal advice. Consult a lawyer for binding decisions.

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-17T03:04:45.565Z; 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
7bab73ea-3f90-42c5-82e5-abcc626cc489
SHA-256 output hash
sha256:100c7827b6054cc9c4e2723ef99b3c3c8864f58a3e490f70b0b2f88f25e86cc4
Canonical bytes
eyJjYWxsZXIiOnsiYmFzaXMiOiJpcF91YV8zMGQiLCJpZCI6InNoYTI1Njo4MzFjMGI2M2E4ZTUwOGE2ZTUzNzM4YzA4M2FjNDAxODE0MzhhZjhmNmQxYjFiZTdlYTU2ZmYwY2ZhNzY2OGE5Iiwicm90YXRlc19hdCI6IjIwMjYtMTEtMDNUMDA6MDA6MDAuMDAwWiIsInR5cGUiOiJhbm9ueW1vdXMifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7ImRpc2NsYWltZXIiOiJBSSBhbmFseXNpcyDigJQgbm90IGxlZ2FsIGFkdmljZS4gQ29uc3VsdCBhIGxhd3llciBmb3IgYmluZGluZyBkZWNpc2lvbnMuIiwibmVnb3RpYXRpb25fcG9pbnRzIjpbIkRlZmluZSB0aGUgc3BlY2lmaWMgY3JpdGVyaWEgZm9yICdEZWxpdmVyeScgdG8gYXZvaWQgc3ViamVjdGl2ZSBkaXNwdXRlcy4iLCJDYXAgdGhlIGN1bXVsYXRpdmUgcGVuYWx0eSB0byBhIHJlYXNvbmFibGUgcGVyY2VudGFnZSBvZiB0aGUgdG90YWwgY29udHJhY3QgdmFsdWUuIiwiQ2xhcmlmeSB0aGUgYmFzZSBhbW91bnQgZm9yIHRoZSBwZW5hbHR5IGNhbGN1bGF0aW9uLiIsIkFkZCBhIGZvcmNlIG1hamV1cmUgY2xhdXNlIHRvIHByb3RlY3QgYWdhaW5zdCBkZWxheXMgY2F1c2VkIGJ5IGV2ZW50cyBiZXlvbmQgcmVhc29uYWJsZSBjb250cm9sLiJdLCJvdmVyYWxsX3ZlcmRpY3QiOiJUaGlzIGNvbnRyYWN0IGlzIGRhbmdlcm91cyBkdWUgdG8gdGhlIHVuY2FwcGVkIGFuZCB1bmRlZmluZWQgcGVuYWx0eSBjbGF1c2UuIFRoZSAxMCUgd2Vla2x5IHBlbmFsdHkgY291bGQgcXVpY2tseSBiZWNvbWUgdW5tYW5hZ2VhYmxlIGlmIHRoZSBiYXNlIGFtb3VudCBpcyBoaWdoIG9yIGlmIHRoZSBkZWxheSBleHRlbmRzLiBUaGUgYW1iaWd1aXR5IGluICdkZWxpdmVyeScgYWxzbyBjcmVhdGVzIHNpZ25pZmljYW50IGxlZ2FsIHJpc2suIERvIG5vdCBzaWduIHdpdGhvdXQgY2xhcmlmeWluZyB0aGUgcGVuYWx0eSBiYXNlLCBhZGRpbmcgYSBjYXAsIGFuZCBkZWZpbmluZyBkZWxpdmVyeSBtaWxlc3RvbmVzLiIsInBsYWluX2VuZ2xpc2hfc3VtbWFyeSI6IlBhcnR5IEEgbXVzdCBoYW5kIG92ZXIgc29mdHdhcmUgYnkgRGVjZW1iZXIgMSwgMjAyNi4gSWYgdGhleSBhcmUgbGF0ZSwgdGhleSBvd2UgYSBwZW5hbHR5IG9mIDEwJSBmb3IgZXZlcnkgd2VlayBvZiBkZWxheS4gVGhlIGNvbnRyYWN0IGRvZXMgbm90IHNheSB3aGF0IDEwJSBpcyBjYWxjdWxhdGVkIG9uLCBub3IgZG9lcyBpdCBsaW1pdCBob3cgbXVjaCB0b3RhbCBwZW5hbHR5IGNhbiBiZSBjaGFyZ2VkLiIsInJlZF9mbGFncyI6W3siY2xhdXNlIjoiUGFydHkgQSBzaGFsbCBkZWxpdmVyIHNvZnR3YXJlIGJ5IERlY2VtYmVyIDEsIDIwMjYuIiwiaXNzdWUiOiJUaGUgZGVmaW5pdGlvbiBvZiAnZGVsaXZlcicgaXMgdW5kZWZpbmVkLiBJdCBpcyB1bmNsZWFyIGlmIHRoaXMgbWVhbnMgc291cmNlIGNvZGUgdHJhbnNmZXIsIGRlcGxveW1lbnQgdG8gYSBzZXJ2ZXIsIG9yIHBhc3NpbmcgYWNjZXB0YW5jZSB0ZXN0cy4gVGhpcyBhbWJpZ3VpdHkgY2FuIGxlYWQgdG8gZGlzcHV0ZXMgb3ZlciB3aGV0aGVyIHRoZSBvYmxpZ2F0aW9uIHdhcyBtZXQuIiwic2V2ZXJpdHkiOiJoaWdoIiwic3VnZ2VzdGVkX2ZpeCI6IkRlZmluZSAnRGVsaXZlcnknIGV4cGxpY2l0bHksIGUuZy4sICdEZWxpdmVyeSBtZWFucyB0aGUgdHJhbnNmZXIgb2YgYWxsIHNvdXJjZSBjb2RlLCBkb2N1bWVudGF0aW9uLCBhbmQgYmluYXJpZXMgdG8gUGFydHkgQidzIGRlc2lnbmF0ZWQgcmVwb3NpdG9yeSwgZm9sbG93ZWQgYnkgc3VjY2Vzc2Z1bCBleGVjdXRpb24gb2YgdGhlIGFncmVlZC11cG9uIGFjY2VwdGFuY2UgdGVzdCBzdWl0ZS4nIn0seyJjbGF1c2UiOiJGYWlsdXJlIHRvIGRlbGl2ZXIgaW5jdXJzIGEgMTAlIHBlbmFsdHkgcGVyIHdlZWsuIiwiaXNzdWUiOiJUaGUgYmFzZSBhbW91bnQgZm9yIHRoZSAxMCUgcGVuYWx0eSBpcyBub3Qgc3BlY2lmaWVkICgxMCUgb2Ygd2hhdD8gQ29udHJhY3QgdmFsdWU/IFJlbWFpbmluZyBiYWxhbmNlPykuIEFkZGl0aW9uYWxseSwgdGhlcmUgaXMgbm8gY2FwIG9uIHRoZSBwZW5hbHR5LCB3aGljaCBjb3VsZCB0aGVvcmV0aWNhbGx5IGV4Y2VlZCB0aGUgdG90YWwgY29udHJhY3QgdmFsdWUsIGNyZWF0aW5nIHVubGltaXRlZCBsaWFiaWxpdHkuIiwic2V2ZXJpdHkiOiJjcml0aWNhbCIsInN1Z2dlc3RlZF9maXgiOiJTcGVjaWZ5IHRoZSBiYXNlIGFtb3VudCAoZS5nLiwgJzEwJSBvZiB0aGUgdG90YWwgQ29udHJhY3QgUHJpY2UnKSBhbmQgYWRkIGEgY2FwIChlLmcuLCAncHJvdmlkZWQgdGhhdCB0aGUgdG90YWwgcGVuYWx0eSBzaGFsbCBub3QgZXhjZWVkIDUwJSBvZiB0aGUgdG90YWwgQ29udHJhY3QgUHJpY2UnKS4ifSx7ImNsYXVzZSI6IlRoaXMgQWdyZWVtZW50IGlzIGVudGVyZWQgaW50byBiZXR3ZWVuIFBhcnR5IEEgYW5kIFBhcnR5IEIuIiwiaXNzdWUiOiJUaGUgcm9sZXMgYXJlIG5vdCBkZWZpbmVkLiBJdCBpcyB1bmNsZWFyIHdoaWNoIHBhcnR5IGlzIHRoZSBjbGllbnQgYW5kIHdoaWNoIGlzIHRoZSB2ZW5kb3IuIElmIHlvdSBhcmUgdGhlICdzaWduaW5nIHBhcnR5JyBhbmQgeW91IGFyZSBQYXJ0eSBBLCB5b3UgYXJlIHRoZSBvbmUgZGVsaXZlcmluZy4gSWYgeW91IGFyZSBQYXJ0eSBCLCB5b3UgYXJlIHRoZSBvbmUgcmVjZWl2aW5nLiBUaGUgcmlzayBwcm9maWxlIGRlcGVuZHMgZW50aXJlbHkgb24gd2hpY2ggc2lkZSB5b3UgYXJlIG9uLCBidXQgdGhlIGNvbnRyYWN0IHRleHQgaXRzZWxmIGxhY2tzIGNsYXJpdHkgb24gb2JsaWdhdGlvbnMgYmV5b25kIGRlbGl2ZXJ5LiIsInNldmVyaXR5IjoibWVkaXVtIiwic3VnZ2VzdGVkX2ZpeCI6IkNsZWFybHkgaWRlbnRpZnkgUGFydHkgQSBhcyB0aGUgJ1ZlbmRvcicgYW5kIFBhcnR5IEIgYXMgdGhlICdDbGllbnQnIGFuZCBkZWZpbmUgdGhlaXIgcmVzcGVjdGl2ZSByb2xlcyBpbiBhIHByZWFtYmxlIG9yIGRlZmluaXRpb25zIHNlY3Rpb24uIn1dLCJyaXNrX2xldmVsIjoiaGlnaCIsIndoYXRfeW91X2Nhbl9wdXNoX2JhY2tfb24iOlsiVGhlIGxhY2sgb2YgYSBjYXAgb24gdGhlIHBlbmFsdHkgZmVlLiIsIlRoZSB1bmRlZmluZWQgYmFzZSBhbW91bnQgZm9yIHRoZSBwZW5hbHR5IGNhbGN1bGF0aW9uLiIsIlRoZSB2YWd1ZSBkZWZpbml0aW9uIG9mICdkZWxpdmVyJyB3aGljaCBjb3VsZCBiZSBpbnRlcnByZXRlZCBicm9hZGx5LiJdfSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiY29udHJhY3Rfc2NhbiIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
Timestamp

Bound call context

Receipt schema
0.4
Tool name
contract_scan
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
a336108e09d3f1af5850b08f9a085d6501172fb94a20d90cc4740c243c39841c
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-17T03:04:45.565Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:100c7827b6054cc9c4e2723ef99b3c3c8864f58a3e490f70b0b2f88f25e86cc4","receipt_uuid":"7bab73ea-3f90-42c5-82e5-abcc626cc489","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

API v2 status: verified. This status summarizes the v2 commitment and provenance checks; it does not prove 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/7bab73ea-3f90-42c5-82e5-abcc626cc489/badge.svg)](https://zambo.dev/run/7bab73ea-3f90-42c5-82e5-abcc626cc489?ref=badge)

HTML

<a href="https://zambo.dev/run/7bab73ea-3f90-42c5-82e5-abcc626cc489?ref=badge"><img src="https://zambo.dev/api/receipt/7bab73ea-3f90-42c5-82e5-abcc626cc489/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

46,377 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