Ask Zambo anything · saved and checkable

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-23T09:01:41.541Z; 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

3347c6ed-e48e-4d4e-8a43-66a7f2b3758b

SHA-256 output hash

sha256:acd73cedc3ad2ff00be35e8bd110e6fefb1eac03cfa11e510399be90a3fb2c07

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZTgwZmY0ZDAxNmU0NDFmMmE0N2IwN2I5NDkyODA4ZDMzMjNiODE2ZjA2ZDIyN2IzZWU3ZjI0MzdjNDhjNGU3ZCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJleGVjdXRlZFwiLFwicHJpbWFyeV90b29sXCI6XCJsaXZlX3ByaWNlXCIsXCJleGVjdXRlZFwiOnRydWUsXCJleGVjdXRlZF90b29sc1wiOltcImxpdmVfcHJpY2VcIl0sXCJyZXN1bHRcIjpcIkJUQyDCtyAkODEsNjk1LjAwIFVTRFxcbuKWvCAwLjA5JSAoMjRoKSDCtyBNYXJrZXQgY2FwOiAkMTY0Mi4yNUJcXG5cXG5MaXZlIHByaWNlIHZpYSBDb2luR2Vja28gwrcgRnJpLCAyMyBPY3QgMjAyNiAwOTowMToxOSBHTVRcIixcInZlcmlmeVwiOntcInN0YXR1c1wiOlwiY29tcGxldGVcIixcIm1lc3NhZ2VcIjpcIkJUQy1VU0QgcHJpY2UgYW5kIHNvdXJjZSB3ZXJlIHJldHVybmVkIGJ5IHRoZSBsaXZlIHByaWNlIHByb3ZpZGVyLlwifX0iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzb3VyY2VfY29tbWl0bWVudF9jaGVja2VkIjp0cnVlLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6NDRlOThmMGQwNTY1MGE1YjdlYjhiOGE5NzdmZmM0OTI3ZmE1YzIzYWRiMThkNjFkYTUyNTc5ODJiYzg1MDY0NyIsInNvdXJjZV9yZWNlaXB0X2lkIjoiOTQwNmI5NWYtMGVjOS00YTU0LTk4YTMtYTAyMGM0NDMzMzkxIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJ6YW1ib191bml2ZXJzYWwiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-10-23T09:01:41.541Z

Bound call context

Receipt schema

0.4

Tool name

zambo_universal

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:e80ff4d016e441f2a47b07b9492808d3323b816f06d227b3ee7f2437c48c4e7d

Declared side effects

state_write

Side-effects schema

zambo-side-effects/1

Declaration hash

sha256:dfb4412aa429d3ac637a05668c435bcc90a251363fcdd49f7b85ae4ab55b5bc9

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

eb5eefdee2f6a66fe2de0d949ea1ec18d7243fa2ed5435d9d7a14806a6b88fd2

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-23T09:01:41.541Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:acd73cedc3ad2ff00be35e8bd110e6fefb1eac03cfa11e510399be90a3fb2c07","receipt_uuid":"3347c6ed-e48e-4d4e-8a43-66a7f2b3758b","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.