Skip to main content
The Web Search setting stores the search provider the agent should use to search the web, with that provider’s API key. You can set one provider at a time, or none. Open it from Settings → Web Search in the AI Studio sidebar. The header reads “Search provider the agent uses to browse the web”.
Agent settings Web Search section with the text Pick the provider the agent searches the web with. With no provider, web search is off, and the options Off (marked Current), Exa, Firecrawl and TinyFish, with a Save button in the header

Settings → Web Search with no provider set

In the current release, saving a provider stores it but no agent tool calls it yet: the agent does not run web searches through Exa, Firecrawl or TinyFish. The agent can still read public pages, such as a CVE record or a vendor advisory, with its page-fetch tool, which does not depend on this setting. It makes a plain HTTP GET to a public URL, refuses private and internal addresses, and returns the first 16 KB of the page.

Providers

Each provider takes only an API key; there are no other fields. The option you saved is marked In use (or Current for Off).

Choose a provider

1

Open Web Search

In AI Studio, open Settings → Web Search.
2

Pick a provider

Select Exa, Firecrawl or TinyFish. A <Provider> API Key field appears below the options.
3

Enter the API key

Paste the key from your account with that provider. The field is required (marked *) for any provider that is not the one in use. For the provider already in use, the field shows the saved key masked; leave it blank to keep it, or paste a new key to replace it.
4

Save

Click Save in the header. The console confirms with “Web search updated”. Discard drops unsaved changes.
Save stays disabled until something changed and, for a provider without a saved key, a key is entered.

Turn web search off

Select Off and click Save. The console confirms with “Web search turned off”.
Only one provider is stored. Switching to another provider, or to Off, deletes the previous provider’s key, so you need to enter it again if you switch back.

How the key is stored

  • The setting is personal: it applies to your own chats in the current workspace. Other members set their own.
  • The API key is encrypted at rest with the workspace’s encryption key and is never shown again in full. The console only shows a masked value ending in the key’s last four characters.
  • Changing the setting requires the agent.write permission. See Permissions.

Chat

Ask mode, Agent mode and what the agent can look up

Connectors

The tools the agent can use in this workspace