Both the Alpha and Beta APIs continue to be supported. Using the Alpha API will result in warnings and no breaking errors in production. We will deprecate the Alpha API in December 2025.
What’s New
-
No more processors - The Beta API removes the
baseandproprocessor selection. The API now automatically optimizes search execution. -
Optional mode parameter - Use
modeto optimize results for your use case:one-shot(default, comprehensive results) oragentic(concise, token-efficient for multi-step workflows). -
Content freshness control - New
fetch_policyparameter lets you control whether to use cached or fresh content. - MCP integration - The Search API is now available through the Parallel Search MCP for seamless integration with AI tools.
- Enhanced SDK support - Full TypeScript and Python SDK support with better developer experience.
Overview of Changes
| Component | Alpha | Beta |
|---|---|---|
| Endpoint | /alpha/search | /v1beta/search |
| Beta Header | Not required | parallel-beta: search-extract-2025-10-10 (required) |
| Processor | processor: "base" or "pro" (required) | Removed |
| Mode | Not available | mode: "one-shot" or "agentic" (optional) |
| Excerpt Config | max_chars_per_result: 1500 | excerpts: { max_chars_per_result: 10000 } |
| Freshness Control | Not available | fetch_policy: { max_age_seconds: 3600 } (optional) |
| SDK Method | N/A | client.beta.search() |
Migration Example
Before (Alpha)
After (Beta)
Additional Resources
- Search Quickstart - Get started with the Beta API
- Best Practices - Optimize your search requests
- Search MCP - Use Search via Model Context Protocol
- API Reference - Complete parameter specifications