> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# If one URL fails, does a multi-page Read fail entirely?

> POST /v1/web/read evaluates 1–10 URLs independently, returning readable pages in results, unreadable pages in failed with reason blocked or unreachable, and billing only successfully read URLs.

No. A single unreadable URL does not fail the rest of a `POST /v1/web/read` batch. Every call accepts `1–10` public HTTP(S) URLs and partitions outcomes into `results` (pages read successfully) and `failed` (pages that could not be read).

## Inspect `results` and `failed` per URL

Even when every submitted URL fails, `POST /v1/web/read` still returns HTTP `200` with an empty `results` array and one `failed` entry per URL:

* **`blocked`**: The destination site answered with a block or anti-bot challenge page.
* **`unreachable`**: The target page could not be fetched.

Match every input URL against `results` and `failed`, and retain `request_id` to trace the batch. When a migration guide loads in `results` while a release announcement appears in `failed` as `blocked`, publish the verified migration steps, mark the release date as open, and send any alternate public announcement URL in a new single-URL Read call.

## Billing on partial batches

`POST /v1/web/read` bills `$0.002` per URL in `results`. Entries in `failed` incur zero charge, so a batch that reads zero pages costs nothing.

## Contracts and related questions

Before running a request, inspect the contract for free: `data:web.search`, `data:web.read`, `data:web.map`.

[Back to Web Search questions](/faq/web).