Verifiable receipt 09bb713a - day_pass_activate result | Zambo
✓ This result hasn’t changed since it was saved.
Saved:
What was asked: The request recorded for this receipt.
Zambo is the verifiable work layer for AI.
Zambo is the verifiable work layer for AI. Verifiable receipt for a day_pass_activate call on Zambo: {"receipt_type":"x402_day_pass_activation","payment":{"receipt_id":"x402_77d95eba-1877-492b-901c-ca66f
Observed result
receipt type: x402_day_pass_activation payment / receipt id: x402_77d95eba-1877-492b-901c-ca66f37735c6 payment / resource: https://zambo.dev/api/x402/day-pass payment / chain: eip155:8453 payment / asset: 0x8335…2913 payment / pay to: 0xb753…b9AC payment / max amount: 990000 payment / signed payload hash: sha256:a33b5a51b9916705b30627d6f659b9cf782faf881f0f66082ab15f86c5749e67 payment / settlement id: 0x1c81…c8e6 activation / activated at: 2026-10-20T01:28:07.430Z activation / expires at: 2026-10-21T01:28:07.423Z activation / window seconds: 86400 verification: Confirmed Base settlement and x402 spend receipt; bearer access key is not included.
This is the saved result preview, not proof that the answer was correct.
Settlement transaction: 0x1c8169502c1ec322ebc226fa34b7ee9a36ad7876971aabdc807ee2e539bac8e6
Check this receipt
This page shows the result and when it was saved. Use the receipt checker to see whether the saved result has changed.
Show technical provenance details
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 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.
What the receipt can and cannot prove
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.
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
Show technical verification checks
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-20T01:28:07.504Z; external immutability is not checked
Get proof like this from your own AI
Get receipts for your own AI work: add zambo.dev/mcp
One URL, no key. Copy the line for your AI and add it yourself in its settings.
- ClaudeSettings, Connectors, Add custom connector, paste the URL.
https://zambo.dev/mcp - ChatGPTSettings, Apps and Connectors, developer mode, create a connector with this URL.
https://zambo.dev/mcp - GrokAdd a remote MCP server in your Grok client and paste the URL.
https://zambo.dev/mcp - CursorPaste into ~/.cursor/mcp.json.
{"mcpServers":{"zambo":{"url":"https://zambo.dev/mcp"}}}
Nothing is installed automatically. Full setup guides
Want a verifiable receipt for every job your bots do?
Add Zambo Receipt Bot to your team · File this in Receipt Bot
Show receipt data and verification evidence
Committed provenance claim
EXECUTED BY ZAMBO
The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
- Receipt ID
09bb713a-03c8-42c0-9c59-a6830e6ec922- SHA-256 output hash
sha256:4a148b2a68dd3f7835e33135ac314d306be3390fd320f48836cf8d2566c4cb67- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YTM5MzE5ZmE3NDFjOTQyM2Y2ODUzZWNiNDE0NjU1YmE4NmU5NWYwYjRmZDc3ZWExMWIwMjM4MmY5YzVhN2E2ZCIsInR5cGUiOiJhcGlfa2V5In0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJhY3RpdmF0aW9uIjp7ImFjdGl2YXRlZF9hdCI6IjIwMjYtMTAtMjBUMDE6Mjg6MDcuNDMwWiIsImV4cGlyZXNfYXQiOiIyMDI2LTEwLTIxVDAxOjI4OjA3LjQyM1oiLCJ3aW5kb3dfc2Vjb25kcyI6ODY0MDB9LCJwYXltZW50Ijp7ImFzc2V0IjoiMHg4MzM1ODlmY2Q2ZWRiNmUwOGY0YzdjMzJkNGY3MWI1NGJkYTAyOTEzIiwiY2hhaW4iOiJlaXAxNTU6ODQ1MyIsIm1heF9hbW91bnQiOiI5OTAwMDAiLCJwYXlfdG8iOiIweGI3NTNiZTVFYWM1QjI5YzcxMTA1MURmRjkxMjc5ODM0ZTlDOWI5QUMiLCJyZWNlaXB0X2lkIjoieDQwMl83N2Q5NWViYS0xODc3LTQ5MmItOTAxYy1jYTY2ZjM3NzM1YzYiLCJyZXNvdXJjZSI6Imh0dHBzOi8vemFtYm8uZGV2L2FwaS94NDAyL2RheS1wYXNzIiwic2V0dGxlbWVudF9pZCI6IjB4MWM4MTY5NTAyYzFlYzMyMmViYzIyNmZhMzRiN2VlOWEzNmFkNzg3Njk3MWFhYmRjODA3ZWUyZTUzOWJhYzhlNiIsInNpZ25lZF9wYXlsb2FkX2hhc2giOiJzaGEyNTY6YTMzYjVhNTFiOTkxNjcwNWIzMDYyN2Q2ZjY1OWI5Y2Y3ODJmYWY4ODFmMGY2NjA4MmFiMTVmODZjNTc0OWU2NyJ9LCJyZWNlaXB0X3R5cGUiOiJ4NDAyX2RheV9wYXNzX2FjdGl2YXRpb24iLCJ2ZXJpZmljYXRpb24iOiJDb25maXJtZWQgQmFzZSBzZXR0bGVtZW50IGFuZCB4NDAyIHNwZW5kIHJlY2VpcHQ7IGJlYXJlciBhY2Nlc3Mga2V5IGlzIG5vdCBpbmNsdWRlZC4ifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjIwYjIzNjU5MTVmMDAyNmFjNTE1YmQ5MzhjZDYwMzVjOTZhNThkYWRlYmJmNDA1NWJhZTY3MGEyN2ZiM2NlMTkiLCJkZWNsYXJlZCI6WyJwYXltZW50IiwiYWNjZXNzX2FjdGl2YXRpb24iXSwic2NoZW1hX3ZlcnNpb24iOiIxIn0sInRvb2wiOnsibmFtZSI6ImRheV9wYXNzX2FjdGl2YXRlIiwic2NvcGUiOiJ4NDAyIiwidmVyc2lvbiI6IjEifX0=- Timestamp
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:a39319fa741c9423f6853ecb414655ba86e95f0b4fd77ea11b02382f9c5a7a6d- 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
Receipt commitment: commitment matched; issuer, signature and chain not checked. This checks the saved bytes, not whether 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
[](https://zambo.dev/run/09bb713a-03c8-42c0-9c59-a6830e6ec922?ref=badge)
HTML
<a href="https://zambo.dev/run/09bb713a-03c8-42c0-9c59-a6830e6ec922?ref=badge"><img src="https://zambo.dev/api/receipt/09bb713a-03c8-42c0-9c59-a6830e6ec922/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
53,098 verifiable receipts minted
Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.