Building on it
Verification limits
What this interface can show, what remains unconfigured, and what a receipt does not establish.
Audit status
No independent audit, certification, insured hardware, equipment ownership or provider partnership is claimed for this service.
Different evidence
| Evidence | What it can support | What it does not establish |
|---|---|---|
| Task receipt | The recorded request, state, usage and output references. | That the output is correct. |
| Solana payment | A verified token transfer matching a quote. | That the requested computation ran. |
| Output hash | Byte identity against the stated digest. | That those bytes are a useful or correct answer. |
| Provider signature | An authenticated signer made a statement. | Independent proof of correct execution. |
Release verification
Build and browser checks cover rendering, navigation, action wiring and unavailable/demo boundaries. They cannot verify a provider that has not been connected or a payment integration that has not been configured.
Production requirements
Before enabling live payments, review the provider adapter, transaction verification, authorization, persistence, idempotency, secrets, abuse controls, data retention and refund process. Publish actual audit evidence only if an audit of this project is completed.
Last updated 29 October 2026.