Skip to main content
Use phaseo:web_fetch when the model needs to read a known URL, such as a documentation page, article, changelog, or PDF-like text source. The model decides when to fetch, provides the URL, and receives bounded page text back as tool context.

How it works

  1. Add { "type": "phaseo:web_fetch" } to tools.
  2. The model decides whether it needs to fetch a URL.
  3. Phaseo fetches and extracts the content using the configured engine.
  4. The extracted text, title, URL, and truncation metadata are returned to the model.
  5. The model writes the final response and may fetch more URLs if needed.

Quick start

Configuration

Engine selection

Only HTTP(S) URLs are supported. Direct gateway fetch accepts text-like content types and reduces HTML to plain text before returning it to the model.

Native Anthropic fetch

Tool result

Managed fetch returns a JSON tool result with fields such as:
Check truncated before assuming the model received the full page.

Usage and pricing

Web fetch calls increment:
Managed fetch pricing can use server_tool_web_fetch_requests. Provider-native fetch usage can use native_web_fetch_requests where a model price card defines that meter.
Last modified on August 4, 2026