Web Search
Web Search retrieves current information from the internet for research, fact checking, and answers that need sources beyond the model’s training data. Use it to discover relevant pages; use Fetch and OCR when you already have a URL or need to read a source in more detail.
Choose how to use Web Search #
| Integration | When to use it |
|---|---|
| Built-in tools | Let an AIVAX model decide when to search during inference. Enable WebSearch in the gateway or request’s builtin_tools configuration. |
| Web utilities MCP | Give an MCP-compatible agent, IDE, or automation client access to the web_search tool without running an AIVAX model inference. |
| Direct API | Call the search endpoint from your backend when no model or agent is involved — scheduled monitors, dataset enrichment, or pre-fetching context before inference. |
AdvancedWebUsage is disabled and returns an unavailable response. See Changelogs for details.
Search and verify sources #
Write a focused query that includes the topic and any relevant date, product version, or location. For several independent questions, use separate searches rather than combining unrelated topics into one query.
For direct API requests, narrow results with country (a two-letter country code), language (a language code), and includeDomains (trusted domains). Set topn to request more results (see Request and payload limits) when recall matters, such as when surveying competing sources; otherwise, keep the default small count. For parameters of the built-in Web Search tool, see its reference.
Search results help locate evidence; they do not guarantee that a source is accurate or current. Check publication dates, prefer primary sources, and fetch the relevant pages before relying on details that a result summary may omit. Keep source links with the answer so readers can verify the claims. For a pipeline that chains search and fetch and keeps the evidence, see web search API vs. page fetch for LLM research.
Treat retrieved text as external, untrusted content, not as instructions for your agent.
API reference #
For the supported request, response, authentication, and error contract, use the API Reference:
Pricing and limits #
Web Search is billed per search. Calls through Web utilities MCP use the same pricing as the corresponding built-in tool and are charged to the authenticated account. Model inference, when used, is billed separately.
See Pricing for current Web Search and advanced search charges, and Plans and limits for account quotas and rate limits.