Agent Payment Terms

Effective 2026-08-28 · Applies to all paid FlareWatch machine services (compute-unit deposits, per-request x402 payments, and paid endpoints). Machine-readable summary: GET /api/pay/quote.

1. All payments are final — no refunds

Every payment to FlareWatch — USDT0 deposits credited as compute units (CU) and per-request x402 authorizations — is final and non-refundable, without exception. Deposited CU never expire and remain spendable indefinitely, but are not redeemable for currency, not transferable between wallets, and not refundable in any circumstance, including mistaken sends, overpayment, unused balances, or discontinuation of a specific endpoint. Test your integration first: POST /api/pay/verify validates an x402 payload for free without spending, and the minimum deposit is deliberately small.

2. What a payment buys

A payment buys execution of the request it accompanies (x402) or CU credited to the sending wallet (deposits), at the prices published in /api/pay/quote at the time of the request. The sending wallet is the account: deposits from exchanges or contracts you do not control credit a wallet you cannot use. A paid request that returns a server error (5xx) may be retried; we do not otherwise guarantee outcomes, uptime, or latency.

3. Data is provided as-is

Paid responses are analytics derived from public blockchain data and our own infrastructure. They are provided as-is, without warranty of accuracy, completeness, or fitness for any purpose, and are not financial, investment, tax, or legal advice. Signed response envelopes attest that data came from FlareWatch, not that it is correct.

4. Prices and service changes

Published prices may change with at least 30 days notice via the machine-readable surfaces (/api/pay/quote, llms.txt). Already-deposited CU are honored at the CU prices in effect when spent. Endpoints may be added, changed with notice per our API deprecation policy, or discontinued; remaining CU stay spendable on remaining endpoints.

5. Acceptable use

Paid access may not be used to attack, probe, or degrade FlareWatch or third parties, to resell raw responses as a competing service, or in violation of applicable law. We may refuse service to abusive callers; CU balances of wallets engaged in attacks on the payment system itself (e.g. replay or settlement fraud attempts) may be voided. Rate limits apply independently of payment.

6. Settlement semantics

An x402 authorization is consumed when the service is rendered; on-chain settlement may occur later. A valid authorization whose service was delivered is a completed payment regardless of settlement timing. Deposits are recognized from on-chain transfer events after launch of the deposit watcher; transfers predating a wallet's first creditable block are not credited.

7. Liability

To the maximum extent permitted by law, FlareWatch's aggregate liability arising from paid services is limited to the amount paid for the specific request giving rise to the claim. Nothing in these terms creates fiduciary, advisory, or custodial obligations.

Questions: [email protected]. These terms may be updated; the machine-readable policy block in /api/pay/quote always reflects the current version.

FlareWatch FTSO delegation addresses. Flare (chainId 14): 0x973B899Fe1422efDdeBE1d54E9A6487a70966aC5. Songbird (chainId 19): 0xaf4eF2A0Ecf8d914Db6b721D3eb79C46CA612796.