Beta Notice: This API is currently in beta and subject to change. Usage is
limited to 600 requests per minute. For production access or higher capacity, contact
support@parallel.ai.
Key Benefits
The Search API is ideal for LLM workflows, agents and retrieval-augmented tasks that use web information.- Speed: Replace brittle multi-step pipelines with a single API call that reduces latency while improving overall quality.
- Flexibility: Configure the number of results and control excerpt length using tunable parameters.
- Token Efficiency: Returns compressed, structured text from the web that minimizes tokens and eliminates the need for post-processing or additional prompting.
- Quality: Built on a web-scale index with advanced ranking and compression techniques that prioritize relevance, clarity, and source reliability.
- Simple Integration: Drop-in replacement for existing keyword-based workflows—just send your search keywords as is to the API and receive structured results.
Request Fields
Note that at least one ofobjective
or search_queries
is required. The remaining fields are optional.
Field | Type | Notes | Example |
---|---|---|---|
objective | string | Natural-language description of what the web research goal is. Include any source or freshness guidance. | ”I want to know when the UN was founded. Prefer UN’s websites.” |
search_queries | string[] | Optional search queries to guide the search. | [“Founding year UN”, “Year of founding United Nations”] |
processor | enum | Either base or pro | base |
max_results | int | Maximum number of search results | 10 |
max_chars_per_result | int | Maximum characters per search result | 6000 |
source_policy | SourcePolicy | Source policy to use for controlling retrieval sources | See Source policy example |
objective
: limited to 5,000 characters.search_queries
: Maximum number of queries allowed is 5 and each query can have a maximum length of 200 characters.max_results
: Processor defined limits. See processors reference.max_chars_per_result
: Minimum value allowed is 100. Per-result excerpt length greater than 30,000 characters in length are not guaranteed.
Best Practices
- Specify natural language objective over search queries. The
objective
field should contain a clear, natural language description of your research goal. Usesearch_queries
only as optional guidance to supplement the objective. - Be precise about objective and avoid vague terms. Instead of “official announcements,” specify “press releases from company websites” or “SEC filings.” Clear objectives lead to more relevant results.
- Choose processors according to your needs. Use
base
for fast, general queries andpro
for complex research requiring higher quality and freshness. See the processors reference for detailed guidance.