Skip to main content

​
Overview

Web providers let Omni’s AI assistant and background agents look up public web information live during a chat or agent run. They are optional and configured independently from the Web Connector, which crawls a fixed website into Omni’s internal index.
Configure web providers from Settings → Web Providers. Provider API keys are encrypted at rest using Omni’s normal service-credential encryption.

​
Provider Types

Provider kindSupported providersAgent toolPurpose
SearchExa, Serper, Brave Searchweb_searchSearch the public web and return citation-friendly results
FetchExa, Firecrawlfetch_web_pageFetch readable content from a specific public HTTP(S) URL
You can connect more than one provider of each kind, but only one search provider and one fetch provider are marked Current at a time.

​
Setup

  1. Navigate to Settings → Web Providers
  2. In Search Providers or Fetch Providers, click Connect on the provider you want to use
  3. Enter the provider API key
  4. Optionally set a custom Base URL if you use a proxy or compatible endpoint
  5. Click Connect
  6. If multiple providers are connected for the same kind, click Set current on the provider Omni should use
fetch_web_page is only available when a fetch provider is configured. web_search is available when a search provider is configured.

​
URL Blocklist

The same settings page includes a URL Blocklist for public web fetches. Add one pattern per line: 
example.com
*.example.com
https://example.com/private
PatternBehavior
example.comBlocks exactly that hostname
*.example.comBlocks subdomains such as docs.example.com
https://example.com/privateBlocks URLs starting with that prefix
The fetch tool also rejects localhost URLs and URLs that resolve to private/internal IP addresses.

​
How Agents Use Web Providers

When web providers are configured, the assistant may use:
ToolDescription
web_searchSearches public web results for current or external information not expected to be in Omni’s workplace index
fetch_web_pageFetches readable content from a specific public HTTP(S) URL and treats it as untrusted context
Fetched page content is wrapped as untrusted web content so the model treats it as data, not instructions.

​
Troubleshooting

Check the URL blocklist. Omni also blocks localhost and private/internal network targets to prevent server-side request forgery.
Verify the API key, optional base URL, account quota, and provider status. Remove and reconnect the provider if the key was rotated.

​
Security Considerations

  • Public HTTP(S) only: Fetches must use http:// or https://
  • Network safety: Localhost and private/internal IP ranges are blocked
  • Admin policy: Use the URL blocklist for sensitive domains or URL prefixes
  • Untrusted content: Fetched pages are treated as context only, not instructions
  • Separate from indexing: Live web results are not automatically added to Omni’s search index