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 with varying trade-off profiles for different types of use cases. See Modes for details. Defauls to one-shot. | ”fast” |
| 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 | Upper bound on the number of results to return (1-20). The actual number of results may be fewer depending on query specificity and available sources. Defaults to 10. | 10 |
| source_policy | SourcePolicy | Controls your sources: include/exclude specific domains and optionally set a start date for freshness control via after_date. Use when you want stricter source control than objective text alone. | Source policy example |
| excerpts | object | Customize excerpt length. | {"max_chars_per_result": 10000, "max_chars_total": 50000} |
| 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} |
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: