Verifiable receipt 7bc9e064 - day_pass_activate result | Zambo

Verifiable receipt for a day_pass_activate call on Zambo: {"receipt_type":"x402_day_pass_activation","payment":{"receipt_id":"x402_738ead50-8a94-4295-9b99-82bc9

Observed result

{"receipt_type":"x402_day_pass_activation","payment":{"receipt_id":"x402_738ead50-8a94-4295-9b99-82bc93241775","resource":"https://zambo.dev/api/x402/day-pass","chain":"eip155:8453","asset":"0x8335…2913","pay_to":"0xb753…b9AC","max_amount":"990000","signed_payload_hash":"sha256:0aa8187b3de81b71d334dde00ed4147613417b789c48359f0a0d5f8a45413ba2","settlement_id":"0x1b04…771a"},"activation":{"activated_at":"2026-10-10T11:52:41.495Z","expires_at":"2026-10-11T11:52:41.488Z","window_seconds":86400},"verification":"Confirmed Base settlement and x402 spend receipt; bearer access key is not included."}

Settlement transaction: 0x1b04bdb0ac7ed25a15b66d6966aa92be6e46d57db94a00ee85e0e325e74a771a

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.

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: 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-10T11:52:41.551Z; 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: 7bc9e064-a0b0-490d-bef6-c1823970ba91
SHA-256 output hash: sha256:5c8792cdadee14bc7ada758bfc3f350af60e14155c45772d5866d8fa14109d62
Canonical bytes: eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ODk1MGUxN2ZjZTM2N2IzMTllY2JkMzA4N2EzNzQ5ZWVhMWRlODI5NTkzMTc5NGQyNjBlOTA0MmQ4ZDRkZGE1YiIsInR5cGUiOiJhcGlfa2V5In0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJhY3RpdmF0aW9uIjp7ImFjdGl2YXRlZF9hdCI6IjIwMjYtMTAtMTBUMTE6NTI6NDEuNDk1WiIsImV4cGlyZXNfYXQiOiIyMDI2LTEwLTExVDExOjUyOjQxLjQ4OFoiLCJ3aW5kb3dfc2Vjb25kcyI6ODY0MDB9LCJwYXltZW50Ijp7ImFzc2V0IjoiMHg4MzM1ODlmY2Q2ZWRiNmUwOGY0YzdjMzJkNGY3MWI1NGJkYTAyOTEzIiwiY2hhaW4iOiJlaXAxNTU6ODQ1MyIsIm1heF9hbW91bnQiOiI5OTAwMDAiLCJwYXlfdG8iOiIweGI3NTNiZTVFYWM1QjI5YzcxMTA1MURmRjkxMjc5ODM0ZTlDOWI5QUMiLCJyZWNlaXB0X2lkIjoieDQwMl83MzhlYWQ1MC04YTk0LTQyOTUtOWI5OS04MmJjOTMyNDE3NzUiLCJyZXNvdXJjZSI6Imh0dHBzOi8vemFtYm8uZGV2L2FwaS94NDAyL2RheS1wYXNzIiwic2V0dGxlbWVudF9pZCI6IjB4MWIwNGJkYjBhYzdlZDI1YTE1YjY2ZDY5NjZhYTkyYmU2ZTQ2ZDU3ZGI5NGEwMGVlODVlMGUzMjVlNzRhNzcxYSIsInNpZ25lZF9wYXlsb2FkX2hhc2giOiJzaGEyNTY6MGFhODE4N2IzZGU4MWI3MWQzMzRkZGUwMGVkNDE0NzYxMzQxN2I3ODljNDgzNTlmMGEwZDVmOGE0NTQxM2JhMiJ9LCJyZWNlaXB0X3R5cGUiOiJ4NDAyX2RheV9wYXNzX2FjdGl2YXRpb24iLCJ2ZXJpZmljYXRpb24iOiJDb25maXJtZWQgQmFzZSBzZXR0bGVtZW50IGFuZCB4NDAyIHNwZW5kIHJlY2VpcHQ7IGJlYXJlciBhY2Nlc3Mga2V5IGlzIG5vdCBpbmNsdWRlZC4ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjIwYjIzNjU5MTVmMDAyNmFjNTE1YmQ5MzhjZDYwMzVjOTZhNThkYWRlYmJmNDA1NWJhZTY3MGEyN2ZiM2NlMTkiLCJkZWNsYXJlZCI6WyJwYXltZW50IiwiYWNjZXNzX2FjdGl2YXRpb24iXSwic2NoZW1hX3ZlcnNpb24iOiIxIn0sInRvb2wiOnsibmFtZSI6ImRheV9wYXNzX2FjdGl2YXRlIiwic2NvcGUiOiJ4NDAyIiwidmVyc2lvbiI6IjEifX0=
Timestamp: 2026-10-10T11:52:41.551Z

Bound call context

Receipt schema: 0.4
Tool name: day_pass_activate
Tool version: 1
Permission scope: x402
Caller type: api_key
Caller ID: sha256:8950e17fce367b319ecbd3087a3749eea1de8295931794d260e9042d8d4dda5b
Declared side effects: payment, access_activation
Side-effects schema: 1
Declaration hash: sha256:20b2365915f0026ac515bd938cd6035c96a58dadebbf4055bae670a27fb3ce19

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: pending/unavailable
Anchor status: unavailable
Public key: unavailable

Relay hints: unavailable

Anchor status "unavailable": The anchor status is not available.

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.

Embed this receipt

Markdown

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/7bc9e064-a0b0-490d-bef6-c1823970ba91/badge.svg)](https://zambo.dev/run/7bc9e064-a0b0-490d-bef6-c1823970ba91)

HTML

<a href="https://zambo.dev/run/7bc9e064-a0b0-490d-bef6-c1823970ba91"><img src="https://zambo.dev/api/receipt/7bc9e064-a0b0-490d-bef6-c1823970ba91/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG