Perplexity Sonar API vs SerpApi
Perplexity Sonar API wins · 17–10 (16 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnDirect probe evidence confirms llms.txt is live (HTTP 200) with an index pointing to agent-oriented docs, plus .md variants of docs pages and an OpenAPI spec are all directly fetchable, exactly matching the agent-consumable docs pattern; docs also explicitly reference agents/coding agents consuming these resources. Missing for 10: no independent third-party report of an agent actually successfully using llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.perplexity.ai/llms.txt # Perplexity > Perplexity API documentation for building with the Agent API…”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.perplexity.ai/docs/getting-started/overview.md > ## Documentation Index > Fetch the complete documen…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
- [claimed-docs] “Install and use Perplexity's pplx command-line interface for web search and query-relevant page snippets from your terminal or coding agent.”
Probe confirms llms.txt exists at serpapi.com/llms.txt (HTTP 200) and per-page markdown docs (.md suffix) are available, plus explicit docs pages describing markdown output optimized for LLMs/agents and MCP integration. missing for 10: no independent/community confirmation of an agent actually consuming llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
- [probe] “PROBE docs-md: HTTP 200 at https://serpapi.com/search-api.md --- title: "Google Search Engine Results API" description: "Scrape Google searc…”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
- [claimed-docs] “Install the library for your language and use your API key to start searching”
- [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
- [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnSonar API is fundamentally a REST/API product with official Python SDK (sync and async clients, httpx/aiohttp), CLI tool returning JSON for shell pipelines/agent tool calls, retries/error handling, and an OpenAPI spec — all directly enabling headless/CI automation. Docs explicitly call out CLI output as 'ready for shell pipelines and agent tool calls, with no code to write.' Missing for 10: no explicit CI/CD pipeline examples (e.g. GitHub Actions) or independent third-party report of running it in CI.
- [claimed-docs] “You can now run Perplexity Search straight from your terminal. The Perplexity CLI returns the same ranked results as JSON, ready for shell p…”
- [claimed-docs] “Install and use Perplexity's pplx command-line interface for web search and query-relevant page snippets from your terminal or coding agent.”
- [github] “We provide support for streaming responses using Server Side Events (SSE).”
- [github] “Certain errors are automatically retried 2 times by default, with a short exponential backoff.”
- [github] “By default, the async client uses `httpx` for HTTP requests. However, for improved concurrency performance you may also use `aiohttp` as the…”
- [github] “The library includes type definitions for all request params and response fields, and offers both synchronous and asynchronous clients power…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
SerpApi is a pure REST API with API-key auth and official SDKs (Python, etc.) enabling non-interactive scripted calls with no browser/UI, suitable for CI/automation; docs also show an async submission mode for background/batch jobs. Missing for 10: explicit CI/CD pipeline examples (e.g., GitHub Actions workflow) or dedicated docs describing running in CI.
- [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
- [claimed-docs] “Parameter defines the way you want to submit your search to SerpApi. It can be set to `false` (default) to open an HTTP connection and keep …”
- [github] “SerpApi provides a script builder to get you started quickly.”
- [claimed-docs] “Install the library for your language and use your API key to start searching”
- [probe] “PROBE docs-md: HTTP 200 at https://serpapi.com/search-api.md --- title: "Google Search Engine Results API" description: "Scrape Google searc…”
ai-native userConnect an agent via an official MCP server
weight 3 · round to Perplexity Sonar APIPerplexity Sonar API is not itself an agent but a service/API, so this axis applies; docs clearly document an official MCP server, both a Perplexity-hosted remote endpoint (api.perplexity.ai/mcp) and a local stdio server, plus tool-restriction configuration, allowing agents to connect via MCP. Missing for 10: independent/hands-on third-party confirmation of the MCP server working in practice beyond first-party docs.
- [claimed-docs] “The Perplexity MCP Server enables AI assistants to access Perplexity's powerful search and reasoning capabilities directly within their work…”
- [claimed-docs] “Remote MCP server (recommended): hosted by Perplexity at `https://api.perplexity.ai/mcp`. No installation, nothing to update, works with any…”
- [claimed-docs] “Local MCP server: run the open-source server on your machine over stdio. Use this if your client only supports stdio servers or you need to …”
- [claimed-docs] “To restrict which tools the model can call, disable tools by default and enable the ones you want”
- [probe] “official MCP server documented at https://docs.perplexity.ai/docs/getting-started/integrations/mcp-server”
SerpApi documents an official MCP integration letting MCP-compatible agents (Claude, ChatGPT, Cursor) use it as a web search tool, and a dedicated serpapi-mcp GitHub repo confirms a first-party MCP server implementation. Missing for 10: independent/hands-on community corroboration of the MCP server working in practice, and detailed setup/config docs beyond the brief integration blurb.
- [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
- [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
- [claimed-docs] “Install the library for your language and use your API key to start searching”
ai-native userUse an official CLI
weight 2 · round to Perplexity Sonar APIPerplexity documents an official 'pplx' CLI for search from the terminal or coding agent, explicitly designed for shell pipelines and agent tool calls (JSON output, no code required), which directly matches the ai-native/agentic story. Missing for 10: independent hands-on verification/community corroboration of the CLI beyond first-party docs, and more detail on install/distribution channels.
- [claimed-docs] “You can now run Perplexity Search straight from your terminal. The Perplexity CLI returns the same ranked results as JSON, ready for shell p…”
- [claimed-docs] “You can now run Perplexity Search straight from your terminal. The [Perplexity CLI](/docs/cli/overview) returns the same ranked results as J…”
- [claimed-docs] “Install and use Perplexity's pplx command-line interface for web search and query-relevant page snippets from your terminal or coding agent.”
ai-native userDrive the product through a documented public API
weight 3 · round to Perplexity Sonar APIPerplexity Sonar API is extensively documented as a public API with OpenAPI spec, official SDKs (Python etc.), CLI, quickstart guides, and API reference for the Sonar/Search/Agent endpoints, confirmed by a live openapi.json probe and multiple docs. This directly matches the ai-native/agenticness story of driving the product through a documented public API. Missing for 10: independent third-party developer testimonials beyond one skeptical HN comment about model selection, which doesn't contradict API existence.
- [claimed-docs] “Get web-grounded answers with built-in citations in one call, or access third-party models from OpenAI, Anthropic, Google, and xAI with web …”
- [claimed-docs] “Install one of our official SDKs for a convenient, type-safe integration”
- [claimed-docs] “You can now run Perplexity Search straight from your terminal. The Perplexity CLI returns the same ranked results as JSON, ready for shell p…”
- [claimed-docs] “Generate an API key and make your first call in < 3 minutes.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
- [github] “The library includes type definitions for all request params and response fields, and offers both synchronous and asynchronous clients power…”
- [claimed-docs] “"citations": [ "<string>" ], "search_results": [”
SerpApi is fundamentally an API product with extensive documented endpoints (Search, News, Ads, Flights, etc.), official client libraries in multiple languages, markdown/JSON output modes for LLM consumption, llms.txt and .md doc endpoints for AI agents, and an official MCP server, all confirmed by live probes and docs. missing for 10: no discoverable OpenAPI/Swagger spec (probe found 404s across candidate paths), and independent hands-on confirmation is limited to community commentary rather than a full third-party integration review.
- [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
- [claimed-docs] “Install the library for your language and use your API key to start searching”
- [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
- [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
- [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
- [probe] “PROBE docs-md: HTTP 200 at https://serpapi.com/search-api.md --- title: "Google Search Engine Results API" description: "Scrape Google searc…”
- [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
- [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnPerplexity Sonar APInone0/10The evidence covers API key generation, rate-limit tiers, and tool-restriction for MCP servers, but there is no mention of scoped or least-privilege API credentials (e.g., per-key permissions, role-based scopes, restricted key creation for sub-agents). Nothing in the docs describes issuing narrowly-scoped keys for delegated agent use.
SerpApinone0/10Evidence shows only a single API key mechanism (used directly in requests) with no mention of scoped, role-based, or least-privilege sub-keys/tokens for agents; community feedback even flags that embedding the secret key in the URL complicates secret management, suggesting no finer-grained credentialing exists.
- [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
- [community] “Embedding the API key (secret) in the URL complicates secret management. Please move that to a header and allow setting via env var.”
ai-native userBuild against official SDKs
weight 2 · round to Perplexity Sonar APIDocs explicitly point to official, type-safe SDKs (perplexity-sonar-docs-7/12), and there's a real Python SDK repo on GitHub with streaming, async/sync clients, typed responses, retries, and error handling (perplexity-sonar-gh-1 through gh-6), corroborating first-party claims with hands-on package evidence. Missing for 10: explicit confirmation of SDKs in multiple other languages (e.g., JS/TS, Go) beyond Python, and independent community usage reports of the SDKs themselves.
- [claimed-docs] “Install one of our official SDKs for a convenient, type-safe integration”
- [claimed-docs] “Install one of our [official SDKs](/docs/sdk/overview) for a convenient, type-safe integration”
- [github] “We provide support for streaming responses using Server Side Events (SSE).”
- [github] “Certain errors are automatically retried 2 times by default, with a short exponential backoff.”
- [github] “When the API returns a non-success status code (that is, 4xx or 5xx response), a subclass of `perplexity.APIStatusError` is raised, containi…”
- [github] “By default, the async client uses `httpx` for HTTP requests. However, for improved concurrency performance you may also use `aiohttp` as the…”
- [github] “The library includes type definitions for all request params and response fields, and offers both synchronous and asynchronous clients power…”
- [github] “search = client.search.create(query="latest AI developments 2024", max_results=5)”
SerpApi ships official SDKs (e.g., the Python client, with docs pointing to installing 'the library for your language') and explicitly supports AI-native workflows via LLM-optimized markdown output and an official MCP server for AI agents. The one caveat is that the flagship Python package is being deprecated in favor of a newer implementation, showing SDK churn. missing for 10: independent/hands-on validation of SDK quality across multiple languages, and clarity on the full breadth of language coverage beyond Python.
- [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
- [github] “This package will soon be **deprecated** in favor of [serpapi-python](https://github.com/serpapi/serpapi-python). We recommend migrating to …”
- [github] “This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
- [claimed-docs] “Install the library for your language and use your API key to start searching”
- [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
- [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnPerplexity Sonar APInone0/10No evidence of any webhook/event subscription mechanism in the Sonar API docs; the product offers request/response APIs, SDKs, CLI, and MCP integration but nothing about outbound event notifications or webhooks.
SerpApinone0/10The evidence shows async search submission and a Searches Archive API for polling results, but no mention anywhere of webhook subscriptions or event push notifications. Missing for 10: any documented webhook endpoint, event subscription mechanism, or push-notification callback feature.
- [claimed-docs] “Parameter defines the way you want to submit your search to SerpApi. It can be set to `false` (default) to open an HTTP connection and keep …”
- [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to Perplexity Sonar APISonar API provides building blocks (embeddings for RAG, Agent API with sandbox/code execution, structured output, web search tools) that a developer could use to build AI-generated insights over their own data, but it is a raw API/platform, not an end-user product with built-in ingestion or dashboard-style insight generation from 'my data'. missing for 10: native data-ingestion/connectors for a user's own datasets, a first-party UI or workflow that surfaces proactive insights/suggestions from stored user data, and independent evidence of this being used end-to-end for such insights.
- [claimed-docs] “Generate high-quality embeddings for semantic search and RAG pipelines.”
- [claimed-docs] “Built-in tools | Perplexity-hosted capabilities: web search, URL fetch, people and finance search, and a code sandbox. Enable each by `type`…”
- [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer — for results that must be …”
- [claimed-docs] “Structured output makes the model return JSON that conforms to a schema you define, so you can deserialize it directly.”
- [claimed-docs] “Use the Search API when you need raw results for your own processing. For an LLM-generated answer with citations, use the Agent API.”
SerpApinone0/10SerpApi's evidence shows it as a raw search-data API/scraper with use-case pages suggesting users feed results into external AI/RAG pipelines, but there's no evidence the product itself generates AI insights or suggestions from a user's own data inside a dashboard or interface. The AI-SEO/GEO use case describes monitoring brand visibility manually, not built-in AI-generated insights.
- [claimed-docs] “Find out how your content is being used in AI-generated answers on Google AI Mode. Monitor your brand's visibility and optimize your SEO str…”
- [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnPerplexity Sonar APInone0/10The evidence describes building agents via the Agent API (tools, sandbox, model fallback, profiles, multi-turn context) but nothing about scheduling, triggers, or autonomous background execution without a caller invoking the API — it's a request/response API, not a background-automation runtime.
SerpApinone0/10SerpApi offers an async request mode (submit now, retrieve later) and account-level 'Automatic Early Renewal', but there is no evidence of a scheduling/cron engine, webhooks, or any mechanism for users to configure recurring searches that run autonomously in the background without manual polling. missing for 10: scheduled/recurring search jobs, webhook/callback delivery, any 'automation' or monitoring dashboard for background runs.
- [claimed-docs] “Parameter defines the way you want to submit your search to SerpApi. It can be set to `false` (default) to open an HTTP connection and keep …”
- [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”
- [claimed-docs] “You can set your plan to Automatic Early Renewal. It will trigger an early renewal once you've used all your searches.”
ai-native userOperate the product with natural-language commands
weight 2 · round to Perplexity Sonar APIThe Agent API is explicitly designed around natural-language 'instructions' and 'input' fields, presets, and MCP integration so AI assistants and agents can drive the product purely via NL commands rather than rigid code paths, and the CLI/MCP server extend this to terminal and agent-tool contexts. missing for 10: independent or hands-on third-party verification that NL-driven agent behavior works reliably in practice, and no evidence of a conversational end-user interface beyond API/CLI/MCP docs.
- [claimed-docs] “A `preset` gives you a working agent in one field.”
- [claimed-docs] “`instructions` is the agent's **system prompt** — the rules that hold on every turn. `input` is the specific thing to do this turn.”
- [claimed-docs] “Built-in tools | Perplexity-hosted capabilities: web search, URL fetch, people and finance search, and a code sandbox. Enable each by `type`…”
- [claimed-docs] “Remote MCP server (recommended): hosted by Perplexity at `https://api.perplexity.ai/mcp`. No installation, nothing to update, works with any…”
- [claimed-docs] “Local MCP server: run the open-source server on your machine over stdio. Use this if your client only supports stdio servers or you need to …”
- [claimed-docs] “Install and use Perplexity's pplx command-line interface for web search and query-relevant page snippets from your terminal or coding agent.”
SerpApi itself is a structured JSON API driven by explicit parameters (q, location, engine, etc.), not a natural-language command console, but its documented MCP server integration lets MCP-compatible AI agents (Claude, ChatGPT, Cursor) invoke it as a tool, effectively letting an AI-native user issue natural-language requests that the agent translates into SerpApi calls. Missing for 10: no first-party natural-language CLI/chat interface for the API itself, and no independent hands-on evidence of the MCP server's real-world reliability.
- [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
- [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
- [claimed-docs] “You can use anything that you would use in a regular Google search. e.g. `inurl:`, `site:`, `intitle:`.”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to Perplexity Sonar APIDocs include an OpenAPI spec (probe-3) and an interactive Playground where users can try the Search API without an API key (docs-14), plus a full API reference page (docs-23) — strong signals of an interactive reference experience. However, there's no explicit confirmation that the API reference pages themselves embed runnable/executable code examples (vs. just a separate Playground and static code snippets). Missing for 10: direct evidence of in-reference 'try it' runnable code blocks, independent user confirmation of the interactive reference experience.
- [claimed-docs] “You can also [try Perplexity Search in the interactive Playground](https://console.perplexity.ai/project/playground/search) with no API key …”
- [claimed-docs] “"citations": [ "<string>" ], "search_results": [”
- [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.perplexity.ai/docs/getting-started/overview.md > ## Documentation Index > Fetch the complete documen…”
SerpApi has extensive documentation pages with parameter descriptions and code snippets (e.g., Python examples, script builder mentioned in serpapi-gh-7) and markdown-formatted docs for LLMs, but there is no evidence of an interactive, runnable API reference (e.g., a live 'try it' console or Swagger/OpenAPI explorer) — the openapi probe returned 404s across all candidate paths. missing for 10: an interactive in-browser API console/playground with runnable requests, an OpenAPI/Swagger spec, and independent confirmation that examples can be executed directly from the docs.
- [github] “SerpApi provides a script builder to get you started quickly.”
- [claimed-docs] “Install the library for your language and use your API key to start searching”
- [probe] “PROBE docs-md: HTTP 200 at https://serpapi.com/search-api.md --- title: "Google Search Engine Results API" description: "Scrape Google searc…”
- [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to Perplexity Sonar APIA probe confirms a machine-readable OpenAPI spec is live at https://docs.perplexity.ai/openapi.json (HTTP 200, contains 'openapi' key), directly satisfying the story, and this is corroborated by an llms.txt documentation index also returning 200. Missing for 10: independent/community confirmation of the OpenAPI spec's completeness or usage beyond the first-party probe.
- [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.perplexity.ai/llms.txt # Perplexity > Perplexity API documentation for building with the Agent API…”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.perplexity.ai/docs/getting-started/overview.md > ## Documentation Index > Fetch the complete documen…”
SerpApinone0/10SerpApi provides docs in markdown (.md) and an llms.txt file for LLM consumption, but a direct probe for standard OpenAPI/Swagger spec locations (openapi.json, swagger.json, etc.) returned 404 on all candidates, and no other evidence pack item references a downloadable OpenAPI/Swagger spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
- [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
- [probe] “PROBE docs-md: HTTP 200 at https://serpapi.com/search-api.md --- title: "Google Search Engine Results API" description: "Scrape Google searc…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnPerplexity Sonar APInone0/10No evidence of any sandbox environment, test mode, or isolated non-production data access for Sonar API—only production API docs, SDKs, MCP server, pricing tiers, and an interactive Playground (which uses live web search, not isolated test data) are mentioned.
SerpApinone0/10SerpApi is a live search-scraping API with a free tier, caching, and 'ZeroTrace Mode' for not storing data, but there is no evidence of a distinct sandbox/test environment separate from production data — all searches appear to hit live Google/Bing/etc. results against the same API key and billing. Missing for 10: any documented sandbox mode, test API keys, mock/staging endpoint, or explicit separation between test and production data.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnPerplexity Sonar APInone0/10The evidence pack shows extensive API documentation, SDKs, an OpenAPI spec, and product features, but nowhere mentions API versioning scheme, a deprecation policy, model sunset timelines, or changelog practices. A community comment even notes model selection 'regressed' over time with no policy context given. No evidence supports this specific axis.
SerpApinone0/10Evidence shows a client library (google-search-results-python) being deprecated in favor of a newer package, but there is no documentation of API versioning (e.g., v1/v2 endpoints) or a formal deprecation policy for the SerpApi service/API itself; an OpenAPI spec probe returned 404s. This is an applicable axis for an API product, but no evidence supports it being delivered.
- [github] “This package will soon be **deprecated** in favor of [serpapi-python](https://github.com/serpapi/serpapi-python). We recommend migrating to …”
- [github] “We recommend migrating to the newer implementation to ensure continued support and access to the latest features and improvements.”
- [github] “This package will soon be deprecated in favor of serpapi-python. We recommend migrating to the newer implementation to ensure continued supp…”
- [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to Perplexity Sonar APIThe Search API mentions 'multi-query search' (perplexity-sonar-docs-17), which hints at handling multiple queries in one call, but there's no explicit batch/bulk endpoint, no documentation of processing many items (e.g., a list of URLs, files, or embeddings) in a single request, and no examples of bulk automation workflows. Missing for 10: dedicated batch/bulk API endpoint, explicit bulk-item processing docs, and evidence of large-scale bulk usage patterns.
- [claimed-docs] “Access real-time web search results with Perplexity's Search API. Get ranked results, domain filtering, multi-query search, and content extr…”
- [claimed-docs] “Search context determines how much web information is retrieved. Higher context = more comprehensive results.”
- [claimed-docs] “As you spend more on API credits over time, you automatically advance to higher tiers with increased rate limits.”
SerpApinone0/10The evidence pack covers single-search parameters, formats, caching, and archive retrieval, but nothing indicates a bulk/batch API endpoint for submitting or processing many search items at once. Bulk operations are a plausible feature for a search-API product, but no documentation or examples confirm this capability exists.
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnPerplexity Sonar APInone0/10No evidence in the pack mentions any scheduling, cron, recurring job, or workflow automation trigger feature for Sonar/Agent API; the docs cover search, agents, tools, MCP, routing, and SDKs but nothing about persisting or scheduling recurring runs.
SerpApinone0/10No evidence of any scheduling, cron-like, or recurring job/workflow feature in SerpApi's docs or integrations—only ad-hoc synchronous/async single searches and a temporary results cache/archive API are documented.
- [claimed-docs] “Parameter defines the way you want to submit your search to SerpApi. It can be set to `false` (default) to open an HTTP connection and keep …”
- [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”
- [github] “The search results are stored in a temporary cache. The previous search can be retrieved from the cache for free.”
Citations trust — stories about citations trust in this arenaCitations trust
Stories about citations trust in this arena
Citation fidelity
developerRely on results carrying canonical URLs, titles, and published dates so my app can cite sources accurately
weight 3 · round to Perplexity Sonar APIDocs confirm the API returns a `citations` array and a `search_results` object alongside answers, and the Search API returns 'ranked results' with content extraction, implying source metadata is present. However, the evidence pack never explicitly confirms canonical URL, title, and published-date fields in the schema (the API reference snippet is truncated before showing field names), so accuracy/completeness of that metadata for citation purposes is unverified. missing for 10: explicit schema documentation of title/url/date fields per search result, independent confirmation that returned URLs/dates are accurate and stable for citation.
- [claimed-docs] “"citations": [ "<string>" ], "search_results": [”
- [claimed-docs] “Access real-time web search results with Perplexity's Search API. Get ranked results, domain filtering, multi-query search, and content extr…”
- [claimed-docs] “Use the Search API when you need raw results for your own processing. For an LLM-generated answer with citations, use the Agent API.”
SerpApinone0/10The evidence pack describes SerpApi's general search/JSON output, formats, and MCP integration, but never documents the structure of returned result fields (e.g., canonical URL, title, published date) that a developer would rely on for citations. Missing for 10: explicit schema documentation of link/title/date fields, examples showing these fields populated, or independent verification of their accuracy/canonicality.
- [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
- [claimed-docs] “Our Google News API allows you to scrape results from the Google News search page.”
- [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
data engineerRead a documented stance on robots.txt, content licensing, and permitted use of results
weight 2 · round to SerpApiPerplexity Sonar APInone0/10No evidence in the pack addresses robots.txt handling, content licensing terms, or a documented policy on permitted use of search results — only general API/product docs, SDK, and pricing information are present.
SerpApi publishes a clear stance on legality of scraping/parsing via its 'U.S. Legal Shield' (covering use of data as long as it's not illegal, with $2M coverage on Production plans), and community discussion corroborates this legal defense framing. However, there is no explicit documented stance on robots.txt compliance or content licensing/copyright of scraped results—only the broad legality/permitted-use angle is covered. Missing for 10: explicit robots.txt policy statement, explicit content-licensing/copyright guidance, independent verification of legal shield's real-world enforceability.
- [claimed-docs] “Our U.S. Legal Shield covers the scraping and parsing of search engine data, as long as your use of the data or service is not illegal.”
- [claimed-docs] “Included with the Production Plan and above, with up to $2 million in coverage.”
- [community] “I used Serp via API many moons ago. The most interesting part of the company imo is their legal defense of different plans... 'Our U.S. Lega…”
- [community] “I'm not sure of the legality but I definitely appreciate their product. From what I see SerpApi is really just providing a machine interface…”
Content extraction — stories about content extraction in this arenaContent extraction
Stories about content extraction in this arena
Ai consumption
ai-native userHave an agent run a multi-step research flow — search, extract contents, and synthesize — through one API
weight 2 · round to Perplexity Sonar APIThe Agent API supports building agents with built-in tools (web search, URL fetch, code sandbox), multi-step reasoning via Pro Search, structured output synthesis, and multi-turn context retention — covering search, extraction, and synthesis in one API call chain. missing for 10: independent/hands-on third-party validation of a full multi-step research flow end-to-end, and quantitative benchmarks on extraction fidelity.
- [claimed-docs] “Pro Search enhances Sonar Pro with automated tool usage and multi-step reasoning. When enabled, the model can perform multiple web searches …”
- [claimed-docs] “Built-in tools | Perplexity-hosted capabilities: web search, URL fetch, people and finance search, and a code sandbox. Enable each by `type`…”
- [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer — for results that must be …”
- [claimed-docs] “Structured output makes the model return JSON that conforms to a schema you define, so you can deserialize it directly.”
- [claimed-docs] “For most multi-turn conversations, use `previous_response_id` to continue from a completed prior response without resending the conversation…”
- [claimed-docs] “A `preset` gives you a working agent in one field.”
- [claimed-docs] “Use the Search API when you need raw results for your own processing. For an LLM-generated answer with citations, use the Agent API.”
SerpApi provides search results (JSON/markdown) and an MCP integration so agents can call it as a search tool, plus RAG use-case docs showing search data feeding into AI pipelines, but it is fundamentally a single-purpose search-scraping API — it does not itself perform multi-step 'extract full page contents' or 'synthesize' steps within one API call; those would need to be orchestrated by the agent/other tools. missing for 10: evidence of a single API call or endpoint that chains search + full-content extraction + synthesis, native content-extraction (beyond search snippets) capability, and independent hands-on proof of a full multi-step research flow working end-to-end.
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
- [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
- [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”
- [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
- [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
Page contents
developerRetrieve full page text or markdown for results, not just snippets
weight 3 · round to SerpApiDocs mention the Search API offers "content extraction for developers" alongside ranked results and snippets (perplexity-sonar-docs-17), suggesting more than snippet-level text is retrievable, but the CLI docs explicitly describe only "query-relevant page snippets" (perplexity-sonar-docs-24) and no doc confirms full-page or markdown output format, schema, or size limits. Missing for 10: explicit API field/response example returning full page text or markdown, documentation of extraction depth/limits, and independent confirmation that returned content is full-page rather than truncated snippets.
- [claimed-docs] “Access real-time web search results with Perplexity's Search API. Get ranked results, domain filtering, multi-query search, and content extr…”
- [claimed-docs] “Install and use Perplexity's pplx command-line interface for web search and query-relevant page snippets from your terminal or coding agent.”
- [claimed-docs] “Use the Search API when you need raw results for your own processing. For an LLM-generated answer with citations, use the Agent API.”
SerpApi supports an `md` output format that returns markdown-formatted search results optimized for LLMs/AI agents, and a dedicated markdown-output feature serving any search result as clean markdown, plus raw HTML output — but this is markdown/HTML of the SERP results themselves, not full page text extraction of the underlying linked pages. missing for 10: evidence of extracting full text/markdown of the destination web pages (not just search result snippets/HTML/markdown), and independent hands-on verification of markdown output quality.
- [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
- [claimed-docs] “output to `json` (default)... `html` to get the raw HTML retrieved, or `md` to get a markdown-formatted version optimized for LLMs and AI ag…”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
developerGet structured output matching a JSON schema I define
weight 2 · round to Perplexity Sonar APIDocs explicitly describe a 'Structured output' feature that 'makes the model return JSON that conforms to a schema you define, so you can deserialize it directly,' directly matching the story. Missing for 10: independent/hands-on corroboration beyond first-party docs, and no code sample showing the schema definition syntax in the evidence pack.
- [claimed-docs] “Structured output makes the model return JSON that conforms to a schema you define, so you can deserialize it directly.”
SerpApinone0/10SerpApi returns structured JSON per endpoint and lets developers pick output format (json/html/md) or filter fields, but there is no evidence of a mechanism to supply a custom JSON schema that the response is validated/shaped against.
- [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
- [claimed-docs] “Parameter defines the fields you want to include in the output, reducing payload size for faster response.”
- [claimed-docs] “output to `json` (default)... `html` to get the raw HTML retrieved, or `md` to get a markdown-formatted version optimized for LLMs and AI ag…”
data engineerCrawl subpages or entire sites starting from a search result
weight 1 · round drawnPerplexity Sonar APInone0/10Evidence shows single-query search, URL fetch, and content-extraction tools (docs-17, docs-30, docs-38) but nothing about recursively crawling subpages or an entire site starting from a search result; no site-map/crawl-depth feature is documented.
- [claimed-docs] “Access real-time web search results with Perplexity's Search API. Get ranked results, domain filtering, multi-query search, and content extr…”
- [claimed-docs] “Built-in tools | Perplexity-hosted capabilities: web search, URL fetch, people and finance search, and a code sandbox. Enable each by `type`…”
- [claimed-docs] “Use the Search API when you need raw results for your own processing. For an LLM-generated answer with citations, use the Agent API.”
SerpApinone0/10SerpApi's documented capability is restricted to scraping structured search engine results pages (Google, Bing, News, Ads, Flights, etc.); there is no evidence of any subpage/site-crawling capability that would follow a search result link to fetch and traverse the destination site's pages. All docs and GitHub references describe SERP scraping only, not general web crawling. Missing for 10: any documentation or code showing SerpApi fetching/crawling pages beyond the search results themselves, a crawl depth/breadth parameter, or site-wide crawling feature.
- [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
- [claimed-docs] “Our Google News API allows you to scrape results from the Google News search page.”
- [github] “This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
Filters controls — stories about filters controls in this arenaFilters controls
Stories about filters controls in this arena
Query filters
developerRestrict or exclude specific domains from my search results
weight 2 · round drawnDocs explicitly mention 'domain filtering' as a Search API feature and reference 'advanced filtering' of search results, indicating some domain include/exclude capability exists. However, there is no detailed documentation of the actual parameter/API syntax, allowed limits, or confirmation it supports exclusion specifically (vs just filtering to include). Missing for 10: explicit parameter documentation (e.g. search_domain_filter), examples of excluding domains, independent/hands-on verification of behavior.
- [claimed-docs] “Access real-time web search results with Perplexity's Search API. Get ranked results, domain filtering, multi-query search, and content extr…”
- [claimed-docs] “Get raw, ranked web search results with advanced filtering and real-time data.”
SerpApi supports Google search operators like 'site:' which can be used to include or exclude specific domains (e.g., site:example.com or -site:example.com), giving developers a workaround to restrict/exclude domains, but there's no dedicated first-class parameter or documented feature specifically for domain inclusion/exclusion filtering. missing for 10: a documented dedicated domain-restrict/exclude parameter, explicit examples of exclude-domain usage, and independent confirmation this works reliably across engines.
- [claimed-docs] “You can use anything that you would use in a regular Google search. e.g. `inurl:`, `site:`, `intitle:`.”
developerRead per-result relevance scores to threshold what enters my pipeline
weight 1 · round drawnPerplexity Sonar APInone0/10Docs describe ranked web/search results, citations, and a search_results field, but nowhere do they document per-result relevance/confidence scores that a developer could use to threshold what enters a pipeline. Missing for 10: any documented score field in the API response schema, docs explaining score semantics, or examples of threshold-based filtering.
- [claimed-docs] “Access real-time web search results with Perplexity's Search API. Get ranked results, domain filtering, multi-query search, and content extr…”
- [claimed-docs] “"citations": [ "<string>" ], "search_results": [”
- [claimed-docs] “Use the Search API when you need raw results for your own processing. For an LLM-generated answer with citations, use the Agent API.”
Freshness coverage — stories about freshness coverage in this arenaFreshness coverage
Stories about freshness coverage in this arena
Freshness
data engineerGet fresh results with date-range and recency filters backed by a frequently updated index
weight 3 · round to Perplexity Sonar APIDocs claim 'real-time data' and 'advanced filtering'/'domain filtering' in the Search API, implying a fresh, filterable index, but no evidence explicitly documents date-range or recency-specific filter parameters or index update cadence. missing for 10: explicit documentation of recency/date-range filter parameters, evidence of index refresh frequency, independent verification of freshness.
- [claimed-docs] “Get raw, ranked web search results with advanced filtering and real-time data.”
- [claimed-docs] “Access real-time web search results with Perplexity's Search API. Get ranked results, domain filtering, multi-query search, and content extr…”
- [claimed-docs] “Use the Search API when you need raw results for your own processing. For an LLM-generated answer with citations, use the Agent API.”
SerpApinone0/10The evidence shows SerpApi is a real-time scraping API with caching (1h cache) and mentions of 'real-time JSON API' claims, but nothing in the pack documents explicit date-range or recency filter parameters (e.g., time-window search flags) or describes how frequently the underlying index itself is refreshed. Without concrete documentation of such filters, the axis is unaddressed by the evidence provided.
- [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
- [claimed-docs] “Cache expires after 1h. Cached searches are free, and are not counted towards your searches per month.”
- [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”
data engineerQuery dedicated verticals like news, images, or finance through specific endpoints or category filters
weight 2 · round to SerpApiDocs mention a built-in 'finance search' tool and general domain/content filtering in the Search API, showing some vertical/category targeting, but there is no evidence of dedicated endpoints or filters for news or images verticals specifically. missing for 10: dedicated news endpoint/filter, dedicated images endpoint/filter, explicit documentation of category-based filtering beyond finance/people/web/URL/sandbox tools.
- [claimed-docs] “Built-in tools | Perplexity-hosted capabilities: web search, URL fetch, people and finance search, and a code sandbox. Enable each by `type`…”
- [claimed-docs] “Access real-time web search results with Perplexity's Search API. Get ranked results, domain filtering, multi-query search, and content extr…”
- [claimed-docs] “Get raw, ranked web search results with advanced filtering and real-time data.”
SerpApi ships dedicated endpoints for specific verticals such as Google News (with topic_token category filters) and other specialized APIs like Google Flights and Google Ads Transparency Center, alongside the core search API; images vertical is implied by the broader engine family though not explicitly documented in this pack. Evidence includes first-party docs for parameters and topic filtering plus API listings confirming multiple vertical-specific endpoints. Missing for 10: explicit documentation/example of an Images-specific endpoint and independent hands-on confirmation of vertical query results.
- [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
- [claimed-docs] “Parameter defines the Google News topic token. It is used for accessing the news results for a specific topic (e.g., "World", "Business", "T…”
- [claimed-docs] “Parameter defines the Google News topic token. It is used for accessing the news results for a specific topic”
- [claimed-docs] “Our Google News API allows you to scrape results from the Google News search page.”
- [claimed-docs] “Use SerpApi's Google Flights API to scrape Google Flights information.”
- [claimed-docs] “Use SerpApi's Google Ads Transparency Center API to scrape Ads information display on Google.”
- [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
Targeting
data engineerLocalize results by country, language, or location parameters
weight 2 · round to SerpApiPerplexity Sonar APInone0/10The evidence pack describes domain filtering, multi-query search, search context tuning, and content extraction, but no citation mentions country, language, or location-based localization parameters for the Sonar/Search/Agent APIs. This is a plausible axis for a web-search API, but no supporting evidence exists in the pack.
SerpApi docs and SDK examples show explicit location/language parameters (e.g. 'location' recommended at city level, 'gl'/search origin parameter) and a code example passing 'location':'Austin,Texas' with a helper to disambiguate locations. This directly supports localization by country/language/location for a data engineer's search queries. Missing for 10: explicit documentation/example of the 'hl' (language) and 'gl' (country) parameters together with independent hands-on confirmation of localized result differences.
- [claimed-docs] “It is recommended to specify location at the city level in order to simulate a real user’s search.”
- [claimed-docs] “Parameter defines from where you want the search to originate.”
- [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
- [github] “This prints the first 3 locations matching Austin (Texas, Texas, Rochester).”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to Perplexity Sonar APIThe Sonar/Agent API exposes a very wide surface — search, agent orchestration, MCP server (remote and local), CLI, SDKs, sandboxed code execution, structured output, model fallback, profiles — suggesting most capabilities are API-accessible and even API-first, with a playground for exploration. However, none of the evidence explicitly compares API capabilities against the consumer chat UI (e.g., Spaces, Threads, Collections, personalization features), so full UI-parity is not directly demonstrated. Missing for 10: explicit statement or evidence that all consumer-UI-only features (e.g., Spaces, saved threads, UI personalization) are also exposed via API, and independent confirmation of parity.
- [claimed-docs] “You can now run Perplexity Search straight from your terminal. The Perplexity CLI returns the same ranked results as JSON, ready for shell p…”
- [claimed-docs] “Install and use Perplexity's pplx command-line interface for web search and query-relevant page snippets from your terminal or coding agent.”
- [claimed-docs] “Built-in tools | Perplexity-hosted capabilities: web search, URL fetch, people and finance search, and a code sandbox. Enable each by `type`…”
- [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer — for results that must be …”
- [claimed-docs] “Remote MCP server (recommended): hosted by Perplexity at `https://api.perplexity.ai/mcp`. No installation, nothing to update, works with any…”
- [claimed-docs] “Local MCP server: run the open-source server on your machine over stdio. Use this if your client only supports stdio servers or you need to …”
- [claimed-docs] “A profile is a reusable, versioned configuration that you save and manage. ... Select a profile by ID instead of repeating the full configur…”
- [claimed-docs] “You can also [try Perplexity Search in the interactive Playground](https://console.perplexity.ai/project/playground/search) with no API key …”
Evidence strongly documents that SerpApi's core scraping functionality (Google, News, Ads, Flights, etc.) and output formats (json/html/md) are fully accessible via the API and various language libraries, and even account-level settings like ZeroTrace Mode and Automatic Early Renewal are described as configurable in docs. However, there is no evidence of an API/endpoint for programmatically managing billing, plan changes, or dashboard analytics (api-metrics page appears to be a UI-only dashboard), and no OpenAPI spec was found (404s), leaving unclear whether account/administrative actions in the UI have full API parity. missing for 10: API endpoints for billing/plan management, confirmation that dashboard-only features (api-metrics, account settings) have API equivalents, and independent verification of full UI-API parity.
- [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
- [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
- [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”
- [claimed-docs] “You can set your plan to Automatic Early Renewal. It will trigger an early renewal once you've used all your searches.”
- [claimed-docs] “Monitor SerpApi's live API success rates and response times.”
- [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
- [claimed-docs] “Install the library for your language and use your API key to start searching”
ai-native userRead the product's source under an open license
weight 2 · round drawnPerplexity Sonar APInone0/10Perplexity Sonar API is a closed commercial API; the evidence shows SDKs and a local MCP server are open-source components, but there is no evidence the core Sonar/Agent API source or models are released under an open license, so a user cannot read the product's source.
SerpApinone0/10SerpApi is a closed, paid SaaS API; only client-side SDK wrappers (e.g. google-search-results-python) are on GitHub, and there is no evidence the core search/scraping service or API source is released under an open license — the wrappers are thin API clients, not 'the product' itself.
- [github] “This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more”
- [github] “This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more, using Se…”
- [github] “This package will soon be **deprecated** in favor of [serpapi-python](https://github.com/serpapi/serpapi-python). We recommend migrating to …”
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Pricing clarity
developerRead documented rate limits and concurrency caps with a self-serve upgrade path
weight 2 · round to Perplexity Sonar APIDocs describe a dedicated rate-limits/usage-tiers page where spending automatically and permanently upgrades your tier (self-serve, no manual request needed), which covers rate limits and an upgrade path. However, no evidence explicitly documents concurrency caps or specific per-tier numeric limits. Missing for 10: explicit concurrency cap documentation, concrete per-tier RPM/RPS figures, independent confirmation of the auto-upgrade mechanism.
- [claimed-docs] “As you spend more on API credits over time, you automatically advance to higher tiers with increased rate limits.”
- [claimed-docs] “As you spend more on API credits over time, you automatically advance to higher tiers with increased rate limits. Higher tiers unlock signif…”
- [claimed-docs] “As you spend more on API credits over time, you automatically advance to higher tiers with increased rate limits... once you reach a tier, y…”
Pricing page shows tiered plans with searches-per-month caps (e.g., 250/month free tier) and a self-serve 'Automatic Early Renewal' upgrade mechanism triggered once searches are used up, giving a self-serve path to more capacity. However, there is no explicit documentation of concurrency caps (simultaneous request limits) or per-second/per-minute rate limits, which developers typically need for building resilient clients. Missing for 10: explicit concurrency/rate-limit numbers (requests per second/minute), documented error/backoff behavior when limits are hit, and independent confirmation of self-serve upgrade flow beyond pricing page claims.
- [claimed-docs] “Free $ 0 / month 250 searches per month”
- [claimed-docs] “You can set your plan to Automatic Early Renewal. It will trigger an early renewal once you've used all your searches.”
- [claimed-docs] “Included with the Production Plan and above, with up to $2 million in coverage.”
developerPrototype against the API on a free tier or free credits
weight 2 · round to SerpApiPerplexity Sonar APInone0/10The evidence shows an API key signup flow and a no-key-required Playground for testing, but no documentation of a free tier, free trial credits, or free quota for the Sonar API itself — rate-limit tiers are described as advancing with paid spend, not free usage. missing for 10: explicit free credits/free tier terms, any trial credit amount, or free-usage rate limits for new developers.
- [claimed-docs] “You can also [try Perplexity Search in the interactive Playground](https://console.perplexity.ai/project/playground/search) with no API key …”
- [claimed-docs] “Generate an API key and make your first call in < 3 minutes.”
- [claimed-docs] “As you spend more on API credits over time, you automatically advance to higher tiers with increased rate limits. Higher tiers unlock signif…”
SerpApi's pricing page explicitly documents a free tier of 250 searches/month at $0, and cached searches are also free and don't count against quota, giving developers a clear path to prototype without payment; the free plan is easy to sign up for via API key per the docs/GitHub examples. Missing for 10: no independent/community confirmation of the free-tier signup experience or its limitations in practice.
- [claimed-docs] “Free $ 0 / month 250 searches per month”
- [claimed-docs] “Cache expires after 1h. Cached searches are free, and are not counted towards your searches per month.”
- [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
- [claimed-docs] “Install the library for your language and use your API key to start searching”
developerSee clear per-request or per-credit pricing without talking to sales
weight 3 · round to SerpApiPerplexity publishes a dedicated pricing page (search context, Pro Search, credit-tier rate limits) and lets developers self-serve by generating an API key in minutes without contacting sales, implying transparent self-serve pricing. However the evidence pack never shows actual per-request or per-credit dollar figures, so we can't confirm the pricing is fully itemized/clear from what's provided. Missing for 10: concrete $/request or $/credit rate tables, confirmation that all model/tool usage (sandbox, MCP, agent tools) is separately priced and disclosed publicly.
- [claimed-docs] “Pro Search enhances Sonar Pro with automated tool usage and multi-step reasoning. When enabled, the model can perform multiple web searches …”
- [claimed-docs] “Search context determines how much web information is retrieved. Higher context = more comprehensive results.”
- [claimed-docs] “As you spend more on API credits over time, you automatically advance to higher tiers with increased rate limits.”
- [claimed-docs] “As you spend more on API credits over time, you automatically advance to higher tiers with increased rate limits. Higher tiers unlock signif…”
- [claimed-docs] “When using tools with the Agent API:”
- [claimed-docs] “Generate an API key and make your first call in < 3 minutes.”
SerpApi publishes a public pricing page with a free tier (250 searches/month), paid plans, and automatic early renewal, all discoverable without sales contact (serpapi-docs-6, serpapi-docs-26). Community discussion on HN also references SerpApi's plan structure without any indication of a sales-gated model. Missing for 10: a full per-request/credit cost table across all paid tiers and confirmation that no enterprise tier requires contacting sales.
- [claimed-docs] “Free $ 0 / month 250 searches per month”
- [claimed-docs] “You can set your plan to Automatic Early Renewal. It will trigger an early renewal once you've used all your searches.”
- [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”
- [community] “I used Serp via API many moons ago. The most interesting part of the company imo is their legal defense of different plans... 'Our U.S. Lega…”
Scale throughput
data engineerSubmit batched or asynchronous jobs for high-volume query workloads
weight 2 · round to SerpApiPerplexity Sonar APInone0/10The evidence covers synchronous SDK calls, streaming (SSE), retries, rate-limit tiers, and model routing/fallback, but nowhere mentions batch job submission or an asynchronous job/queue API for high-volume workloads — the async client mentioned is just a non-blocking HTTP client, not a batch-job system. No documentation of batch endpoints, job polling, or bulk submission exists in the pack.
SerpApi explicitly supports async submission via the `async` parameter (submit now, retrieve later) plus a Searches Archive API to fetch async results later, which directly enables asynchronous high-volume workflows [serpapi-docs-9][serpapi-docs-14]. However, there is no explicit documentation of a dedicated batch-job endpoint or bulk-submission API for large query sets. Missing for 10: dedicated batch/bulk submission endpoint documentation, rate/throughput guarantees for high-volume async workloads, and independent confirmation of async reliability at scale.
- [claimed-docs] “Parameter defines the way you want to submit your search to SerpApi. It can be set to `false` (default) to open an HTTP connection and keep …”
- [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnPerplexity Sonar APInone0/10No evidence in the pack mentions data residency, region selection, or data storage location controls for the Sonar API; this is an applicable axis for an API/cloud service but no documentation addresses it.
ai-native userPrevent my data from being used to train AI models
weight 3 · round to SerpApiPerplexity Sonar APInone0/10No evidence in the pack addresses data usage for training, opt-out settings, or a privacy/data-retention policy for API data; nothing in the docs pack mentions training-data opt-out at all.
SerpApi doesn't explicitly address AI-training use of customer data, but its ZeroTrace Mode claims that once a search completes, no search parameters/files/data are stored, which would preclude such data being used to train models — an indirect but relevant privacy control. missing for 10: explicit AI-training data-use policy/statement, opt-out mechanism specifically for AI training, and independent verification of ZeroTrace Mode's scope.
- [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”
ai-native userControl data retention and deletion
weight 2 · round to SerpApiPerplexity Sonar APInone0/10No evidence in the pack addresses data retention policies, deletion controls, or privacy/data-handling settings for the Sonar API; the docs cover search, agents, MCP, routing, and SDKs but nothing about controlling stored data or deleting logs/history.
SerpApi documents a 'ZeroTrace Mode' that stops storage of search parameters/files/data, giving users some control over data retention, and mentions a temporary 1h cache and a Searches Archive API for retrieving stored results. However, there's no documentation of a general data-deletion mechanism, retention policy for non-ZeroTrace plans, or user-initiated deletion of historical searches/account data. missing for 10: explicit deletion/export controls for stored account data, retention policy details for standard (non-ZeroTrace) plans, independent confirmation that ZeroTrace behaves as claimed.
- [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”
- [claimed-docs] “Cache expires after 1h. Cached searches are free, and are not counted towards your searches per month.”
- [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”
- [github] “The search results are stored in a temporary cache. The previous search can be retrieved from the cache for free.”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round to SerpApiPerplexity Sonar APInone0/10No evidence in the pack addresses telemetry opt-out or usage-tracking controls for the Sonar API; nothing mentions privacy settings, data retention toggles, or telemetry configuration.
SerpApi's ZeroTrace Mode lets users prevent storage of search parameters/data ('once a search completes, it's as if it never happened'), which is adjacent to a telemetry/usage-tracking opt-out but is framed around search data retention rather than explicit telemetry or usage analytics collection. No documentation addresses opting out of product usage telemetry (e.g., client library analytics, dashboard tracking) specifically. Missing for 10: explicit telemetry/usage-tracking opt-out documentation, evidence covering the SDK/API client's own telemetry behavior, and independent confirmation that ZeroTrace disables all tracking beyond search data.
- [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”
Search quality — stories about search quality in this arenaSearch quality
Stories about search quality in this arena
Ai consumption
ai-native userPlug the API into an agent as a ready-made tool, with function-calling schemas and agent-framework integrations designed for direct tool-call consumption
weight 3 · round drawnPerplexity ships an official MCP server (remote and local/stdio) that exposes its search/reasoning as agent-consumable tools, plus OpenAPI schema, official SDKs with type-safe function signatures, built-in tools (web search, sandbox, URL fetch) designed for tool-call consumption within the Agent API, and integration with Anthropic's Messages API MCP connector. This directly matches the story of plugging the API into an agent via ready-made schemas/integrations. Missing for 10: independent third-party validation of agent-framework interop (e.g. LangChain/AutoGen adapters) and hands-on developer reports confirming smooth tool-call schema usage beyond vendor docs.
- [claimed-docs] “The Perplexity MCP Server enables AI assistants to access Perplexity's powerful search and reasoning capabilities directly within their work…”
- [claimed-docs] “Remote MCP server (recommended): hosted by Perplexity at `https://api.perplexity.ai/mcp`. No installation, nothing to update, works with any…”
- [claimed-docs] “Local MCP server: run the open-source server on your machine over stdio. Use this if your client only supports stdio servers or you need to …”
- [claimed-docs] “Use Perplexity's tools in a Messages API request with the MCP connector:”
- [claimed-docs] “Built-in tools | Perplexity-hosted capabilities: web search, URL fetch, people and finance search, and a code sandbox. Enable each by `type`…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://docs.perplexity.ai/docs/getting-started/integrations/mcp-server”
- [github] “The library includes type definitions for all request params and response fields, and offers both synchronous and asynchronous clients power…”
SerpApi documents an official MCP server (serpapi-mcp) enabling any MCP-compatible agent (Claude, ChatGPT, Cursor) to call it as a web search tool, plus markdown-optimized output designed for LLM/agent consumption and llms.txt/docs.md endpoints for agent discoverability. missing for 10: no published OpenAPI/function-calling JSON schema (openapi.json probes 404), and no independent hands-on report of agent-framework integration success beyond vendor docs.
- [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
- [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
- [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
- [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
- [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”
Llm ready results
developerGet a sourced, LLM-generated answer to a query in a single API call
weight 2 · round to Perplexity Sonar APIDocs explicitly describe getting web-grounded answers with built-in citations in one API call (Sonar/Agent API), with a quickstart to make the first call in under 3 minutes, and the API reference shows a response schema with 'citations' and 'search_results' fields. Docs even distinguish this from the raw Search API, clarifying that the sourced LLM-generated answer use case is served by the Sonar/Agent endpoints. missing for 10: independent hands-on developer verification of citation quality/accuracy beyond vendor docs.
- [claimed-docs] “Get web-grounded answers with built-in citations in one call, or access third-party models from OpenAI, Anthropic, Google, and xAI with web …”
- [claimed-docs] “"citations": [ "<string>" ], "search_results": [”
- [claimed-docs] “Generate an API key and make your first call in < 3 minutes.”
- [claimed-docs] “Use the Search API when you need raw results for your own processing. For an LLM-generated answer with citations, use the Agent API.”
SerpApinone0/10SerpApi's evidence shows it returns structured/markdown search results (including Google AI Overview scraping and RAG use-case framing) meant to be fed into a separate LLM pipeline, not a single-call endpoint that itself returns an LLM-generated, sourced answer. No endpoint or docs describe SerpApi generating the answer itself.
- [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”
- [claimed-docs] “Find out how your content is being used in AI-generated answers on Google AI Mode. Monitor your brand's visibility and optimize your SEO str…”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
developerGet results sized and ranked for direct use as LLM context in a RAG pipeline
weight 3 · round drawnDocs explicitly market a Search API returning 'raw, ranked web search results' for developer processing, distinct from the answer-generating Agent API, with domain filtering, multi-query search, and content extraction designed for RAG use, plus embeddings generation for semantic search/RAG pipelines. SDKs, CLI, and structured citations/search_results fields support direct ingestion into a RAG context window. missing for 10: no independent benchmark or hands-on evidence of chunk sizing/token-length suitability for context windows, and no explicit documentation of result truncation or size controls tailored to LLM context limits.
- [claimed-docs] “Get raw, ranked web search results with advanced filtering and real-time data.”
- [claimed-docs] “Generate high-quality embeddings for semantic search and RAG pipelines.”
- [claimed-docs] “Access real-time web search results with Perplexity's Search API. Get ranked results, domain filtering, multi-query search, and content extr…”
- [claimed-docs] “Use the Search API when you need raw results for your own processing. For an LLM-generated answer with citations, use the Agent API.”
- [claimed-docs] “"citations": [ "<string>" ], "search_results": [”
SerpApi explicitly supports markdown output 'optimized for LLMs and AI agents' with roughly half the token size of JSON, a field-selection parameter to reduce payload size, and explicitly markets a RAG use case ('Feed search data into AI pipelines to minimize hallucinations'), plus an llms.txt and MCP server for agent consumption. missing for 10: independent/hands-on evidence confirming markdown output quality and ranking relevance in a real RAG pipeline, and no benchmark showing token/size reduction claims validated externally.
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
- [claimed-docs] “Parameter defines the fields you want to include in the output, reducing payload size for faster response.”
- [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”
- [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
- [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
- [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
Retrieval modes
developerFind pages similar to a URL I already have
weight 1 · round drawnPerplexity Sonar APInone0/10The evidence pack covers web search, embeddings, MCP integration, agent tooling, and code sandboxing, but there is no mention of a 'find similar pages/URLs' or URL-based similarity search feature anywhere in the docs.
SerpApinone0/10SerpApi's docs only mention support for generic Google search operators like inurl:, site:, and intitle: — there is no evidence of support for the 'related:' operator or any dedicated 'find similar pages' feature that would let a developer discover pages similar to a given URL.
- [claimed-docs] “You can use anything that you would use in a regular Google search. e.g. `inurl:`, `site:`, `intitle:`.”
- [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
developerRun meaning-based semantic search that finds results keyword engines miss
weight 3 · round to Perplexity Sonar APIDocs explicitly mention embeddings 'for semantic search and RAG pipelines' and web search with ranked/filtered results, supporting meaning-based retrieval beyond keyword matching, but the evidence never shows benchmark or hands-on proof that this semantic search surfaces results keyword engines miss. Missing for 10: independent/hands-on evidence comparing semantic vs keyword recall, detail on embedding model quality/architecture, and concrete examples of semantic-only matches.
- [claimed-docs] “Generate high-quality embeddings for semantic search and RAG pipelines.”
- [claimed-docs] “Get raw, ranked web search results with advanced filtering and real-time data.”
- [claimed-docs] “Access real-time web search results with Perplexity's Search API. Get ranked results, domain filtering, multi-query search, and content extr…”
- [claimed-docs] “Search context determines how much web information is retrieved. Higher context = more comprehensive results.”
SerpApinone0/10SerpApi's evidence describes scraping keyword-based results from Google, Bing, etc. (serpapi-docs-1, serpapi-gh-6) and provides RAG/feed-to-LLM use cases (serpapi-docs-25), but nothing indicates it performs meaning-based/semantic search or surfaces results that keyword engines would miss — it merely mirrors the underlying search engine's keyword results. No vector search, embeddings, or semantic ranking capability is mentioned anywhere in the pack.
- [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
- [github] “This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more”
- [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparablePerplexity Sonar APInone0/10The evidence only shows Perplexity publishing its own MCP server (and an Anthropic-side MCP connector for consuming Perplexity's tools) — i.e., Perplexity acts as the tool provider, not as a client that ingests third-party MCP servers' tools. The Agent API's 'built-in tools' (web search, sandbox, fetch, finance/people search) are Perplexity-hosted, and there is no documentation of a mechanism to plug an arbitrary external MCP server into the Agent/Sonar API so it can call that server's tools.
- [claimed-docs] “The Perplexity MCP Server enables AI assistants to access Perplexity's powerful search and reasoning capabilities directly within their work…”
- [claimed-docs] “Remote MCP server (recommended): hosted by Perplexity at `https://api.perplexity.ai/mcp`. No installation, nothing to update, works with any…”
- [claimed-docs] “Local MCP server: run the open-source server on your machine over stdio. Use this if your client only supports stdio servers or you need to …”
- [claimed-docs] “Use Perplexity's tools in a Messages API request with the MCP connector:”
- [claimed-docs] “Built-in tools | Perplexity-hosted capabilities: web search, URL fetch, people and finance search, and a code sandbox. Enable each by `type`…”
SerpApin/aSerpApi is a search-data API/tool provider, not an AI agent or agentic platform that would itself consume/plug in external MCP servers. The evidence instead shows SerpApi ships its OWN MCP server so that agents can consume SerpApi as a tool (serpapi-docs-21, serpapi-probe-4) — the inverse relationship, which is the correct axis for this product type, not this story's client-side axis.
- [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
- [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableThe Agent API provides a genuine delegate-task capability: presets give 'a working agent in one field', instructions/input define system prompts and per-turn tasks, and built-in tools (web search, URL fetch, code sandbox) let the agent autonomously perform multi-step work and return results inline. However, this is a developer-facing API construct rather than a built-in assistant embedded in an end-user product surface — there's no evidence of a native chat/assistant UI within the product itself that an 'ai-native user' interacts with directly. missing for 10: evidence of an end-user-facing assistant UI (vs. API-only agent), independent/hands-on validation of agent task delegation working reliably, and clarity on autonomy limits beyond documented tool list.
- [claimed-docs] “A `preset` gives you a working agent in one field.”
- [claimed-docs] “`instructions` is the agent's **system prompt** — the rules that hold on every turn. `input` is the specific thing to do this turn.”
- [claimed-docs] “Built-in tools | Perplexity-hosted capabilities: web search, URL fetch, people and finance search, and a code sandbox. Enable each by `type`…”
- [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer — for results that must be …”
- [claimed-docs] “For most multi-turn conversations, use `previous_response_id` to continue from a completed prior response without resending the conversation…”
- [claimed-docs] “Model fallback enables specifying multiple models in a `models` array. The API tries each model in order until one succeeds, providing autom…”
- [claimed-docs] “A profile is a reusable, versioned configuration that you save and manage. ... Select a profile by ID instead of repeating the full configur…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · not comparablePerplexity Sonar APIn/aPerplexity Sonar API is a search/answer/agent API and SDK, not an event/rule-based automation or workflow-trigger platform; there's no concept of user-defined triggers firing actions on events. This is a wrong-axis question for this product category.
SerpApinone0/10SerpApi's evidence pack shows only search scraping APIs, caching, and plan billing automation (Automatic Early Renewal), none of which let a user define custom rules that trigger arbitrary actions on events. No webhook, alerting, or rule-engine capability is documented.
- [claimed-docs] “You can set your plan to Automatic Early Renewal. It will trigger an early renewal once you've used all your searches.”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparablePerplexity's Agent API 'profiles' are described as reusable, versioned configurations that can be saved and selected by ID, which is a thin form of automation versioning, but there is no documented review workflow or rollback mechanism for these profiles or any other automation constructs. missing for 10: explicit rollback/revert capability, change review or diff tooling, audit history beyond simple versioning.
- [claimed-docs] “A profile is a reusable, versioned configuration that you save and manage. ... Select a profile by ID instead of repeating the full configur…”
ai-native userExport all of my data in open formats and leave
weight 3 · not comparablePerplexity Sonar APIn/aPerplexity Sonar API is a developer-facing API/platform for search, generation, and agent workflows; it does not function as a data-storage application where a user accumulates personal content that would need bulk export in open formats. Data export/portability is not a natural axis for this kind of product — developers already own their request/response data via their own integration.
SerpApi's outputs (search results) are always available in open formats—JSON, HTML, or markdown—and a Searches Archive API lets users retrieve past results, while ZeroTrace mode means the vendor doesn't retain data at all. But there is no documented bulk 'export all my account data and leave' feature, account-data portability tool, or data-deletion/export workflow beyond retrieving individual past search results. missing for 10: a documented bulk account-data export mechanism, explicit data portability/deletion tooling, and independent confirmation that users can fully extract historical usage/account data before leaving.
- [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
- [claimed-docs] “output to `json` (default)... `html` to get the raw HTML retrieved, or `md` to get a markdown-formatted version optimized for LLMs and AI ag…”
- [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
- [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”
- [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”
ai-native userSelf-host the core product
weight 3 · not comparablePerplexity Sonar APInone0/10Perplexity Sonar API is a hosted, closed-source API/SaaS product; there is no evidence of any self-hostable core model, search index, or backend—only a local MCP connector (a thin client wrapper) that still calls Perplexity's cloud API. The core product (search/answer engine) cannot be run on the user's own infrastructure. missing for 10: any self-hosted deployment option, open-source core engine/model weights, or on-prem offering.
- [claimed-docs] “Remote MCP server (recommended): hosted by Perplexity at `https://api.perplexity.ai/mcp`. No installation, nothing to update, works with any…”
- [claimed-docs] “Local MCP server: run the open-source server on your machine over stdio. Use this if your client only supports stdio servers or you need to …”
- [community] “They've had their sonar models on API since forever. Even the pricing looks same as always. If anything they've regressed - selection of mod…”
SerpApin/aSerpApi is a hosted SaaS scraping/API service; there is no evidence of a self-hostable core engine, and the product's architecture (proprietary scraping infrastructure, IP rotation, legal shield tied to SerpApi's own infrastructure) is inherently a managed cloud service, not something designed to be self-hosted by users.
developerChoose between keyword, neural, or hybrid retrieval modes per query
weight 2 · not comparablePerplexity Sonar APInone0/10The evidence describes search context size, domain filtering, and multi-query search, but no documentation mentions selectable retrieval modes such as keyword, neural, or hybrid search per query.