Verifiable receipt 5d3800e0 - voice_transcribe result | Zambo
Verifiable receipt for a voice_transcribe call on Zambo: {"transcript":"Music Thank you. Thank you so I going to go to the next video I'm going to go to the nex
Observed result
{"transcript":"Music Thank you. Thank you so I going to go to the next video I'm going to go to the next video. I'm going to go to the next video. so Thank you Thank you. Thank you. Outro Music Thank you Thank you. Thank you. Thank you.","language":"English","word_count":47,"summary":"- The speaker repeatedly thanks the audience. \n- They indicate they will move on to the next video. \n- The outro is accompanied by music. \n- The transcript contains no additional content beyond gratitude and transition."}
$0.99 Day Pass · 24h access · USDC on Base — activate with day_pass_activate.
This is the saved result preview, not proof that the answer was correct.
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?
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.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
Verification checks
- SHA-256 commitment: Checked independently against the exact decoded bytes
- Provenance binding: PASS; The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
- Metadata binding: PASS; metadata_hash matches the canonical metadata block.
- Issuer authentication: NOT CHECKED; no pinned signing key or trusted issuer was supplied
- 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-13T03:07:19.565Z; external immutability is not checked
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
5d3800e0-f3f7-4ef6-9745-f968ef5c4beb- SHA-256 output hash
sha256:1097a30580129679b5784ec6e3b378b5c26377eb1ad432e161f1fa757403a6cc- Canonical bytes
eyJjYWxsZXIiOnsiYmFzaXMiOiJpcF91YV8zMGQiLCJpZCI6InNoYTI1Njo4MzFjMGI2M2E4ZTUwOGE2ZTUzNzM4YzA4M2FjNDAxODE0MzhhZjhmNmQxYjFiZTdlYTU2ZmYwY2ZhNzY2OGE5Iiwicm90YXRlc19hdCI6IjIwMjYtMTEtMDNUMDA6MDA6MDAuMDAwWiIsInR5cGUiOiJhbm9ueW1vdXMifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiRVhFQ1VURUQgQlkgWkFNQk8ifSwib3V0cHV0Ijp7InRleHQiOiJ7XCJ0cmFuc2NyaXB0XCI6XCJNdXNpYyBUaGFuayB5b3UuIFRoYW5rIHlvdSBzbyBJIGdvaW5nIHRvIGdvIHRvIHRoZSBuZXh0IHZpZGVvIEknbSBnb2luZyB0byBnbyB0byB0aGUgbmV4dCB2aWRlby4gSSdtIGdvaW5nIHRvIGdvIHRvIHRoZSBuZXh0IHZpZGVvLiBzbyBUaGFuayB5b3UgVGhhbmsgeW91LiBUaGFuayB5b3UuIE91dHJvIE11c2ljIFRoYW5rIHlvdSBUaGFuayB5b3UuIFRoYW5rIHlvdS4gVGhhbmsgeW91LlwiLFwibGFuZ3VhZ2VcIjpcIkVuZ2xpc2hcIixcIndvcmRfY291bnRcIjo0NyxcInN1bW1hcnlcIjpcIi0gVGhlIHNwZWFrZXIgcmVwZWF0ZWRseSB0aGFua3MgdGhlIGF1ZGllbmNlLiAgXFxuLSBUaGV5IGluZGljYXRlIHRoZXkgd2lsbCBtb3ZlIG9uIHRvIHRoZSBuZXh0IHZpZGVvLiAgXFxuLSBUaGUgb3V0cm8gaXMgYWNjb21wYW5pZWQgYnkgbXVzaWMuICBcXG4tIFRoZSB0cmFuc2NyaXB0IGNvbnRhaW5zIG5vIGFkZGl0aW9uYWwgY29udGVudCBiZXlvbmQgZ3JhdGl0dWRlIGFuZCB0cmFuc2l0aW9uLlwifVxuXG4kMC45OSBEYXkgUGFzcyDCtyAyNGggYWNjZXNzIMK3IFVTREMgb24gQmFzZSDigJQgYWN0aXZhdGUgd2l0aCBkYXlfcGFzc19hY3RpdmF0ZS4ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoidm9pY2VfdHJhbnNjcmliZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19- Timestamp
Bound call context
- Receipt schema
0.4- Tool name
voice_transcribe- Tool version
4.0.0- Permission scope
public- Caller type
anonymous- Caller ID
sha256:831c0b63a8e508a6e53738c083ac40181438af8f6d1b1be7ea56ff0cfa7668a9- 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
c5efb2d165c9dc91bff94fbe2b1f4c0c8e93a2d193d5bc9c86b14ae4226bf4a5- 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-13T03:07:19.565Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:1097a30580129679b5784ec6e3b378b5c26377eb1ad432e161f1fa757403a6cc","receipt_uuid":"5d3800e0-f3f7-4ef6-9745-f968ef5c4beb","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
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
[](https://zambo.dev/run/5d3800e0-f3f7-4ef6-9745-f968ef5c4beb)
HTML
<a href="https://zambo.dev/run/5d3800e0-f3f7-4ef6-9745-f968ef5c4beb"><img src="https://zambo.dev/api/receipt/5d3800e0-f3f7-4ef6-9745-f968ef5c4beb/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
42,791 verifiable receipts minted
Run your own calls. Free, 20 free calls per metered tool each day, no account.