Verifiable receipt 9b1883ad - continuity_list_threads result | Zambo

Observed result

{"status":"ok","threads":[],"message":"No job was selected. Call new_session to start, or pass your existing private job ID in _session_id."}

Check this receipt

This record shows the result and timestamp stored for the call. Recompute the SHA-256 commitment from the saved bytes in your browser; signatures and chain proofs are not checked.

• Read the AER-1 Internet-Draft
• Check the saved bytes in your browser
• Open the API v2 JSON check
• See example fixtures

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?

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 →

Share this receipt

Share on X · Copy link

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.
• 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-09T11:33:16.843Z; external immutability is not checked

Committed provenance claim

EXECUTED BY ZAMBO

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

Receipt ID

9b1883ad-e41f-4ca5-8ca7-c924525a971b

SHA-256 output hash

sha256:4578b23521c98d5cc3b5124a996ef543137087f11813e169edb3d144b024d921

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NTdlZTNjMjBhZjQ5N2VhY2QyOWE3NzYwY2FiZGM2MzJkMjUwMDkxODY0ODFjYTY5ZTliOThhYTczYmI3NmI0YyIsInR5cGUiOiJhbm9ueW1vdXMifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7Im1lc3NhZ2UiOiJObyBqb2Igd2FzIHNlbGVjdGVkLiBDYWxsIG5ld19zZXNzaW9uIHRvIHN0YXJ0LCBvciBwYXNzIHlvdXIgZXhpc3RpbmcgcHJpdmF0ZSBqb2IgSUQgaW4gX3Nlc3Npb25faWQuIiwic3RhdHVzIjoib2siLCJ0aHJlYWRzIjpbXX0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImNvbnRpbnVpdHlfbGlzdF90aHJlYWRzIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-10-09T11:33:16.843Z

Bound call context

Receipt schema

0.4

Tool name

continuity_list_threads

Tool version

4.0.0

Permission scope

public

Caller type

anonymous

Caller ID

sha256:57ee3c20af497eacd29a7760cabdc632d25009186481ca69e9b98aa73bb76b4c

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

5792242abb03d231fc4d56a52b3524799c763e57c0cc9f2f8f171f9d121c8344

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-09T11:33:16.831Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:4578b23521c98d5cc3b5124a996ef543137087f11813e169edb3d144b024d921","receipt_uuid":"9b1883ad-e41f-4ca5-8ca7-c924525a971b","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/9b1883ad-e41f-4ca5-8ca7-c924525a971b/badge.svg)](https://zambo.dev/run/9b1883ad-e41f-4ca5-8ca7-c924525a971b)

HTML

<a href="https://zambo.dev/run/9b1883ad-e41f-4ca5-8ca7-c924525a971b"><img src="https://zambo.dev/api/receipt/9b1883ad-e41f-4ca5-8ca7-c924525a971b/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

• live_price · 2026-10-09T12:16:18.611Z
• live_price · 2026-10-09T12:14:58.481Z
• zambot_spark · 2026-10-09T12:00:06.212Z
• continuity_list_threads · 2026-10-09T11:33:16.843Z
• continuity_get_recent · 2026-10-09T11:33:16.513Z