Verifiable receipt 05f74f1a - capability_search result | Zambo

Verifiable receipt for a capability_search call on Zambo: {"query":"receipts","tools":[{"rank":1,"name":"zambo_check","description":"Evidence-aware universal pr

Observed result

{"query":"receipts","tools":[{"rank":1,"name":"zambo_check","description":"Evidence-aware universal preflight. Check a claim, source, tool, action, authorization boundary, execution, completion, output shape, freshness, conflict, or prompt security before relying on it. Returns compact machine-readable status, confidence, observed evidence, freshness, provenance scope, risk, recommended_action, next_action, and an integrity hash. It distinguishes claimed, observed, and verified and never turns a model opinion into proof. Legacy URL + optional GitHub legitimacy scoring remains supported. Free, no auth."}],"message":"Ask zambo_check to verify a receipt, or use continuity_get_recent with your job ID to find recorded work."}

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.

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 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-05T00:54:21.424Z; external immutability is not checked

Proof of observed execution

EXECUTED BY ZAMBO

Receipt ID: 05f74f1a-7c71-40f6-940b-5b26629eeceb
SHA-256 output hash: sha256:00e0c3dc83fbcacd407383824150af88afd3958ff468eebf96a9d37d9acf843b
Canonical bytes: eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YTgzMjBhMWRjOTdmMWU2MWE4OWI0MWQ0NTk3YTlmZThlODE4NzlkZjYyNzI2OTI5ZGJiYWY0NzkxNTdmZWE1NiIsInR5cGUiOiJzZXNzaW9uIn0sIm91dHB1dCI6eyJtZXNzYWdlIjoiQXNrIHphbWJvX2NoZWNrIHRvIHZlcmlmeSBhIHJlY2VpcHQsIG9yIHVzZSBjb250aW51aXR5X2dldF9yZWNlbnQgd2l0aCB5b3VyIGpvYiBJRCB0byBmaW5kIHJlY29yZGVkIHdvcmsuIiwicXVlcnkiOiJyZWNlaXB0cyIsInRvb2xzIjpbeyJkZXNjcmlwdGlvbiI6IkV2aWRlbmNlLWF3YXJlIHVuaXZlcnNhbCBwcmVmbGlnaHQuIENoZWNrIGEgY2xhaW0sIHNvdXJjZSwgdG9vbCwgYWN0aW9uLCBhdXRob3JpemF0aW9uIGJvdW5kYXJ5LCBleGVjdXRpb24sIGNvbXBsZXRpb24sIG91dHB1dCBzaGFwZSwgZnJlc2huZXNzLCBjb25mbGljdCwgb3IgcHJvbXB0IHNlY3VyaXR5IGJlZm9yZSByZWx5aW5nIG9uIGl0LiBSZXR1cm5zIGNvbXBhY3QgbWFjaGluZS1yZWFkYWJsZSBzdGF0dXMsIGNvbmZpZGVuY2UsIG9ic2VydmVkIGV2aWRlbmNlLCBmcmVzaG5lc3MsIHByb3ZlbmFuY2Ugc2NvcGUsIHJpc2ssIHJlY29tbWVuZGVkX2FjdGlvbiwgbmV4dF9hY3Rpb24sIGFuZCBhbiBpbnRlZ3JpdHkgaGFzaC4gSXQgZGlzdGluZ3Vpc2hlcyBjbGFpbWVkLCBvYnNlcnZlZCwgYW5kIHZlcmlmaWVkIGFuZCBuZXZlciB0dXJucyBhIG1vZGVsIG9waW5pb24gaW50byBwcm9vZi4gTGVnYWN5IFVSTCArIG9wdGlvbmFsIEdpdEh1YiBsZWdpdGltYWN5IHNjb3JpbmcgcmVtYWlucyBzdXBwb3J0ZWQuIEZyZWUsIG5vIGF1dGguIiwibmFtZSI6InphbWJvX2NoZWNrIiwicmFuayI6MX1dfSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuMyIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiY2FwYWJpbGl0eV9zZWFyY2giLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==
Timestamp: 2026-10-05T00:54:21.424Z

Bound call context

Receipt schema: 0.3
Tool name: capability_search
Tool version: 4.0.0
Permission scope: public
Caller type: session
Caller ID: sha256:a8320a1dc97f1e61a89b41d4597a9fe8e81879df62726929dbbaf479157fea56
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: 53d22c7c3450e8050000590f559adfdb41742a27ac8693ff456f241f52cea672
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-05T00:54:21.410Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:00e0c3dc83fbcacd407383824150af88afd3958ff468eebf96a9d37d9acf843b","receipt_uuid":"05f74f1a-7c71-40f6-940b-5b26629eeceb","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

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/05f74f1a-7c71-40f6-940b-5b26629eeceb/badge.svg)](https://zambo.dev/run/05f74f1a-7c71-40f6-940b-5b26629eeceb)

HTML

<a href="https://zambo.dev/run/05f74f1a-7c71-40f6-940b-5b26629eeceb"><img src="https://zambo.dev/api/receipt/05f74f1a-7c71-40f6-940b-5b26629eeceb/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG