Verifiable receipt ac61a4f8 - new_session result | Zambo

Verifiable receipt for a new_session call on Zambo: {"status":"created","capture_enabled":true,"privacy_notice":"This named session preserves your continuity. Y

Observed result

{"status":"created","capture_enabled":true,"privacy_notice":"This named session preserves your continuity. You can turn capture off at any time with continuity_set_prefs {\"capture_enabled\":false}. Calls without a session ID are not captured.","instructions":"Use this session_id as _session_id on subsequent Zambo calls in this conversation. Use a different ID or omit it to start clean context; previous session context is not copied."}

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 · File this in Receipt Bot

Committed provenance claim

EXECUTED BY ZAMBO

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

Receipt ID
ac61a4f8-a780-4a66-adf2-ffacb001bca9
SHA-256 output hash
sha256:2e978bf76f0e0a9e39cc92e4c724a6541d151ddde67f9863e2c968c73b49472e
Canonical bytes
eyJjYWxsZXIiOnsiYmFzaXMiOiJpcF91YV8zMGQiLCJpZCI6InNoYTI1NjoxNjMyMGY2NzRhNjgwMTdmYmRhNjcyZDdjMDA3ODUxOTkzMTkzMmM0NmE5MmFkNjlhNzkyNGVmZDcyYTY3YjM4Iiwicm90YXRlc19hdCI6IjIwMjYtMTEtMDNUMDA6MDA6MDAuMDAwWiIsInR5cGUiOiJhbm9ueW1vdXMifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7ImNhcHR1cmVfZW5hYmxlZCI6dHJ1ZSwiaW5zdHJ1Y3Rpb25zIjoiVXNlIHRoaXMgc2Vzc2lvbl9pZCBhcyBfc2Vzc2lvbl9pZCBvbiBzdWJzZXF1ZW50IFphbWJvIGNhbGxzIGluIHRoaXMgY29udmVyc2F0aW9uLiBVc2UgYSBkaWZmZXJlbnQgSUQgb3Igb21pdCBpdCB0byBzdGFydCBjbGVhbiBjb250ZXh0OyBwcmV2aW91cyBzZXNzaW9uIGNvbnRleHQgaXMgbm90IGNvcGllZC4iLCJwcml2YWN5X25vdGljZSI6IlRoaXMgbmFtZWQgc2Vzc2lvbiBwcmVzZXJ2ZXMgeW91ciBjb250aW51aXR5LiBZb3UgY2FuIHR1cm4gY2FwdHVyZSBvZmYgYXQgYW55IHRpbWUgd2l0aCBjb250aW51aXR5X3NldF9wcmVmcyB7XCJjYXB0dXJlX2VuYWJsZWRcIjpmYWxzZX0uIENhbGxzIHdpdGhvdXQgYSBzZXNzaW9uIElEIGFyZSBub3QgY2FwdHVyZWQuIiwic3RhdHVzIjoiY3JlYXRlZCJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJuZXdfc2Vzc2lvbiIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
Timestamp

Bound call context

Receipt schema
0.4
Tool name
new_session
Tool version
4.0.0
Permission scope
public
Caller type
anonymous
Caller ID
sha256:16320f674a68017fbda672d7c0078519931932c46a92ad69a7924efd72a67b38
Caller basis
ip_ua_30d
Caller rotates at
2026-11-03T00:00:00.000Z
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
c82ded92955b3194f5238778bfd587675af724e159980b614f4685c79243f894
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-10T17:41:38.484Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:2e978bf76f0e0a9e39cc92e4c724a6541d151ddde67f9863e2c968c73b49472e","receipt_uuid":"ac61a4f8-a780-4a66-adf2-ffacb001bca9","schema_version":"zambo-receipt-anchor/1"}

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

Check this hash yourself

API v2 status: verified. This status summarizes the v2 commitment and provenance checks; it does not prove 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.

Embed this receipt

Markdown

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/ac61a4f8-a780-4a66-adf2-ffacb001bca9/badge.svg)](https://zambo.dev/run/ac61a4f8-a780-4a66-adf2-ffacb001bca9)

HTML

<a href="https://zambo.dev/run/ac61a4f8-a780-4a66-adf2-ffacb001bca9"><img src="https://zambo.dev/api/receipt/ac61a4f8-a780-4a66-adf2-ffacb001bca9/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

41,830 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