BotDojoDocs
Search BotDojo Docs
Search every guide

Try “stop a run,” “connect an app,” or “daily briefing.”

Browse Integrate
IntegrateAgent Tool IntegrationsAnthropic Web Search
Integrate · Agent Tool Integrations

Anthropic Web Search

Give any agent the Anthropic connection's Web Search tool: Anthropic's web search, with an answer and cited sources.

3 min read

The Anthropic connection includes a Web Search tool. An agent that uses it gets back an answer, the sources it cites, and the searches that ran. The agent can use any model; the search itself runs on a Claude model through the connection's Anthropic API key, in its own model call.

Before You Start

You will need an Anthropic connection, which uses an Anthropic API key from the Anthropic Console. Web search is on for an organization unless an administrator turned it off in the Claude Console; if it is off, every search fails with a message asking you to check that setting.

Anthropic bills the key directly: $10 per 1,000 searches, plus the Claude model's tokens for each request.

Set Up The Anthropic Connection

  1. In BotDojo, open Integrations.
  2. Find Anthropic Claude and click Connect, or open the existing connection.
  3. Paste the Anthropic API key into the Api Key field.
  4. Optionally set Web Search Model to the Claude model that runs the searches. The default is claude-sonnet-5-5. A smaller model such as claude-haiku-5-5 costs less.
  5. Click Connect or Save.

The connection's models keep working as before. Agents only get Web Search when you add the tool to them.

Add Web Search To An Agent

Add the Anthropic connection's Web Search action to the agent, the same way as any other connection tool (for example with an Integration Tool node in the Flow Builder). You can pin any of its inputs on the node, such as allowed_domains, so the agent can't change them.

What The Tool Supports

webSearch takes:

  • query (required, up to 4,000 characters): what to find out. A full question or research request works better than keywords.
  • max_searches (1 to 20, default 5): the most searches Anthropic may run for this request. A long search that Anthropic pauses is resumed, but not after max_searches searches have run, and never more than five times.
  • allowed_domains or blocked_domains (up to 64 hostnames, not both): limit results to, or exclude, sites such as sec.gov.
  • user_location (city, region, a two-letter country, and an IANA timezone such as America/Chicago): for questions that depend on where the user is, such as local news or weather.
  • fetch_pages (default false): also let Anthropic read full pages from the results, for details that search snippets miss.
  • filter_results (default false): let Claude filter results with code before reading them (Claude 4.6 and later models only). This can use fewer tokens on broad searches, but Anthropic then usually returns no cited sources, so sources is often empty. Leave it off when you need sources.

It returns:

  • answer: the model's answer as plain text.
  • sources: the pages the answer cites, each with url, title and the cited passage.
  • searches: each search or page read that ran, with its query or URL, the result titles, URLs and dates, or an error_code when it failed.
  • usage: input and output tokens, and the number of searches and page reads Anthropic billed.

A single search can take from a few seconds to a minute or more, depending on how many searches the model runs.

Use It From An App

Because Web Search is a connection tool, an MCP App artifact can call it too, for its signed-in viewer. Share the app with an authenticated account share, and give viewers access to the connection. Each call is billed to the connection's Anthropic key, so limit how often the app can search.

References