web_search finds pages, and web_fetch extracts their content as text for the model. Both stay off until a provider is configured under Settings → Web search and an agent enables them.
Supported providers
The list comes from the shipped
web-search-catalog.yaml. Self-hosted deployments can override the catalog.
Configure a provider
- Open Settings → Web search and choose the Parallel preset.
- Paste your Parallel API key and save.
Turn web search on for the tenant
Settings → Web search → Allow web search is the tenant-wide switch, and it is on by default. While it is off, new chats and agents cannot enable web search; chats that already use it keep it. In TrueFoundry mode this switch is per tenant.Enable web search on an agent
Once a provider is configured, the UI turns the toggle on for new agents. Agents created through the API keep the schema default,
{ "enabled": false }, until you set the field.
Until a provider is configured, the composer’s Web search row stays disabled.
What the agent gets
web_searchtakes up to 5 keyword queries per call plus an optional objective, and returns ranked hits with titles, URLs, and snippets. Search operators such assite:andfiletype:may work when the provider supports them.web_fetchextracts up to 5 URLs as markdown or text, without a summarization step.
Search through MCP instead
An MCP server with search tools works as well, and the Quickstart connects Exa that way. The built-in tools are independent of MCP: every agent withconfig.web_search.enabled gets them, with no per-tool selection.
Manage the provider through the API
GET /api/v1/settings/web-search-providersreads the provider, with the key redacted.PUT /api/v1/settings/web-search-providerscreates, replaces, or rotates the key.GET /api/v1/catalogs/web-search-providerslists the presets.PATCH /api/v1/settings/configurationwith{ "manifest": { "web_search": { "enabled": true } } }turns web search on for the tenant.GET /api/v1/capabilitiesreports whether web search is available.