The deal, in plain English.

What this is

botx402 is operated by Arnhem Labs Pty Ltd (ABN 53 696 663 297), an Australian proprietary limited company, trading as "botx402". "We", "us", and "botx402" in these terms all mean Arnhem Labs Pty Ltd. We run a per-use bot marketplace: each "bot" is a one-shot job — you give it inputs, you pay a fee, you get back a PDF. No accounts, no subscriptions, no auto-renew.

Two ways to pay: (a) the human checkout — Stripe at the price displayed; (b) the agent endpoints — x402 with USDC on Base (clause 04). Both rails buy the same bot run.

These Terms of Service apply to anyone who uses any bot on botx402.io or any subdomain. By clicking "Pay", or by sending a signed x402 authorization to any /api/v1/agent/... endpoint, you agree to them.

Who can use it

You must be at least 18 years old. If you're using a bot for an organisation, you confirm you have authority to bind that organisation to these terms.

You must have rights to the data you connect. If you connect a Xero (or other) account, you confirm you're authorised to do so by whoever owns the books.

Payment

Each run is a one-time charge to your card via Stripe at the price displayed at checkout (currently $19 per RevenueGuard run). We don't store card details — Stripe does.

We don't auto-renew, run subscriptions, or charge you for anything you didn't click "Pay" on. There is no second invoice.

Volume customers can request a manual quote at hello@botx402.io. We'll send a single Stripe invoice for the run count agreed.

If you're an autonomous agent paying with USDC over x402, see clause 04 — that path has slightly different finality and refund mechanics.

Agent users / x402 payments

We expose every bot to autonomous agents via the x402 protocol — HTTP 402 + a signed USDC authorization on Base, settled by a third-party facilitator. Same price as the Stripe path. The agent reads the bot's payment requirements, signs an EIP-3009 authorization, and resends the request with an X-PAYMENT header. No card.

By using the agent endpoints you confirm that (a) you control the wallet that signed the authorization, (b) you have authority to spend its funds, and (c) the data you provide (or connect via OAuth) is yours to use.

Crypto finality: once a payment settles on-chain, it is final. USDC transfers cannot be charged back, reversed by us, or unwound by the network. There is no Visa-style chargeback pathway. If you need that protection, use the Stripe checkout instead.

Settle-on-success: we only ask the facilitator to broadcast your authorization to the chain after we've successfully delivered the report. If a run fails before delivery, we never settle — your signed authorization expires unused (typically within 15 minutes) and your USDC stays in your wallet. This is the rail's automatic failure-mode refund.

Disputed deliveries: if a run did settle and you believe the report is materially defective (customer list wrong, math wrong, file corrupted) you can request a manual outbound USDC refund from our recipient wallet within 7 days of delivery, on the same grounds as clause 05. We process these by hand; allow 1–2 business days. The refund is sent to the wallet that signed the authorization.

Daily spend cap: to keep individual flows below thresholds where US state money-services rules begin to apply, we cap a single caller (a hash of your wallet + user-agent) to $200 USDC per UTC day. Hitting the cap returns 429; your authorization expires harmlessly. Email hello@botx402.io if you have a legitimate use case past this — we'll talk.

Wallet address logging: the wallet that signed the authorization is recorded on the Job for refund and audit purposes. See the Privacy Notice.

Refunds

Our refund policy is run-or-refund, not run-and-refund. If we couldn't deliver a working report, you get your money back. If we delivered the report you asked for, we don't.

We will refund your $19 in full if any of these are genuinely true:

• Our service couldn't generate your PDF (rendering bug, infrastructure outage, anything on our side).

• Your accounting connection (e.g. Xero) couldn't be read during the run — token expired, scope revoked, or no readable invoice data.

• You believe the report is materially defective — the customer list is wrong, the math is wrong, the file is corrupted — and we agree after looking at it.

We will not refund:

• Change of mind. We don't run subscriptions; the same logic applies to single runs. If you bought it, we ran it, and we delivered it — you keep the report and we keep the $19.

• "I don't like the answer." The score is computed from your own paid and authorised invoices. You can argue with the methodology (we'd love that conversation), but the number itself isn't a refund reason.

• Refusal to explain what's wrong. We will ask once what the issue is. If we can't reproduce it and you'd rather not say, we'll politely decline.

How to ask: email refunds@botx402.io within 7 days of the run, with the receipt ID and one sentence on what went wrong. No phone call required.

Stripe-paid runs: refunds are processed back to the original card via Stripe and typically arrive within 5–10 business days.

x402-paid runs: failed runs auto-refund by simply never being settled — your signed authorization expires and your USDC stays put. For settled runs, we send USDC manually from our recipient wallet back to the wallet that signed the authorization. Allow 1–2 business days. Crypto-rail refunds are at our discretion within the 7-day window above; clause 04 has the rail-specific detail.

What you can't do

Don't use a bot for anything fraudulent, illegal, or that infringes someone else's rights.

Don't try to reverse-engineer the bots, scrape our outputs at scale, or impersonate another user.

Don't connect data sources you don't have authority to read.

We can refuse service or refund and close out a run if we reasonably believe one of these has happened.

Your data, your reports

You own the inputs you give us and the PDFs we generate for you. We claim no rights over either.

We may use anonymised, aggregated metadata (e.g. "we ran 14,000 RevenueGuard reports last quarter") for marketing and product improvement. We never share your individual data, customer names, or financial figures.

Data retention details are in the Privacy Notice.

No warranty

The bots are provided "as is" and "as available". We don't warrant that any bot is fit for a particular purpose, that the PDF is free of error, or that the analysis is suitable for any audit, regulatory, or legal use.

RevenueGuard (and every other bot on the site) is a quick-look diagnostic, not professional accounting, financial, legal, or tax advice. If your covenant compliance, audit defence, or board reporting depends on the answer, run it past a licensed professional before acting on it.

Limit on what we owe you

Our total liability to you for anything connected with a bot run, the website, or these terms — added up across every claim — is capped at the amount you paid us for that run. For a single RevenueGuard run, that's $19.

We are not liable to you for any indirect, incidental, consequential, special, exemplary, or punitive damages: that includes lost profits, lost revenue, lost business, lost data, loss of goodwill, or business interruption, even if we knew the damages were possible.

This applies whether the claim is in contract, tort (including negligence), statute, or any other legal theory.

Some jurisdictions don't allow these limits; in those places, the cap is the maximum the law allows.

Indemnity

If someone sues Arnhem Labs Pty Ltd because of how you used a bot — for example, because you connected data you weren't authorised to use, or used a report in a way that broke the law — you'll cover our reasonable defence costs and any damages awarded.

Changes to the terms

We may update these terms. We'll post the new version here with an updated "effective" date. Material changes (refund window, liability cap, etc.) take effect 14 days after we post.

Governing law

These terms are governed by the laws of the State of Queensland, Australia. Arnhem Labs Pty Ltd (ABN 53 696 663 297) is the contracting party. Any dispute that can't be resolved by email goes to the courts of Queensland.

If any clause is held unenforceable, the rest of the terms still apply.

Contact

Refunds: refunds@botx402.io with your receipt ID (Stripe-paid) or wallet address (x402-paid). Everything else (support, volume quotes, agent integration questions, anything): hello@botx402.io. We aim to reply within 1 business day.