LEGAL
Refund policy
Last updated 7 September 2026 · governed by the laws of JURISDICTION
Every capitalised placeholder below (company name, address, registration number, jurisdiction, retention periods, supervisory authority) must be replaced, and a solicitor in your jurisdiction must review the result. Publishing this as-is is worse than publishing nothing.
The short version
You are only ever charged for a successful response. If a render fails, the payment authorisation is not settled, so no refund is needed — nothing left your wallet.
What is never charged
The following outcomes leave the payment authorisation unused:
- A render that times out before its wait condition is met.
- An upstream failure — the target returned a server error or refused the connection.
- A request blocked by our own policy, for example a denied egress range or a blocked target.
- A request refused for a malformed body, an expired nonce, or a reused authorisation.
- A capacity refusal from a saturated region.
When we do refund
If we charged you for a response that our own fault made unusable — for example a truncated PDF caused by a defect on our side, or a duplicate settlement of the same nonce — we refund the settled amount in USDC to the paying wallet.
Because settlement is on-chain, refunds are sent as a new transaction to the wallet that paid. We cannot reverse the original transaction. Network fees for the refund transaction are ours.
How to ask
Email billing@MY_DOMAINNAME with the receipt identifier from the response (X-Receipt-Id), the transaction reference, and what went wrong. We aim to acknowledge within one business day and to decide within {{REFUND_DECISION_WINDOW}} (suggested: five business days). Refund requests must be made within {{REFUND_WINDOW}} (suggested: 30 days) of the charge.
What we cannot refund
We cannot refund blockchain network fees you paid to submit a transaction, price movements in the value of USDC or any other asset, or charges for successful responses that you simply did not end up using. We also cannot refund charges arising from your own configuration — for example rendering the wrong URL, or a script of yours that failed inside a page we loaded correctly.
Spend caps instead of refunds
The most reliable protection against unexpected spend is a cap, not a refund. The SDK enforces per-request, per-agent and per-day ceilings, and these are also checked server-side against the paying wallet. Set them before you run an agent unattended.
Consumer cancellation rights
If you are a consumer in a jurisdiction with a statutory cooling-off period, you may have a right to cancel a purchase of digital services within {{COOLING_OFF_PERIOD}} (commonly 14 days). Because each request is performed immediately on payment, you are asked to acknowledge that performance begins at once and that the right to cancel is lost for requests already served. Unserved balances, where you hold any, remain refundable.
Taxes
Prices are exclusive of VAT, GST or sales tax unless stated. Where we are required to charge tax, it is added at the applicable rate and shown separately. Tax treatment of refunds follows the rules of {{JURISDICTION_TAX_AUTHORITY}}.
QUESTIONS ABOUT THIS DOCUMENT
Postal enquiries: COMPANY_LEGAL_NAME, REGISTERED_ADDRESS — replace before launch.