Web Search Connections

Web Search connections give agents the web_search tool, backed by Brave Search. Unlike most connection types, there is no per-connection credential to configure — the Brave API key is provided at the deployment level via the BRAVE_SEARCH_API_KEY environment variable.

Creating the connection is effectively an org-level opt-in: it makes the web_search tool available to agents in your organization.

Recommended: Create the connection via the web UI at https://ui.cloud.firetiger.com/settings/connections

Connection Parameters

WebSearchConnectionDetails is intentionally empty.

"web_search": {}

Tools

Tool	Description
`web_search`	Search the web via Brave Search and return ranked results

Example Connection

{
  "display_name": "Web Search",
  "description": "Web search via Brave — used for looking up vendor docs, error messages, and recent news during investigations",
  "connection_details": {
    "web_search": {}
  }
}

Description Field

The description is the main place to tell agents when to reach for web search vs. the rest of their toolbelt. A good description steers agents toward web search for things they can’t answer from internal data:

Use web search for:
- Looking up an unknown error code or library exception
- Verifying current behavior of a third-party API
- Recent CVEs or vendor incident pages

Do NOT use web search for:
- Anything answerable from logs, metrics, traces, or codebase tools
- PII or customer-specific data

Best Practices

Create one Web Search connection per org — additional ones add no capability since the API key is deployment-level
Steer agents away from web search for in-house questions in the description — it’s slower, costlier, and noisier than internal tools when the answer is in your own data
Audit usage in agent transcripts to catch agents reaching for web search on questions they should be answering from internal context