Public work receipt · checkable record

Paused at the free limit · receipt

✓ This result hasn’t changed since it was saved.

Sent using Zambo

Saved:
What ran: handover
Job summary: goal: Deliver the verified BTC price snapshot to the named recipient so they can check the receipt themselves and decide on continued monitoring.

Zambo is the verifiable work layer for AI.

Observed result

status: upgrade_required limit reason: daily_free_wrap_up message: Your handover is ready and saved. Unlock it with Level 2. [Get Day Pass · $0.99](https://zambo.dev/day-pass/?source=wrap-up&job=[private]#checkout) human line: Your handover is ready and saved. Unlock it with Level 2. [Get Day Pass · $0.99](https://zambo.dev/day-pass/?source=wrap-up&job=[private]#checkout) day pass url: https://zambo.dev/day-pass/?source=wrap-up&job=[private]#checkout offer / text: Your handover is ready and saved. Unlock it with Level 2. [Get Day Pass · $0.99](https://zambo.dev/day-pass/?source=wrap-up&job=[private]#checkout) offer / button label: Get Day Pass · $0.99 offer / checkout url: https://zambo.dev/day-pass/?source=wrap-up&job=[private]#checkout x402 / protocol: x402 x402 / scheme: exact x402 / network: eip155:8453 x402 / asset: USDC x402 / amount: 990000 x402 / payTo: 0xb753…b9AC x402 / resource: https://zambo.dev/api/x402/day-pass x402 / retry same call: true retry: Call day_pass_status; it resumes your held handover automatically. Only repeat the call if it didn't. next / mcp url: https://zambo.dev/mcp next / prompt: Use Zambo to hand this over to your next AI. Include what you didn't check. next / setup: https://zambo.dev/handover

This is the saved result preview, not proof that the answer was correct.

Verify saved bytes 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 call that was refused before it ran.

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: 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-11-20T20:27:05.775Z; 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 metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.

Receipt ID
9d65c8bf-d964-4110-ac13-f75517dc4166
SHA-256 output hash
sha256:80fda2b9535c5964a5dfdf1cff840a293db420e3a4d99b06a205d8c504b2d7ed
Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6OWQxY2UzYjgyNWViMmY4MjJkZWFkMzk2M2FkNjFhNDIzM2Y2ZWJhNDliNGI4NmRhMDA4MWQwMjMwNjJhMWE1MyIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJkYXlfcGFzc191cmwiOiJodHRwczovL3phbWJvLmRldi9kYXktcGFzcy8/c291cmNlPXdyYXAtdXAmam9iPVtwcml2YXRlXSNjaGVja291dCIsImh1bWFuX2xpbmUiOiJZb3VyIGhhbmRvdmVyIGlzIHJlYWR5IGFuZCBzYXZlZC4gVW5sb2NrIGl0IHdpdGggTGV2ZWwgMi4gW0dldCBEYXkgUGFzcyDCtyAkMC45OV0oaHR0cHM6Ly96YW1iby5kZXYvZGF5LXBhc3MvP3NvdXJjZT13cmFwLXVwJmpvYj1bcHJpdmF0ZV0jY2hlY2tvdXQpIiwibGltaXRfcmVhc29uIjoiZGFpbHlfZnJlZV93cmFwX3VwIiwibWVzc2FnZSI6IllvdXIgaGFuZG92ZXIgaXMgcmVhZHkgYW5kIHNhdmVkLiBVbmxvY2sgaXQgd2l0aCBMZXZlbCAyLiBbR2V0IERheSBQYXNzIMK3ICQwLjk5XShodHRwczovL3phbWJvLmRldi9kYXktcGFzcy8/c291cmNlPXdyYXAtdXAmam9iPVtwcml2YXRlXSNjaGVja291dCkiLCJuZXh0Ijp7Im1jcF91cmwiOiJodHRwczovL3phbWJvLmRldi9tY3AiLCJwcm9tcHQiOiJVc2UgWmFtYm8gdG8gaGFuZCB0aGlzIG92ZXIgdG8geW91ciBuZXh0IEFJLiBJbmNsdWRlIHdoYXQgeW91IGRpZG4ndCBjaGVjay4iLCJzZXR1cCI6Imh0dHBzOi8vemFtYm8uZGV2L2hhbmRvdmVyIn0sIm9mZmVyIjp7ImJ1dHRvbl9sYWJlbCI6IkdldCBEYXkgUGFzcyDCtyAkMC45OSIsImNoZWNrb3V0X3VybCI6Imh0dHBzOi8vemFtYm8uZGV2L2RheS1wYXNzLz9zb3VyY2U9d3JhcC11cCZqb2I9W3ByaXZhdGVdI2NoZWNrb3V0IiwidGV4dCI6IllvdXIgaGFuZG92ZXIgaXMgcmVhZHkgYW5kIHNhdmVkLiBVbmxvY2sgaXQgd2l0aCBMZXZlbCAyLiBbR2V0IERheSBQYXNzIMK3ICQwLjk5XShodHRwczovL3phbWJvLmRldi9kYXktcGFzcy8/c291cmNlPXdyYXAtdXAmam9iPVtwcml2YXRlXSNjaGVja291dCkifSwicmV0cnkiOiJDYWxsIGRheV9wYXNzX3N0YXR1czsgaXQgcmVzdW1lcyB5b3VyIGhlbGQgaGFuZG92ZXIgYXV0b21hdGljYWxseS4gT25seSByZXBlYXQgdGhlIGNhbGwgaWYgaXQgZGlkbid0LiIsInN0YXR1cyI6InVwZ3JhZGVfcmVxdWlyZWQiLCJ4NDAyIjp7ImFtb3VudCI6Ijk5MDAwMCIsImFzc2V0IjoiVVNEQyIsIm5ldHdvcmsiOiJlaXAxNTU6ODQ1MyIsInBheVRvIjoiMHhiNzUzYmU1RWFjNUIyOWM3MTEwNTFEZkY5MTI3OTgzNGU5QzliOUFDIiwicHJvdG9jb2wiOiJ4NDAyIiwicmVzb3VyY2UiOiJodHRwczovL3phbWJvLmRldi9hcGkveDQwMi9kYXktcGFzcyIsInJldHJ5X3NhbWVfY2FsbCI6dHJ1ZSwic2NoZW1lIjoiZXhhY3QifX0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1NjpkZmI0NDEyYWE0MjlkM2FjNjM3YTA1NjY4YzQzNWJjYzkwYTI1MTM2M2ZjZGQ0OWY3Yjg1YWU0YWI1NWI1YmM5IiwiZGVjbGFyZWQiOlsic3RhdGVfd3JpdGUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJoYW5kb3ZlciIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMS40In19
Timestamp

Bound call context

Receipt schema
0.4
Tool name
handover
Tool version
4.1.4
Permission scope
public
Caller type
session
Caller ID
sha256:9d1ce3b825eb2f822dead3963ad61a4233f6eba49b4b86da0081d023062a1a53
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
ok
Evidence SHA-256
sha256:881838c7d6963bdb5b26e80fcf2e0633a6c16ea3081511a1f19d6d7bc5652c01
Byte length
752

Fetch exact evidence bytes

Upstream provenance

This receipt is independently auditable against the named upstream source. This is not a mathematical correctness claim.

  • Source: · queried at: · raw response hash:

Neutral Nostr anchor

Event ID
c98704a27d641b867756e65a93374119c35ffc8657116a8eb24bc08941a1d189
Anchor status
published
Public key
e13475107d30c918ec664adf2ab•••••24a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-20T20:27:05.775Z","evidence_byte_length":752,"evidence_sha256":"sha256:881838c7d6963bdb5b26e80fcf2e0633a6c16ea•••••11a1f19d6d7bc5652c01","evidence_url":"https://zambo.dev/api/evidence/881838c7d6963bdb5b26e80fcf2e0633a6c16ea•••••11a1f19d6d7bc5652c01","output_sha256":"sha256:80fda2b9535c5964a5dfdf1cff840a293db420e3a4d99b06a205d8c504b2d7ed","receipt_uuid":"9d65c8bf-d•••-••10-ac13-f75517dc4166","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

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: commitment matched; issuer, signature and chain not checked. This checks the saved bytes, not whether the answer was correct. Open the browser receipt checker. 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

[![Verifiable Zambo receipt](https://zambo.dev/api/receipt/9d65c8bf-d964-4110-ac13-f75517dc4166/badge.svg)](https://zambo.dev/run/9d65c8bf-d964-4110-ac13-f75517dc4166?ref=badge)

HTML

<a href="https://zambo.dev/run/9d65c8bf-d964-4110-ac13-f75517dc4166?ref=badge"><img src="https://zambo.dev/api/receipt/9d65c8bf-d964-4110-ac13-f75517dc4166/badge.svg" alt="Verifiable Zambo receipt"></a>

Open badge SVG

Recent receipts

154,803 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.