Skip to main content
Use phaseo:web_search when the model needs current or source-backed information. The model decides when to search, writes the query, and can search multiple times in one request. Phaseo returns URLs, titles, snippets, highlights, and optional page text to the model so it can write a grounded response.
Google native web search is not enabled in Phaseo server tools yet. Use managed search or provider-native search on supported OpenAI and Anthropic routes.

How it works

  1. Add { "type": "phaseo:web_search" } to tools.
  2. The model decides whether it needs a search and emits a query.
  3. Phaseo executes the search using the configured engine.
  4. Results are returned to the model as tool context.
  5. The model writes the final response and may search again if needed.

Quick start

Configuration

Engine selection

Use engine: "native" only in the tool declaration. If a model tries to pass engine: "native" inside an already-emitted gateway search call, Phaseo returns a tool error because native tools must be selected before the upstream request is sent.

Domain filtering

Use allowed_domains when the answer must come from a controlled source set:
Use excluded_domains when broad web search is allowed but specific domains should be removed from the result set. Perplexity and Firecrawl accept either allowed_domains or excluded_domains in a single search call, not both. Perplexity accepts up to 20 domain filters per request and maps excluded domains to its denylist format.

Responses API

The same tool shape works with /v1/responses:

Usage and pricing

Web search calls increment:
Managed search pricing can use server_tool_web_search_requests and server_tool_web_search_extra_results. Provider-native search usage can use native_web_search_requests where a model price card defines that meter.
Last modified on August 4, 2026