For AI agents: a documentation index is available at https://docs.parallel.ai/llms.txt. The full text of all docs is at https://docs.parallel.ai/llms-full.txt. You may also fetch any page as Markdown by appending
This guide helps you migrate from the Beta Search API (.md to its URL or sending Accept: text/markdown./v1beta) to the GA version (/v1).
The V1 Search API is generally available and recommended for all new integrations. This guide explains how to migrate existing Beta integrations to V1’s current modes and request fields.
Highlights
-
search_queriesis now required — At least one non-empty query must be provided. In Beta, only one ofobjectiveorsearch_querieswas required. -
Settings reorganized under
advanced_settings—source_policy,fetch_policy, excerpt settings, andmax_resultsare now nested under a single newadvanced_settingsobject (previously top-level fields). See Advanced Settings for more details. -
New
locationfield — Setadvanced_settings.locationto an ISO 3166-1 alpha-2 country code (e.g.,"us","gb","de","jp") to geo-target search results. Only a subset of countries are currently supported; unsupported or invalid values are ignored with a warning. -
Updated modes — V1 has four modes (
turbo,fast,basic,advanced), withadvancedas the new default. For most use cases, map bothfastandone-shottobasic, and mapagentictoadvanced.turboandfastare new in V1 with no Beta equivalents — V1fastshares a name with Betafastbut is a different, lower-latency mode.basic: The V1 equivalent of Betafastandone-shot. Returns extended snippets per result and works best with 2-3 high-quality search_queries. Reach for it when you want longer excerpts per source in a single call. For most applications, prefer V1fast(see below).advanced(default): The V1 equivalent of Betaagentic. Provides higher quality with more advanced retrieval and compression. Best for complex queries where result quality matters more than latency.turboandfast(new in V1): Lower-latency, lower-cost modes for high-volume and latency-sensitive workloads, with no Beta equivalent.fastdelivers high-quality results in around 700ms and is the recommended default for most agents;turbo(~250ms) is built for real-time, high-volume grounding. See Search Modes.
Overview of Changes
If your integration uses
client.beta.search(), upgrade to the latest parallel-web release and replace it with client.search().
Migration Example
Before (Beta)
cURL
After (V1)
Additional Resources
- Search Quickstart - Get started with the Search API
- Best Practices - Optimize your search requests
- Search MCP - Use Search via Model Context Protocol
- API Reference - Complete parameter specifications