Public work receipt · checkable record

Agent Day Pass payment confirmed · saved and checkable

This result could not be confirmed unchanged yet.

Sent using Zambo

Saved:
What ran: day_pass_activate
Job summary: Confirmed x402 Day Pass settlement with a verifiable receipt.

Zambo is the verifiable work layer for AI.

Observed result

receipt type: x402_day_pass_activation payment / receipt id: x402_86bf4817-f70c-48a1-aa3e-dc7026b845ab 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: 1490000 payment / signed payload hash: sha256:ebe258243b2fe0c72d2fa658c8fdaf71eb4fb7d1bddb2e7f429e51bc441b0840 payment / settlement id: 0xa828…bef6 activation / activated at: 2026-09-19T01:49:12.867Z activation / expires at: 2026-09-20T01:49:12.858Z 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.

Check this receipt Run your own
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.

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 this receipt

Share on X · Share on LinkedIn ·

Show technical verification checks

Verification checks

  • SHA-256 commitment: Checked independently against the exact decoded bytes
  • Provenance binding: FAIL; The receipt schema version is missing or unsupported; provenance binding was not accepted.
  • Metadata binding: LEGACY; legacy receipt, metadata is not cryptographically bound
  • 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-09-19T01:49:12.943Z; external immutability is not checked

Get proof like this from your own AI

Add to my 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 receipt schema version is missing or unsupported; provenance binding was not accepted.

Receipt ID
768e9f76-405c-4756-ab2d-ff15bc2cb9b9
SHA-256 output hash
sha256:09e214531c8ed812b5d26668042a842d5a71720cda4db28ccb3fe3fbb7568314
Canonical bytes
eyJhY3RpdmF0aW9uIjp7ImFjdGl2YXRlZF9hdCI6IjIwMjYtMDktMTlUMDE6NDk6MTIuODY3WiIsImV4cGlyZXNfYXQiOiIyMDI2LTA5LTIwVDAxOjQ5OjEyLjg1OFoiLCJ3aW5kb3dfc2Vjb25kcyI6ODY0MDB9LCJwYXltZW50Ijp7ImFzc2V0IjoiMHg4MzM1ODlmY2Q2ZWRiNmUwOGY0YzdjMzJkNGY3MWI1NGJkYTAyOTEzIiwiY2hhaW4iOiJlaXAxNTU6ODQ1MyIsIm1heF9hbW91bnQiOiIxNDkwMDAwIiwicGF5X3RvIjoiMHhiNzUzYmU1RWFjNUIyOWM3MTEwNTFEZkY5MTI3OTgzNGU5QzliOUFDIiwicmVjZWlwdF9pZCI6Ing0MDJfODZiZjQ4MTctZjcwYy00OGExLWFhM2UtZGM3MDI2Yjg0NWFiIiwicmVzb3VyY2UiOiJodHRwczovL3phbWJvLmRldi9hcGkveDQwMi9kYXktcGFzcyIsInNldHRsZW1lbnRfaWQiOiIweGE4MjhhZmU5MTVjZDIxNDk5ZWI4YWQ0MDZhZjdhOTZjNzJhYmIyM2VhYTZiZjhkMzhkMjRmMjBiYjgyOGJlZjYiLCJzaWduZWRfcGF5bG9hZF9oYXNoIjoic2hhMjU2OmViZTI1ODI0M2IyZmUwYzcyZDJmYTY1OGM4ZmRhZjcxZWI0ZmI3ZDFiZGRiMmU3ZjQyOWU1MWJjNDQxYjA4NDAifSwicmVjZWlwdF90eXBlIjoieDQwMl9kYXlfcGFzc19hY3RpdmF0aW9uIiwidmVyaWZpY2F0aW9uIjoiQ29uZmlybWVkIEJhc2Ugc2V0dGxlbWVudCBhbmQgeDQwMiBzcGVuZCByZWNlaXB0OyBiZWFyZXIgYWNjZXNzIGtleSBpcyBub3QgaW5jbHVkZWQuIn0=
Timestamp

Bound call context

Receipt schema
0.2
v0.2 receipt; call-context metadata was not recorded.

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.

Relay publication is separate from receipt integrity. When the original signed event is available, Zambo retries pending, partial, or failed anchors about once a minute. Relay acknowledgements are external, so there is no guaranteed completion time; the receipt remains checkable from its saved bytes and verification link.

Check this hash yourself

Receipt commitment: legacy_receipt. 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

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/768e9f76-405c-4756-ab2d-ff15bc2cb9b9/badge.svg)](https://zambo.dev/run/768e9f76-405c-4756-ab2d-ff15bc2cb9b9?ref=badge)

HTML

<a href="https://zambo.dev/run/768e9f76-405c-4756-ab2d-ff15bc2cb9b9?ref=badge"><img src="https://zambo.dev/api/receipt/768e9f76-405c-4756-ab2d-ff15bc2cb9b9/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

126,943 verifiable receipts minted

RUN YOUR OWN FREE CALL →

Get your own: connect https://zambo.dev/mcp. Free daily calls, no API key.

Open the interactive receipt view

Your AI's work could look like this

Run a first job free in Zambo Chat. No account needed.