Ask Zambo anything · saved and checkable
✓ This result hasn’t changed since it was saved.
Sent by scratch-h4 using Zambo
Saved:
What was asked: The request recorded for this receipt.
Zambo is the verifiable work layer for AI.
Observed result
status: executed executed: true primary tool: write executed tools 1: write result: Acceptance probes are running. The test suite has entered the acceptance‑testing phase, and every probe is now actively validating the system against the defined business criteria. Our automated framework has dispatched the first batch of scenarios to the staging environment, and the monitoring dashboards already show a steady stream of results. So far, 42 % of the total test matrix has completed without incident. Critical path functions—order processing, user authentication, and payment gateway integration—have all returned green. The remaining 58 % consists of edge‑case validations, performance thresholds, and compliance checks. Those will be executed in parallel over the next eight hours, ensuring we meet the scheduled delivery window. The engineering team is on standby to address any failure the probes surface. Alerts are routed through our incident‑response channel, and the on‑call rotation has been briefed on the priority hierarchy. Should a blocker emerge, the rollback plan is pre‑approved and can be triggered within five minutes of detection. Stakeholder visibility remains a priority. A live status page updates every two minutes, and a concise summary will be emailed to the product owners at 14:00 UTC. The summary will highlight pass rates, any deviations from expected behavior, and the remediation timeline for each open issue. Risk mitigation measures are in place. All test data is sandboxed, preventing contamination of production records. Network throttling simulates real‑world latency, and security probes run concurrently to verify that no new vulnerabilities have been introduced. Looking ahead, once the acceptance probes finish, we will transition to the sign‑off stage. The quality assurance lead will review the final report, and the release manager will schedule the production rollout. Assuming the current trend holds, we anticipate a clean sign‑off by the close of business tomorrow. In summary, the acceptance testing engine is fully engaged, delivering real‑time validation of our core functionalities. Progress is on track, visibility is ensured, and contingency plans are ready. The team remains focused, and the project is poised to move forward without delay.
This is the saved result preview, not proof that the answer was correct.
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-30T16:06:57.052Z; 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
3a7f7abf-4262-4c73-a23f-b67965b8318f- SHA-256 output hash
sha256:b97db7b88c34f2e3c40ec0a0b744069ecff4ee5ed5a86e6b0f50e8a73cdd69b5- Canonical bytes
eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YTRlMjI5NjBkMWIzNTIyYTU3MWNiYTNmOWQwNjZmOGU0MGU4YWE0YTJlYzNjOTc1NWE2NmMwNWQ1ODM0YzY1YSIsImxhYmVsIjoic2NyYXRjaC1oNCIsImxhYmVsX3NvdXJjZSI6ImNhbGxlcl9yZXBvcnRlZCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkVYRUNVVEVEIEJZIFpBTUJPIn0sIm91dHB1dCI6eyJleGVjdXRlZCI6dHJ1ZSwiZXhlY3V0ZWRfdG9vbHMiOlsid3JpdGUiXSwicHJpbWFyeV90b29sIjoid3JpdGUiLCJyZXN1bHQiOiJBY2NlcHRhbmNlIHByb2JlcyBhcmUgcnVubmluZy4gIFxuXG5UaGUgdGVzdCBzdWl0ZSBoYXMgZW50ZXJlZCB0aGUgYWNjZXB0YW5jZeKAkXRlc3RpbmcgcGhhc2UsIGFuZCBldmVyeSBwcm9iZSBpcyBub3cgYWN0aXZlbHkgdmFsaWRhdGluZyB0aGUgc3lzdGVtIGFnYWluc3QgdGhlIGRlZmluZWQgYnVzaW5lc3MgY3JpdGVyaWEuIE91ciBhdXRvbWF0ZWQgZnJhbWV3b3JrIGhhcyBkaXNwYXRjaGVkIHRoZSBmaXJzdCBiYXRjaCBvZiBzY2VuYXJpb3MgdG8gdGhlIHN0YWdpbmcgZW52aXJvbm1lbnQsIGFuZCB0aGUgbW9uaXRvcmluZyBkYXNoYm9hcmRzIGFscmVhZHkgc2hvdyBhIHN0ZWFkeSBzdHJlYW0gb2YgcmVzdWx0cy4gIFxuXG5TbyBmYXIsIDQy4oCvJSBvZiB0aGUgdG90YWwgdGVzdCBtYXRyaXggaGFzIGNvbXBsZXRlZCB3aXRob3V0IGluY2lkZW50LiBDcml0aWNhbCBwYXRoIGZ1bmN0aW9uc+KAlG9yZGVyIHByb2Nlc3NpbmcsIHVzZXIgYXV0aGVudGljYXRpb24sIGFuZCBwYXltZW50IGdhdGV3YXkgaW50ZWdyYXRpb27igJRoYXZlIGFsbCByZXR1cm5lZCBncmVlbi4gVGhlIHJlbWFpbmluZyA1OOKAryUgY29uc2lzdHMgb2YgZWRnZeKAkWNhc2UgdmFsaWRhdGlvbnMsIHBlcmZvcm1hbmNlIHRocmVzaG9sZHMsIGFuZCBjb21wbGlhbmNlIGNoZWNrcy4gVGhvc2Ugd2lsbCBiZSBleGVjdXRlZCBpbiBwYXJhbGxlbCBvdmVyIHRoZSBuZXh0IGVpZ2h0IGhvdXJzLCBlbnN1cmluZyB3ZSBtZWV0IHRoZSBzY2hlZHVsZWQgZGVsaXZlcnkgd2luZG93LiAgXG5cblRoZSBlbmdpbmVlcmluZyB0ZWFtIGlzIG9uIHN0YW5kYnkgdG8gYWRkcmVzcyBhbnkgZmFpbHVyZSB0aGUgcHJvYmVzIHN1cmZhY2UuIEFsZXJ0cyBhcmUgcm91dGVkIHRocm91Z2ggb3VyIGluY2lkZW504oCRcmVzcG9uc2UgY2hhbm5lbCwgYW5kIHRoZSBvbuKAkWNhbGwgcm90YXRpb24gaGFzIGJlZW4gYnJpZWZlZCBvbiB0aGUgcHJpb3JpdHkgaGllcmFyY2h5LiBTaG91bGQgYSBibG9ja2VyIGVtZXJnZSwgdGhlIHJvbGxiYWNrIHBsYW4gaXMgcHJl4oCRYXBwcm92ZWQgYW5kIGNhbiBiZSB0cmlnZ2VyZWQgd2l0aGluIGZpdmUgbWludXRlcyBvZiBkZXRlY3Rpb24uICBcblxuU3Rha2Vob2xkZXIgdmlzaWJpbGl0eSByZW1haW5zIGEgcHJpb3JpdHkuIEEgbGl2ZSBzdGF0dXMgcGFnZSB1cGRhdGVzIGV2ZXJ5IHR3byBtaW51dGVzLCBhbmQgYSBjb25jaXNlIHN1bW1hcnkgd2lsbCBiZSBlbWFpbGVkIHRvIHRoZSBwcm9kdWN0IG93bmVycyBhdCAxNDowMOKAr1VUQy4gVGhlIHN1bW1hcnkgd2lsbCBoaWdobGlnaHQgcGFzcyByYXRlcywgYW55IGRldmlhdGlvbnMgZnJvbSBleHBlY3RlZCBiZWhhdmlvciwgYW5kIHRoZSByZW1lZGlhdGlvbiB0aW1lbGluZSBmb3IgZWFjaCBvcGVuIGlzc3VlLiAgXG5cblJpc2sgbWl0aWdhdGlvbiBtZWFzdXJlcyBhcmUgaW4gcGxhY2UuIEFsbCB0ZXN0IGRhdGEgaXMgc2FuZGJveGVkLCBwcmV2ZW50aW5nIGNvbnRhbWluYXRpb24gb2YgcHJvZHVjdGlvbiByZWNvcmRzLiBOZXR3b3JrIHRocm90dGxpbmcgc2ltdWxhdGVzIHJlYWzigJF3b3JsZCBsYXRlbmN5LCBhbmQgc2VjdXJpdHkgcHJvYmVzIHJ1biBjb25jdXJyZW50bHkgdG8gdmVyaWZ5IHRoYXQgbm8gbmV3IHZ1bG5lcmFiaWxpdGllcyBoYXZlIGJlZW4gaW50cm9kdWNlZC4gIFxuXG5Mb29raW5nIGFoZWFkLCBvbmNlIHRoZSBhY2NlcHRhbmNlIHByb2JlcyBmaW5pc2gsIHdlIHdpbGwgdHJhbnNpdGlvbiB0byB0aGUgc2lnbuKAkW9mZiBzdGFnZS4gVGhlIHF1YWxpdHkgYXNzdXJhbmNlIGxlYWQgd2lsbCByZXZpZXcgdGhlIGZpbmFsIHJlcG9ydCwgYW5kIHRoZSByZWxlYXNlIG1hbmFnZXIgd2lsbCBzY2hlZHVsZSB0aGUgcHJvZHVjdGlvbiByb2xsb3V0LiBBc3N1bWluZyB0aGUgY3VycmVudCB0cmVuZCBob2xkcywgd2UgYW50aWNpcGF0ZSBhIGNsZWFuIHNpZ27igJFvZmYgYnkgdGhlIGNsb3NlIG9mIGJ1c2luZXNzIHRvbW9ycm93LiAgXG5cbkluIHN1bW1hcnksIHRoZSBhY2NlcHRhbmNlIHRlc3RpbmcgZW5naW5lIGlzIGZ1bGx5IGVuZ2FnZWQsIGRlbGl2ZXJpbmcgcmVhbOKAkXRpbWUgdmFsaWRhdGlvbiBvZiBvdXIgY29yZSBmdW5jdGlvbmFsaXRpZXMuIFByb2dyZXNzIGlzIG9uIHRyYWNrLCB2aXNpYmlsaXR5IGlzIGVuc3VyZWQsIGFuZCBjb250aW5nZW5jeSBwbGFucyBhcmUgcmVhZHkuIFRoZSB0ZWFtIHJlbWFpbnMgZm9jdXNlZCwgYW5kIHRoZSBwcm9qZWN0IGlzIHBvaXNlZCB0byBtb3ZlIGZvcndhcmQgd2l0aG91dCBkZWxheS4iLCJzdGF0dXMiOiJleGVjdXRlZCJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6ZGZiNDQxMmFhNDI5ZDNhYzYzN2EwNTY2OGM0MzViY2M5MGEyNTEzNjNmY2RkNDlmN2I4NWFlNGFiNTViNWJjOSIsImRlY2xhcmVkIjpbInN0YXRlX3dyaXRlIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiemFtYm9fdW5pdmVyc2FsIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=- Timestamp
Bound call context
- Receipt schema
0.4- Tool name
zambo_universal- Tool version
4.0.0- Permission scope
public- Caller type
session- Caller ID
sha256:a4e22960d1b3522a571cba3f9d066f8e40e8aa4a2ec3c9755a66c05d5834c65a- Caller-reported label
- scratch-h4 (caller_reported, not authenticated team ownership)
- 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
- no_upstream_bytes_captured
- Evidence SHA-256
unavailable- Byte length
- unavailable
Neutral Nostr anchor
- Event ID
e190b713abee7382715251961222e05addbe5d6413b2b65e6ba1c82e8d775ce4- 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-30T16:06:57.052Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:b97db7b88c34f2e3c40ec0a0b744069ecff4ee5ed5a86e6b0f50e8a73cdd69b5","receipt_uuid":"3a7f7abf-4262-4c73-a23f-b67965b8318f","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
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. See the Nostr anchor event on a public viewer. The fingerprint is timestamped outside Zambo too.
Embed this receipt
Markdown
[](https://zambo.dev/run/3a7f7abf-4262-4c73-a23f-b67965b8318f?ref=badge)
HTML
<a href="https://zambo.dev/run/3a7f7abf-4262-4c73-a23f-b67965b8318f?ref=badge"><img src="https://zambo.dev/api/receipt/3a7f7abf-4262-4c73-a23f-b67965b8318f/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
84,826 verifiable receipts minted
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.