Tavily vs Perplexity Sonar API
free-tier · credits · subscription-flat · enterprise-custom
·credits · usage-based · enterprise-custom
Perplexity Sonar API wins · 8–12 (22 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 to Perplexity Sonar APITavily hosts a working llms.txt (confirmed live via probe, HTTP 200) with agent-oriented CLI examples, plus an agent-setup SKILL.md and MCP server docs explicitly designed for agent consumption. missing for 10: independent third-party confirmation that agents successfully consume/act on the llms.txt content beyond Tavily's own docs.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.tavily.com/llms.txt # Tavily Docs > Tavily is the web layer for AI agents: real-time web search, c…”
- [claimed-docs] “tvly search "latest AI news" tvly extract "https://example.com" tvly crawl "https://docs.example.com" --depth 2 tvly research "compare React…”
- [claimed-docs] “Read and execute tavily.com/agent-setup/SKILL.md”
- [claimed-docs] “Let your coding agent install and configure Tavily for you.”
- [claimed-docs] “Compatible with both Cursor and Claude Desktop! Tavily MCP is also compatible with any MCP client.”
- [probe] “official MCP server documented at https://docs.tavily.com/documentation/mcp”
Direct 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.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnTavily is a REST API with SDKs (Python/JS) and a CLI (tvly search/extract/crawl/research) that can be run non-interactively from scripts or CI, with API keys, rate limits, and usage/logs endpoints suited to automated pipelines. missing for 10: no explicit CI/CD pipeline example (e.g., GitHub Actions) or independent report confirming headless CI usage.
- [claimed-docs] “pip install tavily-python”
- [claimed-docs] “tvly search "latest AI news" tvly extract "https://example.com" tvly crawl "https://docs.example.com" --depth 2 tvly research "compare React…”
- [claimed-docs] “The Python SDK allows for easy interaction with the Tavily API, offering the full range of our search functionality directly from your Pytho…”
- [claimed-docs] “Tavily's JavaScript SDK allows for easy interaction with the Tavily API, offering the full range of our search and extract functionalities d…”
- [claimed-docs] “Environment Requests per minute (RPM) Development 100 Production 1,000”
- [claimed-docs] “Retrieve per-request usage logs for the API keys under your account or organization.”
- [claimed-docs] “tavily_client = TavilyClient(api_key="tvly-YOUR_API_KEY") response = tavily_client.search("Who is Leo Messi?")”
Sonar 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”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnTavily documents an official MCP server providing tavily-search and tavily-extract tools, explicitly compatible with Cursor, Claude Desktop, and any MCP client, confirmed by a live docs page probe. Missing for 10: independent/hands-on third-party confirmation of MCP server reliability and no mention of the full tool set (crawl/map/research) being exposed via MCP.
- [claimed-docs] “The Tavily MCP server provides: Seamless interaction with the tavily-search and tavily-extract tools”
- [claimed-docs] “Compatible with both Cursor and Claude Desktop! Tavily MCP is also compatible with any MCP client.”
- [claimed-docs] “The Tavily MCP server provides: * Seamless interaction with the tavily-search and tavily-extract tools”
- [claimed-docs] “Compatible with both [Cursor](https://cursor.sh) and [Claude Desktop](https://claude.ai/download)! Tavily MCP is also compatible with any MC…”
- [probe] “official MCP server documented at https://docs.tavily.com/documentation/mcp”
Perplexity 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”
ai-native userUse an official CLI
weight 2 · round to Perplexity Sonar APIThe llms.txt docs excerpt shows CLI commands like `tvly search`, `tvly extract`, `tvly crawl`, `tvly research`, suggesting an official CLI named `tvly` exists, but there is no dedicated installation guide, README, or independent corroboration beyond this single snippet. missing for 10: dedicated CLI docs/install instructions, GitHub repo or package listing for the CLI, independent/hands-on confirmation of the tool.
- [claimed-docs] “tvly search "latest AI news" tvly extract "https://example.com" tvly crawl "https://docs.example.com" --depth 2 tvly research "compare React…”
Perplexity 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 drawnTavily is fundamentally an API-first product with extensive documented REST endpoints (search, extract, crawl, map, research) plus official Python/JS SDKs, rate-limit docs, usage/logs endpoints, and keyless trial mode — all clearly aimed at programmatic/AI-native consumption. Missing for 10: a discoverable machine-readable OpenAPI/swagger spec (probe found 404s on standard paths), which would round out full API-native tooling.
- [claimed-docs] “Execute a search query using Tavily Search.”
- [claimed-docs] “Extract content from one URL or batch up to 20 URLs in one request. Successful URLs appear in results; per-URL failures appear in failed_res…”
- [claimed-docs] “Tavily Crawl is a graph-based website traversal tool that can explore hundreds of paths in parallel with built-in extraction and intelligent…”
- [claimed-docs] “Tavily Map traverses websites like a graph and can explore hundreds of paths in parallel with intelligent discovery to generate comprehensiv…”
- [claimed-docs] “Tavily Research performs comprehensive research on a given topic by conducting multiple searches, analyzing sources, and generating a detail…”
- [claimed-docs] “The Python SDK allows for easy interaction with the Tavily API, offering the full range of our search functionality directly from your Pytho…”
- [claimed-docs] “Tavily's JavaScript SDK allows for easy interaction with the Tavily API, offering the full range of our search and extract functionalities d…”
- [claimed-docs] “Environment Requests per minute (RPM) Development 100 Production 1,000”
- [claimed-docs] “Get API key and account usage details”
- [claimed-docs] “Retrieve per-request usage logs for the API keys under your account or organization.”
- [github] “You can try Tavily without an API key. Instantiate `TavilyClient()` with no arguments and the SDK runs in keyless mode against the public Ta…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.tavily.com/openapi.json, https://docs.tavily.com/swagger.json, https://docs.tavily.com/…”
Perplexity 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": [”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnTavilynone0/10Evidence shows API-key authentication, project IDs and session/user identifiers for usage attribution, but nothing about issuing scoped or least-privilege credentials (e.g., read-only keys, permission-restricted keys, per-tool key scoping) for agents. missing for 10: any documentation of restricted-permission API keys, role/scope-based key creation, or agent-specific least-privilege credential issuance.
- [claimed-docs] “You can attach a Project ID to your client to organize and track API usage by project. This is useful when a single API key is used across m…”
- [claimed-docs] “You can attach session and user identifiers to your client for attribution and analytics across multi-step interactions and agent workflows.”
- [claimed-docs] “Get API key and account usage details”
Perplexity 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.
ai-native userBuild against official SDKs
weight 2 · round to TavilyTavily ships official Python and JavaScript SDKs with rich, documented functionality (search, extract, crawl, map, research, QnA, RAG context) via pip/npm install and quick-start guides, plus reference docs covering auth, rate limits, project/session attribution, and proxy config. Missing for 10: independent/third-party corroboration beyond vendor docs and GitHub repo, and no official OpenAPI spec was found (probe returned 404s).
- [claimed-docs] “pip install tavily-python”
- [claimed-docs] “The Python SDK allows for easy interaction with the Tavily API, offering the full range of our search functionality directly from your Pytho…”
- [claimed-docs] “Tavily's JavaScript SDK allows for easy interaction with the Tavily API, offering the full range of our search and extract functionalities d…”
- [claimed-docs] “tavily_client = TavilyClient(api_key="tvly-YOUR_API_KEY") response = tavily_client.search("Who is Leo Messi?")”
- [claimed-docs] “response = tavily_client.crawl("https://docs.tavily.com", instructions="Find all pages on the Python SDK")”
- [claimed-docs] “response = tavily_client.map("https://docs.tavily.com")”
- [claimed-docs] “response = tavily_client.research("What are the latest developments in AI?")”
- [github] “Instantiate `TavilyClient()` with no arguments and the SDK runs in keyless mode against the public Tavily API. Keyless mode supports `search…”
- [claimed-docs] “You can attach a Project ID to your client to organize and track API usage by project. This is useful when a single API key is used across m…”
- [claimed-docs] “You can attach session and user identifiers to your client for attribution and analytics across multi-step interactions and agent workflows.”
- [claimed-docs] “If you would like to specify a proxy to be used when making requests, you can do so by passing in a proxy parameter on client instantiation.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.tavily.com/openapi.json, https://docs.tavily.com/swagger.json, https://docs.tavily.com/…”
Docs 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)”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnTavilynone0/10Tavily's evidence pack covers search, extract, crawl, map, research APIs, SDKs, and an MCP server, but there is no mention of webhooks or event subscription mechanisms anywhere in the docs, GitHub, or probes; async research status must be polled via request ID rather than pushed via webhook.
- [claimed-docs] “Retrieve the status and results of a research task using its request ID.”
- [claimed-docs] “When using the Tavily Research API, you can stream responses in real-time by setting `stream: true` in your request.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.tavily.com/llms.txt # Tavily Docs > Tavily is the web layer for AI agents: real-time web search, c…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.tavily.com/openapi.json, https://docs.tavily.com/swagger.json, https://docs.tavily.com/…”
Agentic features
ai-native userOperate the product with natural-language commands
weight 2 · round to Perplexity Sonar APITavily's API accepts natural-language queries (search, research, crawl instructions) and its MCP server plus CLI (tvly search/extract/crawl/research) let AI-native users invoke it via natural-language-like commands rather than rigid syntax; instructions like crawl's 'Find all pages on the Python SDK' show NL-driven parameterization. missing for 10: no evidence of a true conversational/chat interface parsing arbitrary free-form user commands end-to-end, and no independent/hands-on verification beyond vendor docs and github readme.
- [claimed-docs] “tavily_client.crawl("https://docs.tavily.com", instructions="Find all pages on the Python SDK")”
- [claimed-docs] “response = tavily_client.crawl("https://docs.tavily.com", instructions="Find all pages on the Python SDK")”
- [claimed-docs] “tvly search "latest AI news" tvly extract "https://example.com" tvly crawl "https://docs.example.com" --depth 2 tvly research "compare React…”
- [claimed-docs] “The Tavily MCP server provides: Seamless interaction with the tavily-search and tavily-extract tools”
- [probe] “official MCP server documented at https://docs.tavily.com/documentation/mcp”
- [github] “Tavily Research Research lets you create comprehensive research reports on any topic, with aut”
The 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.”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to Perplexity Sonar APITavily has a documented API reference with endpoint pages (search, extract, crawl, map, research) and code snippets, but there's no confirmed interactive/runnable console—an openapi.json probe returned 404s across candidate paths, suggesting no standard interactive spec-driven explorer. missing for 10: evidence of an actual interactive 'try it' console or sandbox with live runnable requests, a discoverable OpenAPI/Swagger spec, and independent confirmation of interactivity beyond static code examples.
- [claimed-docs] “Execute a search query using Tavily Search.”
- [claimed-docs] “Extract content from one URL or batch up to 20 URLs in one request. Successful URLs appear in results; per-URL failures appear in failed_res…”
- [claimed-docs] “Tavily Crawl is a graph-based website traversal tool that can explore hundreds of paths in parallel with built-in extraction and intelligent…”
- [claimed-docs] “Tavily Map traverses websites like a graph and can explore hundreds of paths in parallel with intelligent discovery to generate comprehensiv…”
- [claimed-docs] “Tavily Research performs comprehensive research on a given topic by conducting multiple searches, analyzing sources, and generating a detail…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.tavily.com/openapi.json, https://docs.tavily.com/swagger.json, https://docs.tavily.com/…”
Docs 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…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to Perplexity Sonar APITavilynone0/10Tavily has detailed API reference docs but an explicit probe for standard OpenAPI/Swagger spec locations (openapi.json, swagger.json, etc.) returned 404s, and no evidence pack item points to a downloadable machine-readable spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.tavily.com/openapi.json, https://docs.tavily.com/swagger.json, https://docs.tavily.com/…”
A 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…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to TavilyDocs mention distinct 'Development' vs 'Production' rate-limit tiers/keys (implying separate environments) and a keyless mode to try the API without an account, which together hint at a way to test without full production access, but there is no explicit sandbox environment, mock data, or isolation-from-production-data guarantee documented. missing for 10: explicit sandbox/test-mode documentation, confirmation that development keys don't touch live production data or billing, and any hands-on/independent corroboration.
- [claimed-docs] “Environment Requests per minute (RPM) Development 100 Production 1,000”
- [claimed-docs] “`Production` 1,000”
- [github] “Instantiate `TavilyClient()` with no arguments and the SDK runs in keyless mode against the public Tavily API. Keyless mode supports `search…”
- [github] “You can try Tavily without an API key. Instantiate `TavilyClient()` with no arguments and the SDK runs in keyless mode against the public Ta…”
- [github] “You can try Tavily without an API key. Instantiate `TavilyClient()` with no arguments and the SDK runs in keyless mode against the public Ta…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnTavilynone0/10No evidence of API versioning scheme (e.g., v1/v2 paths) or any documented deprecation policy; OpenAPI spec probes returned 404s and no changelog/deprecation docs appear in the evidence pack.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.tavily.com/openapi.json, https://docs.tavily.com/swagger.json, https://docs.tavily.com/…”
Perplexity 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.
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 TavilyTavily explicitly supports bulk operations: Extract can batch up to 20 URLs per request, and Crawl/Map can traverse and explore hundreds of paths in parallel graph-based traversal, plus Research performs multi-search comprehensive reports with async status retrieval. These directly satisfy 'bulk operations across many items' for an AI-native/automation use case. Missing for 10: no documented bulk/batch search across many queries in one call, and no independent hands-on benchmark confirming throughput at scale beyond vendor docs.
- [claimed-docs] “Extract content from one URL or batch up to 20 URLs in one request. Successful URLs appear in results; per-URL failures appear in failed_res…”
- [claimed-docs] “Tavily Crawl is a graph-based website traversal tool that can explore hundreds of paths in parallel with built-in extraction and intelligent…”
- [claimed-docs] “Tavily Map traverses websites like a graph and can explore hundreds of paths in parallel with intelligent discovery to generate comprehensiv…”
- [claimed-docs] “Tavily Research performs comprehensive research on a given topic by conducting multiple searches, analyzing sources, and generating a detail…”
- [claimed-docs] “Retrieve the status and results of a research task using its request ID.”
- [github] “Crawl lets you traverse a website's content starting from a base URL.”
- [github] “Tavily Research Research lets you create comprehensive research reports on any topic, with aut”
The 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.”
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 APITavilynone0/10The evidence describes Tavily's search/extract/crawl endpoints and SDKs but never documents the actual result schema (URL, title, published date fields) returned by search results, so there's no evidence supporting reliable citation metadata for developers to build accurate citations.
Docs 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.”
data engineerRead a documented stance on robots.txt, content licensing, and permitted use of results
weight 2 · round drawnTavilynone0/10No evidence pack item documents Tavily's stance on robots.txt compliance, content licensing of crawled/extracted data, or permitted use of search/crawl results; only a general note about security/privacy validation layers (tavily-docs-18) touches trust but not this specific axis.
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 drawnTavily's single API/SDK exposes search, extract, crawl/map, and a dedicated research endpoint that itself performs multiple searches, source analysis, and report synthesis (tavily-docs-4,13,26,27,29), all accessible through one client/API key. This directly matches a multi-step search→extract→synthesize research flow callable by an agent. Missing for 10: independent/hands-on third-party validation of the research endpoint's synthesis quality and no evidence of chaining search+extract+research in a single documented end-to-end example.
- [claimed-docs] “tavily_client.research("What are the latest developments in AI?")”
- [claimed-docs] “response = tavily_client.research("What are the latest developments in AI?")”
- [claimed-docs] “Tavily Research performs comprehensive research on a given topic by conducting multiple searches, analyzing sources, and generating a detail…”
- [claimed-docs] “"mini" is optimized for targeted, efficient research and works best for narrow or well-scoped questions. "pro" provides comprehensive, multi…”
- [claimed-docs] “When using the Tavily Research API, you can stream responses in real-time by setting `stream: true` in your request.”
- [claimed-docs] “Extract web page content from one or more specified URLs using Tavily Extract.”
- [claimed-docs] “Execute a search query using Tavily Search.”
- [github] “Tavily Research Research lets you create comprehensive research reports on any topic, with aut”
The 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.”
Page contents
developerRetrieve full page text or markdown for results, not just snippets
weight 3 · round to TavilyTavily Extract explicitly retrieves full page content (not just snippets) from one or more URLs, batching up to 20 per request, and is documented as a distinct endpoint separate from Search snippets; SDKs and MCP server expose this extract capability directly. Missing for 10: explicit confirmation of markdown-formatted output vs raw text, and independent third-party verification of extraction fidelity.
- [claimed-docs] “Extract web page content from one or more specified URLs using Tavily Extract.”
- [claimed-docs] “Extract content from one URL or batch up to 20 URLs in one request. Successful URLs appear in results; per-URL failures appear in failed_res…”
- [github] “Instantiate `TavilyClient()` with no arguments and the SDK runs in keyless mode against the public Tavily API. Keyless mode supports `search…”
- [claimed-docs] “The Tavily MCP server provides: * Seamless interaction with the tavily-search and tavily-extract tools”
Docs 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.”
developerGet structured output matching a JSON schema I define
weight 2 · round to Perplexity Sonar APITavilynone0/10No evidence in the pack mentions a JSON-schema-based structured output feature, response schema parameter, or Pydantic/type-safe output validation for search/extract/crawl/research endpoints; responses appear to be fixed JSON shapes rather than developer-defined schemas.
Docs 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.”
data engineerCrawl subpages or entire sites starting from a search result
weight 1 · round to TavilyTavily Crawl explicitly traverses a website's content starting from a base URL with graph-based parallel exploration and intelligent discovery, and Map generates full site maps similarly, both documented with SDK examples (tavily_client.crawl(...), tavily_client.map(...)). This directly satisfies crawling subpages/entire sites from a starting URL. Missing for 10: no independent/hands-on verification beyond vendor docs and GitHub README, and no explicit example of crawling starting directly from a search result URL (only from an arbitrary base URL).
- [github] “Crawl lets you traverse a website's content starting from a base URL.”
- [claimed-docs] “Tavily Crawl is a graph-based website traversal tool that can explore hundreds of paths in parallel with built-in extraction and intelligent…”
- [claimed-docs] “response = tavily_client.crawl("https://docs.tavily.com", instructions="Find all pages on the Python SDK")”
- [claimed-docs] “tavily_client.crawl("https://docs.tavily.com", instructions="Find all pages on the Python SDK")”
- [github] “Map lets you discover and visualize the structure of a website starting from a base URL.”
- [claimed-docs] “Tavily Map traverses websites like a graph and can explore hundreds of paths in parallel with intelligent discovery to generate comprehensiv…”
- [claimed-docs] “response = tavily_client.map("https://docs.tavily.com")”
Perplexity 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.”
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 to Perplexity Sonar APITavilynone0/10The evidence pack never mentions domain include/exclude filtering (no 'include_domains' or 'exclude_domains' parameters, or any similar filter) anywhere in the docs, SDK, or API reference excerpts provided; it only covers exact_match, crawl/map depth, research modes, and rate limits.
Docs 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.”
developerRead per-result relevance scores to threshold what enters my pipeline
weight 1 · round drawnTavilynone0/10The evidence pack describes Tavily's search, extract, crawl, map, and research endpoints but never mentions a relevance/score field returned per result that a developer could use to threshold results. Missing for 10: any documentation of a numeric relevance score in the search response schema, and any guidance on filtering/thresholding by that score.
- [claimed-docs] “Execute a search query using Tavily Search.”
- [github] “Use exact_match=True to only return results containing the exact phrase(s) inside quotes”
Perplexity 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 APITavilynone0/10The evidence pack covers Tavily's search, extract, crawl, map, and research endpoints, rate limits, and MCP integration, but contains no mention of date-range parameters, recency/freshness filters, or index update frequency. Missing for 10: explicit date-range/time_range search parameters, recency filter documentation, and any claim about index freshness or update cadence.
- [claimed-docs] “Execute a search query using Tavily Search.”
- [github] “Use exact_match=True to only return results containing the exact phrase(s) inside quotes”
- [claimed-docs] “tavily_client.search("Who is Leo Messi?")”
Docs 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.”
data engineerQuery dedicated verticals like news, images, or finance through specific endpoints or category filters
weight 2 · round to Perplexity Sonar APITavilynone0/10The evidence pack describes Tavily's generic search, extract, crawl, map, and research endpoints, but nowhere mentions vertical-specific categories or filters such as news, images, or finance. Missing for 10: any documentation of a topic/category parameter (e.g., topic=news/finance), dedicated vertical endpoints, or image-specific search options.
- [claimed-docs] “Execute a search query using Tavily Search.”
- [claimed-docs] “tavily_client.search("Who is Leo Messi?")”
- [github] “Map lets you discover and visualize the structure of a website starting from a base URL.”
Docs 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.”
Targeting
data engineerLocalize results by country, language, or location parameters
weight 2 · round drawnTavilynone0/10The evidence pack documents search, extract, crawl, map, research, and MCP capabilities but never mentions country, language, or geo-location filtering/localization parameters for search results. missing for 10: any documented country/language/location parameter, evidence of localized result sets, or docs referencing geographic targeting.
Perplexity 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.
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 TavilyTavily's core functionality (search, extract, crawl, map, research, Q&A, RAG context) is fully exposed through the API/SDKs, and CLI/MCP integrations mirror this, suggesting the API is the primary interface with no UI-only features documented. However, there's no explicit comparison confirming full UI-API parity, and no public OpenAPI spec was found (404 on all probed paths), leaving some doubt about completeness of self-service API discovery. Missing for 10: explicit UI feature list to compare against API, and a public OpenAPI/swagger spec for full endpoint parity verification.
- [claimed-docs] “tavily_client.search("Who is Leo Messi?")”
- [claimed-docs] “Extract web page content from one or more specified URLs using Tavily Extract.”
- [claimed-docs] “tavily_client.crawl("https://docs.tavily.com", instructions="Find all pages on the Python SDK")”
- [claimed-docs] “tavily_client.research("What are the latest developments in AI?")”
- [github] “Map lets you discover and visualize the structure of a website starting from a base URL.”
- [github] “context = tavily_client.get_search_context(query="What happened during the Burning Man floods?")”
- [github] “answer = tavily_client.qna_search(query="Who is Leo Messi?")”
- [claimed-docs] “Execute a search query using Tavily Search.”
- [claimed-docs] “Extract content from one URL or batch up to 20 URLs in one request. Successful URLs appear in results; per-URL failures appear in failed_res…”
- [claimed-docs] “Tavily Crawl is a graph-based website traversal tool that can explore hundreds of paths in parallel with built-in extraction and intelligent…”
- [claimed-docs] “Tavily Map traverses websites like a graph and can explore hundreds of paths in parallel with intelligent discovery to generate comprehensiv…”
- [claimed-docs] “Tavily Research performs comprehensive research on a given topic by conducting multiple searches, analyzing sources, and generating a detail…”
- [claimed-docs] “tvly search "latest AI news" tvly extract "https://example.com" tvly crawl "https://docs.example.com" --depth 2 tvly research "compare React…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.tavily.com/openapi.json, https://docs.tavily.com/swagger.json, https://docs.tavily.com/…”
The 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 …”
ai-native userRead the product's source under an open license
weight 2 · round drawnTavilynone0/10Tavily is a closed, hosted API/SaaS service; while a Python SDK client repo exists on GitHub, the evidence never states any open-source license or exposes the core Tavily service/backend source code. Missing for 10: explicit license grant, access to backend/service source, any statement of open-sourcing the core product.
Perplexity 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.
ai-native userSelf-host the core product
weight 3 · round drawnTavilynone0/10Tavily is offered exclusively as a hosted API/SaaS product (API keys, rate limits, pricing tiers, keyless mode against the 'public Tavily API') with no evidence of a self-hostable core engine, on-prem deployment option, or open-source server code.
- [claimed-docs] “1,000 API credits / month ... No credit card required”
- [github] “Instantiate `TavilyClient()` with no arguments and the SDK runs in keyless mode against the public Tavily API. Keyless mode supports `search…”
- [claimed-docs] “Environment Requests per minute (RPM) Development 100 Production 1,000”
Perplexity 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…”
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 drawnTavily's docs explicitly state RPM caps for Development (100) vs Production (1,000) environments, describe 429/retry-after behavior, and the pricing page shows a self-serve free tier and usage-based paid plans with a usage/logs API to track consumption — together implying a self-serve upgrade path from dev to production limits. However, there is no explicit concurrency-cap documentation or a clearly described step-by-step upgrade workflow beyond the environment distinction. Missing for 10: explicit concurrency limits, a documented step-by-step self-serve upgrade/billing flow.
- [claimed-docs] “the API returns a `429 Too Many Requests` response with a `retry-after` header indicating the number of seconds to wait before making anothe…”
- [claimed-docs] “Environment Requests per minute (RPM) Development 100 Production 1,000”
- [claimed-docs] “`Production` 1,000”
- [claimed-docs] “1,000 API credits / month No credit card required”
- [claimed-docs] “Get API key and account usage details”
- [claimed-docs] “Retrieve per-request usage logs for the API keys under your account or organization.”
- [claimed-docs] “1,000 API credits / month ... No credit card required”
- [claimed-docs] “You get 1,000 free API Credits every month. **No credit card required.**”
Docs 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…”
developerPrototype against the API on a free tier or free credits
weight 2 · round to TavilyTavily offers 1,000 free API credits/month with no credit card required, plus a keyless SDK mode for search/extract to try before signing up, and clear rate limits for development tier prototyping. missing for 10: no independent/community corroboration of the free-tier experience beyond vendor docs.
- [claimed-docs] “1,000 API credits / month ... No credit card required”
- [claimed-docs] “1,000 API credits / month No credit card required”
- [claimed-docs] “You get 1,000 free API Credits every month. **No credit card required.**”
- [github] “Instantiate `TavilyClient()` with no arguments and the SDK runs in keyless mode against the public Tavily API. Keyless mode supports `search…”
- [github] “You can try Tavily without an API key. Instantiate `TavilyClient()` with no arguments and the SDK runs in keyless mode against the public Ta…”
- [github] “You can try Tavily without an API key. Instantiate `TavilyClient()` with no arguments and the SDK runs in keyless mode against the public Ta…”
- [claimed-docs] “Environment Requests per minute (RPM) Development 100 Production 1,000”
Perplexity 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…”
developerSee clear per-request or per-credit pricing without talking to sales
weight 3 · round drawnTavily's public pricing page confirms a self-serve, no-sales-required model: 1,000 free API credits/month with no credit card required and a 'pay only for what you use' model. However, the evidence pack does not show an explicit per-request/per-credit cost table or endpoint-specific credit pricing breakdown, so the exact cost transparency is only partially demonstrated. Missing for 10: a detailed per-endpoint credit-cost table, tier pricing breakdown beyond the free tier.
- [claimed-docs] “1,000 API credits / month ... No credit card required”
- [claimed-docs] “Pay only for what you use”
- [claimed-docs] “1,000 API credits / month No credit card required”
- [claimed-docs] “You get 1,000 free API Credits every month. **No credit card required.**”
Perplexity 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.”
Scale throughput
data engineerSubmit batched or asynchronous jobs for high-volume query workloads
weight 2 · round to TavilyTavily's Research endpoint supports async job submission with request-ID based status polling and streaming, and Extract supports batching up to 20 URLs per request; rate-limit docs show RPM tiers and 429/retry-after handling for high-volume workloads. However there's no dedicated bulk/batch job queue for Search itself, no webhook/callback pattern for large offline jobs, and no explicit high-volume batch pricing guidance beyond per-credit usage. Missing for 10: a true batch-submission API for search queries, webhook/callback support for async job completion, and documented guidance/pricing for large-scale batch workloads.
- [claimed-docs] “Tavily Research performs comprehensive research on a given topic by conducting multiple searches, analyzing sources, and generating a detail…”
- [claimed-docs] “Retrieve the status and results of a research task using its request ID.”
- [claimed-docs] “When using the Tavily Research API, you can stream responses in real-time by setting `stream: true` in your request.”
- [claimed-docs] “Extract content from one URL or batch up to 20 URLs in one request. Successful URLs appear in results; per-URL failures appear in failed_res…”
- [claimed-docs] “the API returns a `429 Too Many Requests` response with a `retry-after` header indicating the number of seconds to wait before making anothe…”
- [claimed-docs] “Environment Requests per minute (RPM) Development 100 Production 1,000”
Perplexity 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.
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 drawnTavilynone0/10No evidence in the pack mentions data residency, regional storage options, or geographic control over where data is processed/stored; only security/privacy filtering (PII blocking) is mentioned, not data residency choice. Missing for 10: any mention of region selection, data residency guarantees, or geo-specific deployment options.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnTavilynone0/10No evidence pack item addresses training-data opt-out or a policy preventing customer data from being used to train AI models; only PII/security filtering is mentioned, which is unrelated to model-training data usage.
ai-native userControl data retention and deletion
weight 2 · round drawnTavilynone0/10No evidence in the pack addresses data retention policies, deletion controls, or user ability to manage stored data/logs beyond usage logging mentions; nothing documents a deletion/export mechanism.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnTavilynone0/10No evidence Tavily documents any telemetry/usage-tracking opt-out mechanism; the only related docs (tavily-docs-33, tavily-docs-34) describe optional session/user/project identifiers for analytics attribution, not a way to disable tracking. Missing for 10: any documented telemetry opt-out setting, privacy policy language on data collection, or configuration flag to disable analytics.
- [claimed-docs] “You can attach a Project ID to your client to organize and track API usage by project. This is useful when a single API key is used across m…”
- [claimed-docs] “You can attach session and user identifiers to your client for attribution and analytics across multi-step interactions and agent workflows.”
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 drawnTavily ships SDKs (Python/JS) designed explicitly for LLM/agent consumption (qna_search 'perfect for usage by LLMs', get_search_context for direct RAG feeding), plus an official MCP server compatible with any MCP client for tool-call integration, and clear API reference/OpenAPI-style endpoint docs for search/extract/crawl/map/research. missing for 10: no discoverable OpenAPI/JSON schema spec (probe found 404s) and no explicit named framework integrations (e.g., LangChain/LlamaIndex tool classes) cited in evidence.
- [github] “This is how you get accurate and concise answers to questions, in one line of code. Perfect for usage by LLMs!”
- [github] “you now have a context string that you can feed directly into your RAG Application”
- [claimed-docs] “The Tavily MCP server provides: * Seamless interaction with the tavily-search and tavily-extract tools”
- [claimed-docs] “Compatible with both Cursor and Claude Desktop! Tavily MCP is also compatible with any MCP client.”
- [claimed-docs] “The Python SDK allows for easy interaction with the Tavily API, offering the full range of our search functionality directly from your Pytho…”
- [claimed-docs] “Tavily's JavaScript SDK allows for easy interaction with the Tavily API, offering the full range of our search and extract functionalities d…”
- [probe] “official MCP server documented at https://docs.tavily.com/documentation/mcp”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.tavily.com/openapi.json, https://docs.tavily.com/swagger.json, https://docs.tavily.com/…”
Perplexity 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…”
Llm ready results
developerGet a sourced, LLM-generated answer to a query in a single API call
weight 2 · round to Perplexity Sonar APITavily's qna_search (and its underlying Q&A search_depth) returns a single, sourced, LLM-generated direct answer in one API call, explicitly described as 'accurate and concise answers to questions, in one line of code. Perfect for usage by LLMs.' The search endpoint also supports an include_answer option returning a synthesized answer alongside sources. Missing for 10: no independent third-party benchmark of answer quality/accuracy, and no explicit example showing the 'answer' field returned alongside source URLs in the same response payload.
- [github] “answer = tavily_client.qna_search(query="Who is Leo Messi?")”
- [github] “This is how you get accurate and concise answers to questions, in one line of code. Perfect for usage by LLMs!”
- [claimed-docs] “tavily_client.search("Who is Leo Messi?")”
- [claimed-docs] “Execute a search query using Tavily Search.”
Docs 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.”
developerGet results sized and ranked for direct use as LLM context in a RAG pipeline
weight 3 · round drawnTavily's get_search_context explicitly produces a context string sized for direct RAG use ('you now have a context string that you can feed directly into your RAG Application'), and qna_search is described as tuned for concise LLM-consumable answers; docs also describe content validation layers improving result quality. missing for 10: no independent/third-party benchmark of ranking quality or context sizing tradeoffs beyond first-party claims.
- [github] “you now have a context string that you can feed directly into your RAG Application”
- [github] “context = tavily_client.get_search_context(query="What happened during the Burning Man floods?")”
- [github] “This is how you get accurate and concise answers to questions, in one line of code. Perfect for usage by LLMs!”
- [claimed-docs] “Requests pass through security, privacy, and content validation layers that block PII leakage, prompt injection, and malicious sources.”
Docs 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": [”
Retrieval modes
developerFind pages similar to a URL I already have
weight 1 · round drawnTavilynone0/10Tavily's evidence shows search (query-based), extract, crawl, and map (both traverse a site's own link structure from a base URL) but no capability to find other pages on the web that are semantically/topically similar to a given URL, which is the actual ask here. Crawl/Map only discover pages within the same site's domain, not similar external content.
- [github] “Crawl lets you traverse a website's content starting from a base URL.”
- [claimed-docs] “Tavily Crawl is a graph-based website traversal tool that can explore hundreds of paths in parallel with built-in extraction and intelligent…”
- [github] “Map lets you discover and visualize the structure of a website starting from a base URL.”
- [claimed-docs] “Tavily Map traverses websites like a graph and can explore hundreds of paths in parallel with intelligent discovery to generate comprehensiv…”
developerChoose between keyword, neural, or hybrid retrieval modes per query
weight 2 · round drawnTavilynone0/10The evidence pack shows Tavily's search API supports exact-phrase matching (exact_match=True) but there is no documentation of selectable retrieval modes such as keyword vs neural vs hybrid search per query.
- [github] “Use exact_match=True to only return results containing the exact phrase(s) inside quotes”
developerRun meaning-based semantic search that finds results keyword engines miss
weight 3 · round to Perplexity Sonar APITavily's search API accepts natural-language queries (e.g., 'Who is Leo Messi?') and the existence of an `exact_match=True` flag implies the default behavior is not strict keyword matching, suggesting some meaning-based ranking. However, no evidence explicitly documents embeddings, semantic ranking, or a comparison showing it surfaces results keyword search misses. Missing for 10: explicit documentation of semantic/embedding-based ranking methodology, benchmark or example showing recall beyond keyword search, and independent corroboration of search-quality claims.
- [claimed-docs] “tavily_client.search("Who is Leo Messi?")”
- [github] “Use exact_match=True to only return results containing the exact phrase(s) inside quotes”
- [github] “answer = tavily_client.qna_search(query="Who is Leo Messi?")”
- [github] “you now have a context string that you can feed directly into your RAG Application”
Docs 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.”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableTavilyn/aTavily is a web-data/API service (search, extract, crawl, map, research) that itself ships an official MCP server so agents can call ITS tools — the evidence never positions Tavily as an agent/orchestrator that consumes other MCP servers' tools. Plugging external MCP servers into a product only applies to agent hosts/orchestration platforms, not to a tool/API provider like Tavily, so this client-role axis is a category mismatch.
- [claimed-docs] “The Tavily MCP server provides: Seamless interaction with the tavily-search and tavily-extract tools”
- [claimed-docs] “The Tavily MCP server provides: * Seamless interaction with the tavily-search and tavily-extract tools”
- [claimed-docs] “Compatible with both [Cursor](https://cursor.sh) and [Claude Desktop](https://claude.ai/download)! Tavily MCP is also compatible with any MC…”
- [probe] “official MCP server documented at https://docs.tavily.com/documentation/mcp”
Perplexity 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`…”
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · not comparableTavilyn/aTavily is a web-search/extraction/crawling API infrastructure for building AI agents, not a data platform where a user's own stored data is analyzed to surface in-product insights or suggestions; its 'research'/'search' outputs are AI-generated summaries of external web content, not analysis of a user's own data within a product UI. This axis is a category mismatch for an API/SDK product rather than an applicable-but-unmet capability.
Sonar 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.”
ai-native userSet up automations that run autonomously in the background
weight 2 · not comparableTavilyn/aTavily is a web search/extraction/crawl API and MCP server for agents to call as a tool; it provides no scheduling, triggers, or background automation/orchestration capability of its own. Setting up autonomous background automations is a workflow/orchestration platform concern, not something this API product category addresses.
Perplexity 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.
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableTavilyn/aTavily is a web-search/data API and SDK toolkit that other AI agents call into (search, extract, crawl, map, research), not a product with its own embedded AI assistant UI that a user delegates tasks to. The evidence shows Tavily as a tool provider for external agents/MCP clients, not as an agent itself — this axis is a category mismatch for this product type.
The 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 comparableTavilyn/aTavily is a web search/extraction/research API and MCP toolset for AI agents, not an automation/rules-engine platform; there is no concept of user-defined triggers or event-driven actions in its evidence. This is a category mismatch rather than a missing feature.
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableTavilyn/aTavily is a search/extraction/research API and MCP toolset for agents, not a scheduler or workflow orchestrator; scheduling recurring jobs is outside its product category (it provides synchronous/async request-response endpoints, not cron-like automation).
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableTavilyn/aTavily is a web search/extraction/crawling API and MCP tool, not an automation/workflow builder with configurable automations to version or roll back — this axis is a category error for this product type.
Perplexity'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 comparableTavilynone0/10Tavily's docs show usage/logs endpoints (tavily-docs-30, tavily-docs-31) for tracking API usage, but there is no evidence of a comprehensive data export feature, open-format data dumps, or account data portability mechanism that would let a user export all their data and leave the platform.
- [claimed-docs] “Get API key and account usage details”
- [claimed-docs] “Retrieve per-request usage logs for the API keys under your account or organization.”
Perplexity 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.