Verifiable receipt 9a9cf68f - client_response result | Zambo

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

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:07:52.123Z; external immutability is not checked

Committed provenance claim

LOGGED BY AGENT

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

Receipt ID

9a9cf68f-d181-4ab2-94af-6ad06cd16bc4

SHA-256 output hash

sha256:658ac9b47e8df0e842e605f1e5654d400955234a1acdfb16c9c61b3a3a65a4d0

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ODc5ZTEyMGMxZGQ3NGZlNTM0MjUyOGY0Mzk4ZDYyNjRiN2RjYWFhNzRjZTJlMWM3ZWE1NjFlNDAzM2I4NTIzYiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYWN0aW9uIjoiYWNjZXB0IiwiZGVjaWRlZF9ieSI6InRoZSBob2xkZXIgb2YgdGhlIGNsaWVudCBsaW5rIiwiaGFuZG92ZXJfaWQiOiJjMmNiYzZhNS05ZTc5LTQ5NTItOTE3MS1mMzFlMzFiYWIyZmIiLCJpZGVudGl0eV9ub3RpY2UiOiJDbGllbnQtbGluayBob2xkZXIgcmVzcG9uc2UuIFJldmlld2VyIGRldGFpbHMgYXJlIHNlbGYtcmVwb3J0ZWQsIG5vdCBpZGVudGl0eS12ZXJpZmllZC4iLCJraW5kIjoiY2xpZW50X2RlY2lzaW9uIiwib3JpZ2luYWxfbWVya2xlX3Jvb3QiOiIyOGE2M2M2ODk3MjljNjAyZmI4YjRhZmFmZGJiNTE1OTdiODIzOTFiOTY5NzJmNDNjYmExYjZjYzhjNTJiMjY0In0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImNsaWVudF9yZXNwb25zZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-10-18T15:07:52.123Z

Bound call context

Receipt schema

0.4

Tool name

client_response

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:879e120c1dd74fe5342528f4398d6264b7dcaaa74ce2e1c7ea561e4033b8523b

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

82546701ce29f1ea0c69c0dd0f24e2ad245cdbd844ca26c6869bcfbaf87f5df6

Anchor status

published

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:07:52.123Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:658ac9b47e8df0e842e605f1e5654d400955234a1acdfb16c9c61b3a3a65a4d0","receipt_uuid":"9a9cf68f-d181-4ab2-94af-6ad06cd16bc4","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

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.