1. readfetch
  2. terms

Terms of service

The deal, in plain terms

You pay per call in USDC over x402 and get the response. There is no account, no subscription, and no minimum. This page is the whole agreement. Last updated 2026-11-21.

What you are buying

readfetch.com reads a URL you name and returns its content: extracted text, a site map, a rendered page, a document, a search result, a screenshot, or a bounded crawl. Each call is independent. Nothing is stored for you between calls, and there is no state to cancel.

Price and payment

  • The quote is the contractthe price you pay is the one in the 402 response you signed
  • Per callno subscription, no minimum spend, no account balance
  • USDC on Baseone signed authorization settles one on-chain transfer
  • Prices can changea published price change never alters a quote you already signed

Published prices, the current catalogue, and the limits that apply are on the pricing section and in x402-resources.json. Where those disagree with a page describing them, the quote in the 402 response governs the call.

When you are charged

Reading routes settle only when content was delivered. A bot wall, an empty extraction, a validation refusal, a rate limit, or a timeout is not a delivery and is not charged — the response says billed: false. /v1/fetch is the exception by design: it bills when the origin answers, including a 4xx or 5xx, because the bytes you asked for were fetched. It does not bill when the transport itself failed.

/v1/probe is free. So are POST /v1/feedback and GET /v1/crawl/{id}.

If a paid call goes wrong

Every paid call carries a signed RECEIPT. A delivery you consider defective can be submitted to POST /v1/claims with that receipt and a signature from the paying wallet. An auto-approved claim issues a credit token you spend once on a later call. The criteria are in /docs#claims; a claim that is not auto-approved is read by the operator rather than decided by an automated system.

What you may not do with it

  • No unlawful useincluding content you have no right to access
  • No attacksno using the service to flood, scan, or overload a third-party host
  • No credential harvestingdo not submit secrets expecting them to be kept
  • No resale of accessthe egress is not a proxy product; it exists to serve the reading routes

Rate limits, per-address free-tier allowances, and concurrency caps are part of the service, not obstacles to route around. Exceeding them returns 429 with a Retry-After; it does not create a charge.

What stays yours

You are responsible for the URLs you submit and for holding whatever right you need to read them, and for what you do with the text afterwards. The service does not grant you rights in third-party content, does not strip copyright, and does not screen what you ask it to fetch beyond refusing private, loopback, and metadata addresses.

What the service records about your calls, and for how long, is on the privacy page. That page is part of these terms.

No warranty, no SLA

The service is provided as-is. There is no uptime guarantee, no service-level agreement, and no promise that a given page can be read: sites change their defences, and some refuse automated clients no matter what is sent. A call that returns nothing is not charged, which is the remedy, and a repeated failure on a specific target is worth reporting through /v1/feedback.

The operator may change, suspend, or withdraw any endpoint, price, or the service itself. When a change removes something a caller relied on, the response names what to use instead; the catalogue and SKILL.md are the record of what is current.

Limits on liability

To the extent the law allows, the operator is not liable for indirect or consequential loss, lost profit, or lost data arising from use of the service, and total liability for any claim is limited to what was actually paid for the calls that gave rise to it in the thirty days before the claim. Nothing here excludes liability that cannot lawfully be excluded.

Changes to these terms

If these terms change materially, the date at the top changes and the previous version stays in the repository history at github.com/readfetch/readfetch. Continuing to call the service after a change accepts the new terms; a quote you already signed is unaffected.

Questions and notices

Send POST /v1/feedback with the X-Request-Id of the response you are asking about, or open an issue at github.com/readfetch/readfetch. The same two channels take formal notices; a signed claim under /v1/claims is the only route that can move money.