POST/v1/batch

Up to 50 URLs in one call and one payment. Results in input order; undelivered pages come back as credit.

$0.0015/page
min 10
partial ok

What it does

One paragraph, no pitch.

Up to 50 URLs in one call and one payment. Results in input order; an undelivered page is not billed and is credited.

Price

Quoted by the 402 before anything runs.

$0.0015/pageper page
95 s default, 95 s maximumwhole-call budget
billedonly when content is delivered
no keythe payment is the credential

x402 settlement is live on eip155:8453: sign a USDC transfer and retry with PAYMENT-SIGNATURE.

When to call it

Cheapest endpoint that answers the question, first.

Call it when the sentence above is the whole job. Its neighbours solve the same URL with a different trade-off — a browser instead of plain HTTP, a site instead of one page, one section instead of a document. /choose walks the decision in thirteen routes, cheapest first, browser last.

Not sure the page is worth paying for at all? /v1/probe is free and returns the status, content type, size, title, language and whether a bot wall is waiting — no body.

Request fields

JSON body. Send this to https://readfetch.com/v1/batch.

Field	Type	Default	What it does
`urls` required	array	—	URLs to read, deduped before quoting.
`egress`	string	—	Egress pool to leave through: `direct` (the default route, no proxy) or any pool the operator configured, e.g. `residential` (the home exit) or `local`. Omit to route by host rules.
`pipeline`	string	text	text = HTTP-first; render needs the browser tier.
`format`	string	markdown
`fresh`	boolean	false
`accept_language`	string	—
`timeout_s`	number	95	Total budget for the whole batch in seconds; every item shares it and no item restarts it.

Make the call

Unpaid, this answers 402 with the quote. Sign accepts[0] and resend with PAYMENT-SIGNATURE.

curl

curl -s https://readfetch.com/v1/batch -H 'content-type: application/json' -d '{"urls":["https://example.com"]}'

json body

{
  "urls": [
    "https://example.com"
  ]
}

Response

Fields shown are the ones a caller branches on.

200 ok

{
  "billed_pages": 1,
  "credit": null,
  "delivered": 1,
  "failed": 0,
  "results": [
    {
      "billed": true,
      "content_sha256": "...",
      "hint": null,
      "requested_url": "https://example.com",
      "status_code": 200,
      "text": "...",
      "title": "Example Domain",
      "url": "https://example.com/",
      "used_browser": false
    }
  ],
  "status": "partial"
}

Limits

Requests are JSON, 1 MiB maximum. Redirects are re-validated at every hop and capped at 5; the final URL is reported. 95 s default, 95 s maximum is the whole-call budget — DNS, connect, redirects, retries and any render share it, and no step starts a fresh clock.

Failures come back as {"error": "…", "hint": "…"} with a status to branch on: 402 for the quote, 429 with Retry-After, 502 and 504 for the upstream. /docs lists the shapes.

Billing

Settled after the work, only when something was delivered.

$0.0015 per delivered page. A response with billed: false settles nothing and names the next call to try.

billed: false means nothing settled: a bot wall, an empty extraction, an unsupported type or a transport failure. The hint on that response names the next call to try.

Every settlement carries a signed RECEIPT bound to the transaction. If a paid call delivered nothing, a claim issues a single-use credit for it — the rail cannot refund.