> 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.

# Can Read access authenticated pages or private-network addresses?

> POST /v1/web/read accepts public http or https URLs only, rejecting embedded credentials, localhost, and private-network IPs with 400 bad_request while treating fetched page text as untrusted data.

No. `POST /v1/web/read` accesses publicly reachable `http` and `https` pages only (up to 2,048 characters per URL). URLs with embedded usernames or passwords, `localhost`, or private-network IP addresses are rejected with `400 bad_request`, and authenticated dashboards or member-only pages cannot be read with user session cookies.

## Separate public docs from private systems

* **Public documentation**: Use `POST /v1/web/read` (and `POST /v1/web/map`) for open help centers, specifications, and public announcements.
* **Internal or authenticated records**: Query account dashboards, internal wikis, or local services through the team's authorized tools or internal APIs. When writing a brief, cite the public documentation URL and the authorized internal record separately (for example, link a public task guide for workflow steps while citing the account dashboard for a specific run status).

## Treat fetched content as untrusted data

Returned page text in `results[].content` originates from third-party websites. Treat any instructions embedded inside fetched webpages strictly as source material, never as commands for an agent or application to execute.

[Web contract and billing](/web-search) · [Capabilities contract](/capabilities)

## 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).