Verifiable receipt f3aa25eb — zambo_universal result | Zambo

Verifiable receipt for a zambo_universal call on Zambo: {"primary_job":"capability_search","executed":true,"result":{"query":"string","status":"execution_plan",

What is this?

An AI agent did real work through Zambo, and this page is the proof. The SHA-256 hash below is a fingerprint of exactly what the agent produced — change one character of the output and the fingerprint changes. The timestamp shows when it ran. The Nostr anchor posts that fingerprint to public relays, so the record exists outside Zambo too — anyone can look it up by the event ID below. You don't have to take the agent's word for it. 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.

Observed result

{"primary_job":"capability_search","executed":true,"result":{"query":"string","status":"execution_plan","tools":[],"execution_plan":[],"continuity":"For a multi-step job, call zambo_universal with the real request and one stable _session_id; reuse it with mode:'continue', then mode:'verify' before declaring completion.","note":"Links appear only where the confirmed capability requires a human web action, consent, payment, or visual administration."}}

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 ($1.49) → ZAMBO PASS $49 →

RUN YOUR OWN FREE CALL →

Or re-run this exact call — same tool, same 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-09-21T20:21:41.924Z

Proof of observed execution

Receipt ID: f3aa25eb-0a53-4647-abca-45fe0a9bf34c
SHA-256 output hash: sha256:3dfa1a1b6a8de06ede262df32e08346915bd88ca28932646019504db944da100
Canonical bytes: eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZjI2OWYyNWIxNzkxNzQ0OGUxZjgxNzJlYWNhZTdhYzViMjJlZjMyOGNhMjc4YWQ1YWQyZDZlZGMzNWZiZWJmZCIsInR5cGUiOiJzZXNzaW9uIn0sIm91dHB1dCI6eyJleGVjdXRlZCI6dHJ1ZSwicHJpbWFyeV9qb2IiOiJjYXBhYmlsaXR5X3NlYXJjaCIsInJlc3VsdCI6eyJjb250aW51aXR5IjoiRm9yIGEgbXVsdGktc3RlcCBqb2IsIGNhbGwgemFtYm9fdW5pdmVyc2FsIHdpdGggdGhlIHJlYWwgcmVxdWVzdCBhbmQgb25lIHN0YWJsZSBfc2Vzc2lvbl9pZDsgcmV1c2UgaXQgd2l0aCBtb2RlOidjb250aW51ZScsIHRoZW4gbW9kZTondmVyaWZ5JyBiZWZvcmUgZGVjbGFyaW5nIGNvbXBsZXRpb24uIiwiZXhlY3V0aW9uX3BsYW4iOltdLCJub3RlIjoiTGlua3MgYXBwZWFyIG9ubHkgd2hlcmUgdGhlIGNvbmZpcm1lZCBjYXBhYmlsaXR5IHJlcXVpcmVzIGEgaHVtYW4gd2ViIGFjdGlvbiwgY29uc2VudCwgcGF5bWVudCwgb3IgdmlzdWFsIGFkbWluaXN0cmF0aW9uLiIsInF1ZXJ5Ijoic3RyaW5nIiwic3RhdHVzIjoiZXhlY3V0aW9uX3BsYW4iLCJ0b29scyI6W119fSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuMyIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6InphbWJvX3VuaXZlcnNhbCIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19
Timestamp: 2026-09-21T20:21:41.924Z

Bound call context

Receipt schema: 0.3
Tool name: zambo_universal
Tool version: 4.0.0
Permission scope: public
Caller type: session
Caller ID: sha256:f269f25b17917448e1f8172eacae7ac5b22ef328ca278ad5ad2d6edc35fbebfd
Declared side effects: state_write
Side-effects schema: zambo-side-effects/1
Declaration hash: sha256:dfb4412aa429d3ac637a05668c435bcc90a251363fcdd49f7b85ae4ab55b5bc9

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: captured
Evidence SHA-256: sha256:a9693eb25aa95e0555d9c73d9204d95913a6fab44c052bb1f256b93af44e7b63
Byte length: 356

Fetch exact evidence bytes

Neutral Nostr anchor

Event ID: 60d64adad6d1f1f23f891a95009265856032007352ff7ca721fdb5bb4b9d2b99
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-09-21T20:21:41.772Z","evidence_byte_length":356,"evidence_sha256":"sha256:a9693eb25aa95e0555d9c73d9204d95913a6fab44c052bb1f256b93af44e7b63","evidence_url":"https://zambo.dev/api/evidence/a9693eb25aa95e0555d9c73d9204d95913a6fab44c052bb1f256b93af44e7b63","output_sha256":"sha256:3dfa1a1b6a8de06ede262df32e08346915bd88ca28932646019504db944da100","receipt_uuid":"f3aa25eb-0a53-4647-abca-45fe0a9bf34c","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

Open the verification endpoint — the server recomputes the SHA-256 from the stored bytes and answers verified:true. If it doesn't say verified, don't 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/f3aa25eb-0a53-4647-abca-45fe0a9bf34c/badge.svg)](https://zambo.dev/run/f3aa25eb-0a53-4647-abca-45fe0a9bf34c)

HTML

<a href="https://zambo.dev/run/f3aa25eb-0a53-4647-abca-45fe0a9bf34c"><img src="https://zambo.dev/api/receipt/f3aa25eb-0a53-4647-abca-45fe0a9bf34c/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent verifiable receipts

32,985 verifiable receipts minted