Verifiable receipt 4d545452 - continuity_get_recent result | Zambo

Verifiable receipt for a continuity_get_recent call on Zambo: {"status":"ok","events":[],"handoff_text":"No job was selected. Call new_session to start, or pass

Observed result

{"status":"ok","events":[],"handoff_text":"No job was selected. Call new_session to start, or pass your existing private job ID in _session_id.","privacy":{"capture_enabled":false}}

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-04T17:18:26.716Z

Proof of observed execution

EXECUTED BY ZAMBO

Receipt ID: 4d545452-4493-4e9f-ba15-c208165271f0
SHA-256 output hash: sha256:6567bb43fbf77fc2680681fceac9dd12e230c8c8111cd806ae3774251422979e
Canonical bytes: eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZWU3YTBiM2MwYTkyYjc0NDE1NmVlM2Y4ZmFhNjIzM2YwYTdhYTU4NTU1M2ExNmUwM2RhYTZhMmE2ZDQzNjM0MCIsInR5cGUiOiJhbm9ueW1vdXMifSwib3V0cHV0Ijp7ImV2ZW50cyI6W10sImhhbmRvZmZfdGV4dCI6Ik5vIGpvYiB3YXMgc2VsZWN0ZWQuIENhbGwgbmV3X3Nlc3Npb24gdG8gc3RhcnQsIG9yIHBhc3MgeW91ciBleGlzdGluZyBwcml2YXRlIGpvYiBJRCBpbiBfc2Vzc2lvbl9pZC4iLCJwcml2YWN5Ijp7ImNhcHR1cmVfZW5hYmxlZCI6ZmFsc2V9LCJzdGF0dXMiOiJvayJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC4zIiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJjb250aW51aXR5X2dldF9yZWNlbnQiLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
Timestamp: 2026-10-04T17:18:26.716Z

Bound call context

Receipt schema: 0.3
Tool name: continuity_get_recent
Tool version: 4.0.0
Permission scope: public
Caller type: anonymous
Caller ID: sha256:ee7a0b3c0a92b744156ee3f8faa6233f0a7aa585553a16e03daa6a2a6d436340
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: dd881659c3cc00fbec9bab943c4ffc1ec61693a68eed51c0db279274af59f821
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-04T17:18:26.701Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:6567bb43fbf77fc2680681fceac9dd12e230c8c8111cd806ae3774251422979e","receipt_uuid":"4d545452-4493-4e9f-ba15-c208165271f0","schema_version":"zambo-receipt-anchor/1"}

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

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/4d545452-4493-4e9f-ba15-c208165271f0/badge.svg)](https://zambo.dev/run/4d545452-4493-4e9f-ba15-c208165271f0)

HTML

<a href="https://zambo.dev/run/4d545452-4493-4e9f-ba15-c208165271f0"><img src="https://zambo.dev/api/receipt/4d545452-4493-4e9f-ba15-c208165271f0/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG