Verifiable receipt 9b561d21 - continuity_start_thread result | Zambo

Verifiable receipt for a continuity_start_thread call on Zambo: {"status":"created","thread_id":"c7f4a2e6-c900-4d3c-a434-cbe8adf5547d","session_id":"c7f4a2e6-c9

Observed result

{"status":"created","thread_id":"c7f4a2e6-c900-4d3c-a434-cbe8adf5547d","session_id":"c7f4a2e6-c900-4d3c-a434-cbe8adf5547d","name":"loop-canary-2026-10-03-continuity","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."}

Verify this receipt

This is a verifiable receipt: the result above is hashed and timestamped at a permanent URL.

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?

An AI agent completed a tool call through Zambo, and this page records the result. The SHA-256 hash below fingerprints exactly what the agent produced. The timestamp shows when it ran. The Nostr anchor posts that fingerprint to public relays, so the record exists outside Zambo too. Check the hash yourself.

What is an execution receipt?

An execution receipt is the public record of one completed AI agent tool call. Read the canonical definition of an AI agent execution receipt.

Keep the work moving

This receipt proves the call completed. 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 on X ·

Verification checks

Integrity check: Recomputable from canonical bytes
Issued by zambo.dev: Served from the zambo.dev receipt store
Chain valid: Receipt hash chain is internally consistent
Recorded in the immutable log: 2026-10-03T11:10:38.260Z

Proof of observed execution

EXECUTED BY ZAMBO

Receipt ID: 9b561d21-b107-4919-9ec8-cd1faf732455
SHA-256 output hash: sha256:0c49a1ddf698fddba38be4626f221ae38608b02fd9d6b0d42e8426b40bc80c67
Canonical bytes: eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZmVmZThmZmEwMTNhY2Y1NWIzOTlhMTI2MGQzYjQxMjRiMzI0MzUxMTAwYzM5MjM4ZDZiYWVlMjg3NGE1MjRhOSIsInR5cGUiOiJzZXNzaW9uIn0sIm91dHB1dCI6eyJpbnN0cnVjdGlvbnMiOiJVc2UgdGhpcyB0aHJlYWRfaWQgYXMgX3Nlc3Npb25faWQgb24gY2FsbHMgZnJvbSBhbnkgQUkgY2xpZW50LiBLZWVwIHRoZSBwYXJlbnQgam9iIElEIHRvIGxpc3Qgb3IgbWFuYWdlIGl0cyBuYW1lZCB0aHJlYWRzLiIsIm5hbWUiOiJsb29wLWNhbmFyeS0yMDI2LTEwLTAzLWNvbnRpbnVpdHkiLCJzZXNzaW9uX2lkIjoiYzdmNGEyZTYtYzkwMC00ZDNjLWE0MzQtY2JlOGFkZjU1NDdkIiwic3RhdHVzIjoiY3JlYXRlZCIsInRocmVhZF9pZCI6ImM3ZjRhMmU2LWM5MDAtNGQzYy1hNDM0LWNiZThhZGY1NTQ3ZCJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC4zIiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiY29udGludWl0eV9zdGFydF90aHJlYWQiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
Timestamp: 2026-10-03T11:10:38.260Z

Bound call context

Receipt schema: 0.3
Tool name: continuity_start_thread
Tool version: 4.0.0
Permission scope: public
Caller type: session
Caller ID: sha256:fefe8ffa013acf55b399a1260d3b4124b324351100c39238d6baee2874a524a9
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: 7992ad50d948dfd0ba4e19fb6dcd41a93125a9a396c691b520f2eb0dd4eacea1
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-03T11:10:38.243Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:0c49a1ddf698fddba38be4626f221ae38608b02fd9d6b0d42e8426b40bc80c67","receipt_uuid":"9b561d21-b107-4919-9ec8-cd1faf732455","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

Open the verification endpoint. The server recomputes the SHA-256 from the stored bytes and answers verified:true. If it does not say verified, do not trust this page. 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/9b561d21-b107-4919-9ec8-cd1faf732455/badge.svg)](https://zambo.dev/run/9b561d21-b107-4919-9ec8-cd1faf732455)

HTML

<a href="https://zambo.dev/run/9b561d21-b107-4919-9ec8-cd1faf732455"><img src="https://zambo.dev/api/receipt/9b561d21-b107-4919-9ec8-cd1faf732455/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG