Verifiable receipt 32406a1e - continuity_start_thread result | Zambo

Verifiable receipt for a continuity_start_thread call on Zambo: {"status":"created","name":"receipt-bot-review-2026-10-10","instructions":"Use this thread_id as

Observed result

{"status":"created","name":"receipt-bot-review-2026-10-10","instructions":"Use this thread_id as _session_id on calls from any AI client. Keep the parent job ID to list or manage its named threads."}

Provenance for every timeline entry

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?

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.

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.

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 ·

Verification checks

Want a verifiable receipt for every job your bots do?

Add Zambo Receipt Bot to your team

Committed provenance claim

EXECUTED BY ZAMBO

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

Receipt ID
32406a1e-9e5a-47c5-aced-bff772e87d5c
SHA-256 output hash
sha256:1e0f9991fc08c81d783b0e1df21a3dd9c4d541a50f5cb975e6a9e9098cb74859
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YTg3NzdmOWNjNjg2MzY2NzA4MjA5NjI2NWU3ZTIyNDI2MmY5YWQyMjRiNjAxZWFmYjY4YmU1MDdlNWUwZDQ5YyIsImxhYmVsIjoicmVjZWlwdC1ib3QtcmV2aWV3IiwibGFiZWxfc291cmNlIjoiY2FsbGVyX3JlcG9ydGVkIiwidHlwZSI6InNlc3Npb24ifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7Imluc3RydWN0aW9ucyI6IlVzZSB0aGlzIHRocmVhZF9pZCBhcyBfc2Vzc2lvbl9pZCBvbiBjYWxscyBmcm9tIGFueSBBSSBjbGllbnQuIEtlZXAgdGhlIHBhcmVudCBqb2IgSUQgdG8gbGlzdCBvciBtYW5hZ2UgaXRzIG5hbWVkIHRocmVhZHMuIiwibmFtZSI6InJlY2VpcHQtYm90LXJldmlldy0yMDI2LTEwLTEwIiwic2Vzc2lvbl9pZCI6IjYxMzMxZmM0LTU1ZmEtNGQwYS05ZWM2LWRmNTRhYmY1MWRhZiIsInN0YXR1cyI6ImNyZWF0ZWQiLCJ0aHJlYWRfaWQiOiI2MTMzMWZjNC01NWZhLTRkMGEtOWVjNi1kZjU0YWJmNTFkYWYifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImNvbnRpbnVpdHlfc3RhcnRfdGhyZWFkIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
Timestamp

Bound call context

Receipt schema
0.4
Tool name
continuity_start_thread
Tool version
4.0.0
Permission scope
public
Caller type
session
Caller ID
sha256:a8777f9cc6863667082096265e7e224262f9ad224b601eafb68be507e5e0d49c
Caller-reported label
receipt-bot-review (caller_reported, not authenticated team ownership)
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
68c0de8d23cb4e87aecea609b7595dbd28b5d6b7aa6f88ed51aa3e0d0b37bcd0
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-10T10:42:32.097Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:1e0f9991fc08c81d783b0e1df21a3dd9c4d541a50f5cb975e6a9e9098cb74859","receipt_uuid":"32406a1e-9e5a-47c5-aced-bff772e87d5c","schema_version":"zambo-receipt-anchor/1"}

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

Check this hash yourself

Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. Signature and chain remain NOT CHECKED unless a real signature verifier or chain proof is supplied. There is no combined “verified” verdict. 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/32406a1e-9e5a-47c5-aced-bff772e87d5c/badge.svg)](https://zambo.dev/run/32406a1e-9e5a-47c5-aced-bff772e87d5c)

HTML

<a href="https://zambo.dev/run/32406a1e-9e5a-47c5-aced-bff772e87d5c"><img src="https://zambo.dev/api/receipt/32406a1e-9e5a-47c5-aced-bff772e87d5c/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

41,720 verifiable receipts minted

RUN YOUR OWN FREE CALL →

Run your own calls. Free, 20 free calls per metered tool each day, no account.

Open the interactive receipt view