ナビゲーションにスキップ

Can Read access authenticated pages or private-network addresses?

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 · Capabilities contract

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

Back to Web Search questions.