1. readfetch
  2. choose
  3. Core
  4. /v1/scrape/residential

Data · Core

POST/v1/scrape/residential

Scrape through a rotating residential exit, for targets that refuse a datacentre address. Same contract as /v1/scrape, one attempt, priced for the bandwidth.

  • $0.02
  • residential exit
  • hard targets
  • one attempt

What it does

One paragraph, no pitch.

Identical request and response to /v1/scrape, but the render leaves through a rotating residential address instead of the datacentre. For targets that block by IP reputation (DataDome, PerimeterX, Cloudflare, AWS WAF). One attempt, no retries: residential bandwidth is the cost, and four times the scrape price is what it takes to cover it honestly.

Price

Quoted by the 402 before anything runs.

  • $0.02per call
  • whole-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/scrape/residential.

FieldTypeDefaultWhat it does
url requiredstring—
modestringrender
freshbooleanfalse
formatstringmarkdown
auth—
advanced—
options—

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/scrape/residential -H 'content-type: application/json' -d '{"url":"https://example.com"}'
json body
{
  "url": "https://example.com"
}

Response

Fields shown are the ones a caller branches on.

200 ok
{
  "billed": true,
  "cache_status": "miss",
  "markdown": "# Pricing\n\n...",
  "status": "success",
  "status_code": 200,
  "title": "Pricing",
  "url": "https://example.com/pricing"
}

Limits

Requests are JSON, 1 MiB maximum. Redirects are re-validated at every hop and capped at 5; the final URL is reported. 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.02 per delivered call. 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.