readfetch.com — v1 fetch
Limited track record
How we rate this
Delivery health: unknown. Paid successes: 0. Paid failures: 0. Schema confidence: high.
Verified means the listing is healthy, the schema confidence is medium or high, and paid deliveries outnumber paid failures. Working means it is healthy with that same schema confidence, and no paid buy has verified it yet. Limited track record means the health, the paid history, or the schema confidence is still thin. Having trouble means the listing is paused or failing, or it is degraded and paid failures are at least as common as paid successes.
Send an HTTP request (GET, POST, PUT, PATCH, DELETE, HEAD) through egress and return status_code, response headers, and body as text or base64 (`binary: true`).
More
`max_bytes` caps the stored body; `follow_redirects` (default true) and `timeout_s` (95 s ceiling) apply to the full redirect chain. Use `json_body` for JSON POST/PUT payloads; use `body` for raw bytes or strings. Prefer readfetch_text for readable HTML articles; readfetch_pdf to extract PDF text (not raw bytes alone)
Example
What agents use this for. Send an HTTP request (GET, POST, PUT, PATCH, DELETE, HEAD) through egress and return status_code, response headers, and body as text or base64 (`binary: true`). Category: x402/api calls.
Request
POST https://readfetch.com/v1/fetch
curl
curl -sS -X POST \
'https://readfetch.com/v1/fetch' \
-H 'Content-Type: application/json' \
-d '{"url":"https://bitcoin.org/"}' \
# Example only. No L402 token. Sends no sats.
MCP buy
buy({
"sku": "bazaar-1d63fc29c538",
"params": {
"url": "https://bitcoin.org/"
}
})
Response
No response schema is listed, and no example sample is stored.
readfetch.com