# Assay terms of service

Effective 26 September 2026.

Assay is operated by Cascadian Tech LLC ("we"). Assay sells machine-readable answers over HTTP, paid per call in
USDC on Base (in test USDC with no value while Assay runs on the Base Sepolia test network) through the x402
protocol. By sending a payment to an Assay endpoint you, or the agent acting for you
("you"), agree to these terms.

### 1. What you are buying

Each paid call buys one attempt at an answer from one endpoint, at the price stated in that endpoint's payment
challenge. Section 3 says what happens when an attempt fails.

- **`GET /v1/pools/new`** returns a page of liquidity pools recently created on Base mainnet by a fixed list of
  factory contracts, with facts read from the chain. Each fact carries the block and time it was read. Each flag is
  true, false or unknown, with its evidence. Anything we could not measure is stated in words under `missing`.
- **`POST /v1/verify`** returns the votes of several independent language models on whether the sources you pasted
  support the claim you sent. Each vote comes with any quoted passages, and a mark for whether each quote appears
  verbatim in the named source. There is **no single verdict**. Model reasoning is model-authored text that we do
  not check. We do not fetch URLs. Your claim, sources and questions are sent to these models, hosted by
  Together.ai, to be answered.

### 2. What you are not buying

Answers are data for your own evaluation. They are **not** financial, investment, legal or security advice. They are
not an audit of any token, pool or contract, and not a guarantee that any claim is true or false. Chain data can
change after it is read. Language models can be wrong, and a pasted source can try to steer them.

### 3. Payment

- **The price** is the one in the payment challenge for that call.
- **When payment settles:**
  - `/v1/verify` settles **before** the answer is produced.
  - `/v1/pools/new` settles **after** the answer is ready and before it is returned.
- **Refused requests are not charged.** These are answered before any payment settles:
  - a malformed request;
  - a request over the size limit;
  - an unknown filter;
  - stale data;
  - a service known, before payment, to be unable to answer (the verify panel down, the daily spending limit
    reached, or pool data too old).
- **After settlement:** if `/v1/verify` fails after its payment settled, the response says so and gives the
  transaction as the reference. If every model fails on a `/v1/verify` call after its payment settled, the answer
  shows every model with no vote and states why; the call is still charged.
- **No automatic refunds.** Contact us with the transaction hash at assay@cascadiantech.com.
- **Each payment authorization pays for one call.** Presenting the same authorization again is refused.

### 4. Availability

We provide Assay **as is** and **as available**, without warranties of any kind, express or implied, including
merchantability, fitness for a particular purpose, accuracy and non-infringement. We may change prices, limits,
endpoints or these terms, or suspend the service, at any time. Changes do not apply to calls already paid.

### 5. Limitation of liability

To the fullest extent the law allows, our total liability for any claim arising from Assay or these terms is limited
to the amount you paid for the call that gave rise to the claim. We are not liable for indirect, incidental,
consequential or punitive damages, or for lost profits, lost funds or trading losses, even if we were told they were
possible.

### 6. Your responsibilities

- **Lawful use only:** do not use Assay to break the law.
- **No harm to the service:** do not try to disrupt it, overload it, or get answers without paying.
- **Your sources:** you are responsible for the text you send. Do not send personal data or material you have no
  right to share.

### 7. Records

We keep a hash-chained record of each payment we submit to the payment facilitator, and its outcome: the amount
and the time, and, for a settled payment, the payer address and the transaction. A payment that fails its check
while storage is critically low may go unrecorded.

We also keep a demand log of unpaid requests and of visits to our pages, which holds the path, the query, the user
agent and, for a page visit, the referring URL. We do not store IP addresses or request bodies.

### 8. Law and contact

These terms are governed by the laws of the State of Oregon, USA. Questions, refund requests and notices: assay@cascadiantech.com.