Key Benefits
- Context engineering for token efficiency: The API ranks and compresses web results based on reasoning utility rather than human engagement, delivering the most relevant tokens for each agent’s specific objective.
- Single-hop resolution of complex queries: Where traditional search forces agents to make multiple sequential calls, accumulating latency and costs, Parallel resolves complex multi-topic queries in a single request.
- Multi-hop efficiency: For deep research workflows requiring multiple reasoning steps, agents using Parallel complete tasks in fewer tool calls while achieving higher accuracy and lower end-to-end latency.
Request Fields
Note that at least one ofobjective or search_queries is required. The remaining
fields are optional. See the API
Reference for complete parameter
specifications and constraints.
| Field | Type | Notes | Example |
|---|---|---|---|
| mode | string | Presets for different use cases: one-shot (comprehensive results with longer excerpts for single-response answers) or agentic (concise, token-efficient results for multi-step workflows). Defaults to one-shot. | ”agentic” |
| objective | string | Natural-language description of the web research goal, including source or freshness guidance and broader context from the task. Maximum 5000 characters. | ”I want to know when the UN was founded. Prefer UN’s websites.” |
| search_queries | string[] | Optional search queries to supplement the objective. Maximum 200 characters per query. | [“Founding year UN”, “Year of founding United Nations”] |
| max_results | int | Maximum number of search results to return (1-20). Defaults to 10 if not provided. | 10 |
| source_policy | SourcePolicy | Controls specific domains to include or exclude from search results. Use only when source guidance in the objective is insufficient. | Source policy example |
| excerpts | object | Customize excerpt length. | {"max_chars_per_result": 30000} |
| fetch_policy | object | Controls when to return indexed vs fresh content. Default is to disable live fetch and return cached content from the index. | {"max_age_seconds": 3600} |
Mode: One-Shot vs Agentic
Themode parameter presets defaults for different use cases:
-
one-shot(default): Returns comprehensive results with longer excerpts. Best for direct user queries, where only a single request will be made, or where lower latency is desired. This is the default mode for the Search API. -
agentic: Returns more concise, token-efficient results designed for multi-step agentic workflows. This is the mode used by the Search MCP server, and should be used when the search is part of a larger reasoning loop. Latency may be slightly higher than forone-shotdue to additional processing to increase excerpt relevance.
Objective and Search Queries
For best results, provide bothobjective and search_queries. The objective should include context about your broader task or goal, while search queries ensure specific keywords are prioritized.
When writing objectives, be specific about preferred sources, include freshness requirements when relevant, and specify desired content types (e.g., technical documentation, peer-reviewed research, official announcements).
Examples of effective objectives with search queries: