Beta Notice: This API is currently in beta and subject to change, and
requires the
parallel-beta: search-extract-2025-10-10 header. Usage is
limited to 600 requests per minute; for production access or higher capacity, contact
support@parallel.ai.Key Benefits
Ideal for LLM workflows, agents, and retrieval-augmented tasks that use web content.- Search with Natural Language: Describe what you’re looking for in plain language and handle complex, multi-faceted queries in a single request—no need for multiple overlapping keyword searches.
- Intelligent Token Efficiency: Automatically include only the tokens necessary for the task at hand. Simple factual queries return concise excerpts; complex research objectives return comprehensive content. No wasted tokens on irrelevant information.
- Speed: Reduce latency and improve quality by replacing multi-step pipelines with fewer, smarter API calls.
- Quality: Powered by Parallel’s web-scale index with advanced ranking that prioritizes relevance, clarity, and source reliability.
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 |
|---|---|---|---|
| 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). | 10 |
| max_chars_per_result | int | Maximum characters per search result (100-~30,000). | 6000 |
| 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 |
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: