Verifiable receipt aacefe01 - new_session result | Zambo

Verifiable receipt for a new_session call on Zambo: {"status":"created","session_id":"e4c13796-7223-46f8-a2b1-3164d377020d","instructions":"Use this session_id

Observed result

{"status":"created","session_id":"e4c13796-7223-46f8-a2b1-3164d377020d","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."}

$0.99 Day Pass · 24h access · USDC on Base — activate with day_pass_activate.

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.

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.

Access is active

This receipt was created with paid access. Your Day Pass remains active until it expires; no additional Day Pass unlock is needed.

ZAMBO PASS $49 →

RUN YOUR OWN FREE CALL →

Or re-run this exact call, using the same tool and arguments.

Share on X ·

Verification checks

SHA-256 commitment: Recomputed by the linked API v2 check from the exact decoded bytes
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-04T23:42:41.618Z; external immutability is not checked

Proof of observed execution

EXECUTED BY ZAMBO

Receipt ID: aacefe01-1ef0-44a5-8a0a-52ed67b57511
SHA-256 output hash: sha256:8c55ed550cf2f9b8f1e7845e0a9cf0454c4f73c5a11f4b3dc8702250d791a768
Canonical bytes: eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZThkNzBkY2E4N2I1ZWVlNzFiOTQwYmUwMWNhMTA4N2Y0OWZjMmVjYTRiMjBhOGRkODY4MGRhM2U2ZmQ0OWUzNyIsInR5cGUiOiJhcGlfa2V5In0sIm91dHB1dCI6eyJ0ZXh0Ijoie1wic3RhdHVzXCI6XCJjcmVhdGVkXCIsXCJzZXNzaW9uX2lkXCI6XCJlNGMxMzc5Ni03MjIzLTQ2ZjgtYTJiMS0zMTY0ZDM3NzAyMGRcIixcImluc3RydWN0aW9uc1wiOlwiVXNlIHRoaXMgc2Vzc2lvbl9pZCBhcyBfc2Vzc2lvbl9pZCBvbiBzdWJzZXF1ZW50IFphbWJvIGNhbGxzIGluIHRoaXMgY29udmVyc2F0aW9uLiBVc2UgYSBkaWZmZXJlbnQgSUQgb3Igb21pdCBpdCB0byBzdGFydCBjbGVhbiBjb250ZXh0OyBwcmV2aW91cyBzZXNzaW9uIGNvbnRleHQgaXMgbm90IGNvcGllZC5cIn1cblxuJDAuOTkgRGF5IFBhc3MgwrcgMjRoIGFjY2VzcyDCtyBVU0RDIG9uIEJhc2Ug4oCUIGFjdGl2YXRlIHdpdGggZGF5X3Bhc3NfYWN0aXZhdGUuIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjMiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6Im5ld19zZXNzaW9uIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=
Timestamp: 2026-10-04T23:42:41.618Z

Bound call context

Receipt schema: 0.3
Tool name: new_session
Tool version: 4.0.0
Permission scope: public
Caller type: api_key
Caller ID: sha256:e8d70dca87b5eee71b940be01ca1087f49fc2eca4b20a8dd8680da3e6fd49e37
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: 8df6bea679093c55f00bad2132be2aeda51b53e3a7bed956b3aab7f8bde12667
Anchor status: failed
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-04T23:42:40.722Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:8c55ed550cf2f9b8f1e7845e0a9cf0454c4f73c5a11f4b3dc8702250d791a768","receipt_uuid":"aacefe01-1ef0-44a5-8a0a-52ed67b57511","schema_version":"zambo-receipt-anchor/1"}

Anchor status "failed": Publication was not confirmed by any configured relay target.

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/aacefe01-1ef0-44a5-8a0a-52ed67b57511/badge.svg)](https://zambo.dev/run/aacefe01-1ef0-44a5-8a0a-52ed67b57511)

HTML

<a href="https://zambo.dev/run/aacefe01-1ef0-44a5-8a0a-52ed67b57511"><img src="https://zambo.dev/api/receipt/aacefe01-1ef0-44a5-8a0a-52ed67b57511/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG