{ "data": { "a": { "slug": "parallel-search-api", "name": "Parallel Search and Task APIs", "vendor": "Parallel Web Systems", "vendorUrl": "https://parallel.ai", "kind": "http-api", "category": "search", "summary": "Parallel's web APIs for agents, covering search, page extraction, asynchronous research tasks, closed-ended decisions answered from current web evidence and an OpenAI-compatible Responses endpoint, with hosted Search and Task MCP servers.", "url": "https://www.anchorterminal.com/tools/parallel-search-api", "markdownUrl": "https://www.anchorterminal.com/tools/parallel-search-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/parallel-search-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/parallel-search-api.json", "dns": "parallel-search-api.grade.anchorterminal.com", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.parallel.ai/v1/search", "packages": [ { "registry": "npm", "name": "parallel-web" }, { "registry": "pypi", "name": "parallel-web" } ], "auth": "mixed", "authNotes": "API key in the `x-api-key` header. The Search MCP at search.parallel.ai/mcp works anonymously at lower limits, takes a Bearer key, and /mcp-oauth adds OAuth. An OAuth provider can issue keys on behalf of your users.", "pricing": "freemium", "pricingNotes": "Up to 5,000 free requests a month, with $5 of free credit monthly and up to $80 at signup. Search $1 per 1,000 requests in turbo or fast, $5 in basic or advanced, 10 results included and $1 per 1,000 extra results. Image Search $1 (fast) or $5 (advanced) per 1,000, up to 20 results. Extract $1 per 1,000 URLs. Task $5 (lite) to $2,400 (ultra8x) per 1,000 successful runs. Responses $10 to $250 per 1,000 by reasoning effort. Decisions $1 per 1,000 requests, up to 100 questions a request. Failed runs aren't billed (https://parallel.ai/pricing).", "priceSummary": "$1 / 1k req", "where": "hosted", "x402": { "level": "partial", "evidence": "Not on api.parallel.ai. A separate gateway at parallelmpp.dev takes x402 (USDC on Base) and MPP (Stripe or Tempo) for search and extract at $0.01 and an ultra task at $0.30. An unauthenticated POST to /api/search returned 402 with an x402 v2 challenge for 10000 base units on eip155:8453 (checked 2026-09-30) (https://docs.parallel.ai/integrations/agentic-payments).", "endpoints": [ { "url": "https://parallelmpp.dev/api/search", "priceUsd": 0.01, "network": "eip155:8453" }, { "url": "https://parallelmpp.dev/api/extract", "priceUsd": 0.01, "network": "eip155:8453" }, { "url": "https://parallelmpp.dev/api/task", "priceUsd": 0.3, "network": "eip155:8453" } ] }, "toolCount": 6, "popularity": { "githubStars": 28, "npmWeekly": 249803, "pypiWeekly": 994376, "asOf": "2026-09-30" }, "docsUrl": "https://docs.parallel.ai", "llmsTxt": "https://docs.parallel.ai/llms.txt", "openapi": "https://docs.parallel.ai/public-openapi.json", "registryName": "ai.parallel/search-mcp", "capabilities": [ "web.search", "web.fetch", "web.extract", "search.answer", "search.research" ], "tags": [ "hosted", "freemium", "mcp", "llms-txt", "openapi", "x402", "python", "typescript", "async-jobs", "webhooks" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 75, "grade": "BB", "agentReady": true, "rank": 73, "ranked": true, "rankOf": 1486, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 87, "maintenance": 87, "payments": 75, "reliability": 75, "schema": 94, "security": 45, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Fast-mode search at $1 per 1,000 with 10 excerpted results, and a keyless two-tool Search MCP annotated read-only. Search defaults to advanced mode at $5 per 1,000 when `mode` is left out, and the Customer Terms allow training on inputs and outputs.", "bestFor": "Agents that mix quick search with long research or enrichment jobs and want one vendor and one bill.", "strengths": [ "Fast-mode search at $1 per 1,000 with 10 excerpted results, and Extract at $1 per 1,000 URLs", "Task runs billed only on success, and documented limits of 600 searches and 2,000 task creations a minute", "Keyless hosted MCP servers whose search, fetch and decision tools are annotated read-only, plus Bearer and OAuth sign-in", "Public OpenAPI, llms.txt and an errors table that says which codes to retry and how", "SDK releases several times a month, with CI and a breaking-change check on the Python SDK, and a dated changelog with entries on 19 and 26 October 2026" ], "weaknesses": [ "Search defaults to advanced mode at $5 per 1,000 when `mode` is left out", "SDKs retry Task creation on 429 and 5xx with no idempotency key", "x402 and MPP only through parallelmpp.dev at a flat $0.01, not on api.parallel.ai", "Customer Terms let Parallel train on inputs and outputs, and no retention period is stated outside the EU endpoint", "No prompt-injection guidance, no security.txt and no public subprocessor list" ], "agentNotes": [ "Pass `mode: \"fast\"` on every API search. Without it you pay the advanced rate. On an authenticated MCP connection, pin it with `?mode=fast`", "Create Task runs with `max_retries=0` and check for an existing run before retrying", "Give an `objective` plus two or three short `search_queries`. That's what ranks the excerpts", "On 402, check available balance rather than total. Running tasks reserve credit", "Ask for zero data retention or use the EU endpoint before sending private queries. The default terms allow training on them", "On Decisions, check each answer's `type` before reading it. A refusal is a 200, not an error, and a predicate is a probability you threshold yourself" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 3.6, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 75 } ], "editorialScores": { "ergonomics": 87, "maintenance": 87, "payments": 75, "reliability": 75, "schema": 94, "security": 45, "transparency": 45 }, "provenanceScore": 85, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-10-30", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.parallel.ai/v1/search -H \"x-api-key: $PARALLEL_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"mode\":\"fast\",\"objective\":\"Latest Parallel Web Systems announcements\",\"search_queries\":[\"Parallel Web Systems news\"]}'", "claudeCode": "claude mcp add --transport http parallel-search https://search.parallel.ai/mcp", "config": { "mcpServers": { "parallel-search": { "headers": { "Authorization": "Bearer ${PARALLEL_API_KEY}" }, "url": "https://search.parallel.ai/mcp" } } }, "x402": "curl -i -X POST https://parallelmpp.dev/api/search -H 'content-type: application/json' -d '{\"query\":\"test\"}'\n# 402 -\u003e pay $0.01 USDC on eip155:8453 (or MPP via Stripe/Tempo) -\u003e resend" }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/parallel-search-api" }, "area": "web-data", "unitPrices": [ { "item": "Search, turbo or fast", "unit": "1k-requests", "usd": 1, "note": "10 results included" }, { "item": "Search, basic or advanced", "unit": "1k-requests", "usd": 5, "note": "advanced is the default mode" }, { "item": "Extract", "unit": "1k-pages", "usd": 1 }, { "item": "Task, lite processor", "unit": "1k-calls", "usd": 5 }, { "item": "Task, pro processor", "unit": "1k-calls", "usd": 100 }, { "item": "Responses, medium effort", "unit": "1k-requests", "usd": 50 }, { "item": "Decisions, up to 100 questions a request", "unit": "1k-requests", "usd": 1, "note": "docs pricing page, 1 November 2026" }, { "item": "x402 search via gateway", "unit": "call", "usd": 0.01, "note": "parallelmpp.dev" } ], "provenance": { "legalEntity": "Parallel Web Systems Inc.", "domain": "parallel.ai", "domainRegistered": "2017-12-16", "domainNote": "Registered in 2017 and transferred on 2024-07-01, so the registration date predates the company's use of it.", "endpointOnVendorDomain": true, "terms": "https://parallel.ai/customer-terms", "privacy": "https://parallel.ai/privacy-policy", "statusPage": "https://status.parallel.ai", "changelog": "https://docs.parallel.ai/resources/changelog", "securityTxt": "none", "checked": "2026-11-01", "score": 85 }, "requirements": { "setupChecked": true, "complianceChecked": true, "agentAlone": true, "card": "unknown", "freeTier": true, "minutes": 5, "credential": "mixed", "hosting": [ "US", "EU" ], "euResidency": "enterprise", "trainsOnData": "unknown", "zeroRetention": "enterprise", "certifications": [ "GDPR" ], "dpa": true, "selfHost": "no" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/parallel-search-api.json", "live": { "slug": "parallel-search-api", "probe": { "target": "https://api.parallel.ai/v1/search", "method": "get", "lastAt": "2026-11-07T18:20:45.797474111Z", "lastOk": true, "lastStatus": 401, "lastMs": 1251, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 1156, "p95ms24h": 1251, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.parallel.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:52.770771808Z" }, "versions": [ { "registry": "mcp-registry", "name": "ai.parallel/search-mcp", "version": "1.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "parallel-web", "version": "1.3.7", "seenAt": "2026-11-06T23:54:39.327146641Z" }, { "registry": "pypi", "name": "parallel-web", "version": "1.3.7", "released": "2026-10-23", "seenAt": "2026-11-06T23:54:40.221328103Z" } ], "npmWeekly": 499802, "pypiWeekly": 1280811, "securityTxt": { "url": "https://parallel.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:47.651524803Z" }, "llmsTxt": { "url": "https://docs.parallel.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:35.374820292Z" }, "domain": { "domain": "parallel.ai", "registered": "2017-12-16", "source": "https://rdap.identitydigital.services/rdap/domain/parallel.ai", "checkedAt": "2026-11-01T14:08:31.990227623Z" }, "pages": [ { "url": "https://docs.parallel.ai/resources/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:25.166885545Z", "changedAt": "2026-11-06T13:29:46.487630215Z", "fingerprint": "64580beee981" }, { "url": "https://parallel.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:15:57.961317128Z", "changedAt": "2026-11-07T14:15:57.961317128Z", "fingerprint": "6907599c6534" }, { "url": "https://parallel.ai/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:15:59.73217133Z", "changedAt": "2026-11-06T13:37:39.393174208Z", "fingerprint": "4f0dd0d135d9" }, { "url": "https://parallel.ai/customer-terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:15:55.334035778Z", "changedAt": "2026-11-06T13:37:35.126347484Z", "fingerprint": "0f2621896abb" }, { "url": "https://parallel.ai/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-16T22:28:19.906253644Z", "changedAt": "2026-10-15T22:01:22.246898534Z", "fingerprint": "5d9bafee0ed2" } ], "mcpTools": { "url": "https://search.parallel.ai/mcp", "checkedAt": "2026-11-07T01:46:44.757089899Z", "status": "ok", "protocol": "2026-07-28", "tools": [ { "name": "web_search", "description": "Purpose: Perform web searches and return\nLLM-friendly results, including excerpts that are usually sufficient to\nanswer directly without a follow-up fetch.\n\nIdeal Use Cases:\n- Answering questions that require fresh or current information\n- Research, comparison, documentation, and troubleshooting questions\n- Broad tasks where multiple `search_queries` can be issued in a single call\n\nFor multiple independent objectives, make one web_search call per objective\nconcurrently. Put related query variations for the same objective in a single\ncall's search_queries list.\n", "inputSchema": { "properties": { "model_name": { "description": "The identifier of the LLM model making this tool call (e.g. 'claude-opus-4.7', 'gpt-5.5', 'gemini-2.5-pro'). Before the first call, verify the exact active model slug from trusted runtime/session metadata or active client configuration. Pass the full slug verbatim; never shorten or substitute a model-family alias like 'gpt-5'. Used for product analytics only; does not affect search behavior.", "maxLength": 100, "type": "string" }, "objective": { "description": "Natural-language description of what the web search is trying to find.\nTry to make the search objective atomic, looking for a specific piece of information. May include guidance about preferred sources or freshness.", "title": "Objective", "type": "string" }, "search_queries": { "description": "Concise keyword search queries, 3-6 words\neach. They may use site: with a bare domain (such as site:example.com), but\nnever a URL path after the domain and never quoted phrases. At least one query\nis required; provide 2-3 for best results. For broad tasks, you can include\nmultiple related queries in a single call instead of chaining web_search\ncalls. The queries should be related to the objective.", "items": { "type": "string" }, "title": "Search Queries", "type": "array" }, "session_id": { "description": "Stable identifier for the current conversation. Generate a random value (UUID or 32+ character hex string) at the start of your session and reuse the exact same value on every web_search / web_fetch call. Do NOT change it between turns. Used for free-tier rate limiting and correlating your tool calls in our logs; ignored on paid-tier keys.", "maxLength": 100, "type": "string" } }, "required": [ "objective", "search_queries" ], "title": "v1_search_toolArguments", "type": "object" }, "outputSchema": { "$defs": { "UsageItem": { "description": "Usage item for a single operation.", "properties": { "count": { "description": "Count of the SKU.", "examples": [ 1 ], "title": "Count", "type": "integer" }, "name": { "description": "Name of the SKU.", "examples": [ "sku_search", "sku_extract_excerpts" ], "title": "Name", "type": "string" } }, "required": [ "name", "count" ], "title": "UsageItem", "type": "object" }, "V1WebSearchResult": { "description": "A single search result from the web search API.", "properties": { "excerpts": { "description": "Relevant excerpted content from the URL, formatted as markdown.", "items": { "type": "string" }, "title": "Excerpts", "type": "array" }, "publish_date": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "description": "Publish date of the webpage in YYYY-MM-DD format, if available.", "title": "Publish Date" }, "title": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "description": "Title of the webpage, if available.", "title": "Title" }, "url": { "description": "URL associated with the search result.", "title": "Url", "type": "string" } }, "required": [ "url", "excerpts" ], "title": "V1WebSearchResult", "type": "object" }, "Warning": { "description": "Human-readable message for a task.", "properties": { "detail": { "anyOf": [ { "additionalProperties": true, "type": "object" }, { "type": "null" } ], "default": null, "description": "Optional detail supporting the warning.", "title": "Detail" }, "message": { "description": "Human-readable message.", "title": "Message", "type": "string" }, "type": { "description": "Type of warning. Note that adding new warning types is considered a backward-compatible change.", "enum": [ "spec_validation_warning", "input_validation_warning", "warning" ], "examples": [ "spec_validation_warning", "input_validation_warning" ], "title": "Type", "type": "string" } }, "required": [ "type", "message" ], "title": "Warning", "type": "object" } }, "description": "Search response.", "properties": { "results": { "description": "A list of search results, ordered by decreasing relevance.", "items": { "$ref": "#/$defs/V1WebSearchResult" }, "title": "Results", "type": "array" }, "search_id": { "description": "Search ID. Example: `search_cad0a6d2dec046bd95ae900527d880e7`", "title": "Search Id", "type": "string" }, "session_id": { "description": "Session identifier, echoed back from the request if provided, otherwise generated by the server. Should be passed to future search and extract calls made by the agent as part of the same larger task.", "examples": [ "session_8a911eb27c7a4afaa20d0d9dc98d07c0" ], "title": "Session Id", "type": "string" }, "usage": { "anyOf": [ { "items": { "$ref": "#/$defs/UsageItem" }, "type": "array" }, { "type": "null" } ], "default": null, "description": "Usage metrics for the search request.", "title": "Usage" }, "warnings": { "anyOf": [ { "items": { "$ref": "#/$defs/Warning" }, "type": "array" }, { "type": "null" } ], "default": null, "description": "Warnings for the search request, if any.", "title": "Warnings" } }, "required": [ "search_id", "results", "session_id" ], "title": "V1SearchResponse", "type": "object" }, "annotations": { "destructiveHint": false, "idempotentHint": true, "openWorldHint": true, "readOnlyHint": true, "title": "Web search" } }, { "name": "web_fetch", "description": "Purpose: Fetch and extract relevant content\nfrom specific web URLs. Use only when web_search excerpts are insufficient\nfor the task at hand.\n\nIdeal Use Cases:\n- The user asked about a specific URL or page\n- You need exact wording or quotes that excerpts may have truncated\n- You need full-page analysis (long article, document, or page structure)\n- web_search excerpts are conflicting or clearly insufficient to answer\n\nFor multiple independent extraction objectives, make separate web_fetch calls\nconcurrently. Put related URLs that share one objective in a single call.\n", "inputSchema": { "properties": { "allow_live_fetch": { "default": true, "description": "Whether live fetching is allowed. Leave\ntrue for the freshest available content. Set false to use cached content only,\nwhich makes web_fetch much faster by avoiding the source website, but may return\nolder content.", "title": "Allow Live Fetch", "type": "boolean" }, "full_content": { "default": false, "description": "Prefer leaving this off. The default\nexcerpt mode returns LLM-optimized snippets focused on your objective — they\nare much smaller, cheaper, and usually all you need. Only set to true when\nyou explicitly need the entire page as markdown (e.g. reading a long article\nin full, or running a document through a downstream summarizer).\n\nWarning: enabling full content can return a large amount of content —\noften tens of thousands of tokens for a long article. This may exceed your\nMCP client's tool-output limit and will substantially increase response\nsize and latency.", "title": "Full Content", "type": "boolean" }, "model_name": { "description": "The identifier of the LLM model making this tool call (e.g. 'claude-opus-4.7', 'gpt-5.5', 'gemini-2.5-pro'). Before the first call, verify the exact active model slug from trusted runtime/session metadata or active client configuration. Pass the full slug verbatim; never shorten or substitute a model-family alias like 'gpt-5'. Used for product analytics only; does not affect search behavior.", "maxLength": 100, "type": "string" }, "objective": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "description": "Natural-language description of what\ninformation you're looking for from the URLs. Limit to 200 characters.", "title": "Objective" }, "search_queries": { "anyOf": [ { "items": { "type": "string" }, "type": "array" }, { "type": "null" } ], "default": null, "description": "Optional keyword search queries (3-6\nwords each) used together with objective to focus excerpts on the most\nrelevant content. Pass the queries from the prior web_search call that\nsurfaced these URLs, if applicable.", "title": "Search Queries" }, "session_id": { "description": "Stable identifier for the current conversation. Generate a random value (UUID or 32+ character hex string) at the start of your session and reuse the exact same value on every web_search / web_fetch call. Do NOT change it between turns. Used for free-tier rate limiting and correlating your tool calls in our logs; ignored on paid-tier keys.", "maxLength": 100, "type": "string" }, "urls": { "description": "List of URLs to extract content from. Must be\nvalid HTTP/HTTPS URLs. Up to 20 URLs per request.", "items": { "type": "string" }, "title": "Urls", "type": "array" } }, "required": [ "urls" ], "title": "v1_extract_toolArguments", "type": "object" }, "outputSchema": { "$defs": { "ExtractError": { "description": "Extract error details.", "properties": { "content": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "description": "Content returned for http client or server errors, if any.", "title": "Content" }, "error_type": { "description": "Error type.", "title": "Error Type", "type": "string" }, "http_status_code": { "anyOf": [ { "type": "integer" }, { "type": "null" } ], "description": "HTTP status code, if available.", "title": "Http Status Code" }, "url": { "title": "Url", "type": "string" } }, "required": [ "url", "error_type", "http_status_code", "content" ], "title": "ExtractError", "type": "object" }, "UsageItem": { "description": "Usage item for a single operation.", "properties": { "count": { "description": "Count of the SKU.", "examples": [ 1 ], "title": "Count", "type": "integer" }, "name": { "description": "Name of the SKU.", "examples": [ "sku_search", "sku_extract_excerpts" ], "title": "Name", "type": "string" } }, "required": [ "name", "count" ], "title": "UsageItem", "type": "object" }, "V1ExtractResult": { "description": "Extract result for a single URL.", "properties": { "acquired_at": { "anyOf": [ { "format": "date-time", "type": "string" }, { "type": "null" } ], "default": null, "description": "When the returned content was acquired, as an RFC 3339 timestamp truncated to the start of the UTC day. Null when unknown.", "examples": [ "2026-10-08T00:00:00Z" ], "title": "Acquired At" }, "excerpts": { "description": "Relevant excerpted content from the URL, formatted as markdown.", "items": { "type": "string" }, "title": "Excerpts", "type": "array" }, "full_content": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "description": "Full content from the URL formatted as markdown, if requested.", "title": "Full Content" }, "links": { "anyOf": [ { "items": { "type": "string" }, "type": "array" }, { "type": "null" } ], "default": null, "description": "Links from the page's rendered content, if requested: up to 512 unique absolute URLs in document order. Empty for pages with no links, including PDFs. Present only when advanced_settings.links was requested.", "title": "Links" }, "publish_date": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "description": "Publish date of the webpage in YYYY-MM-DD format, if available.", "title": "Publish Date" }, "title": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "description": "Title of the webpage, if available.", "title": "Title" }, "url": { "description": "URL associated with the search result.", "title": "Url", "type": "string" } }, "required": [ "url", "excerpts" ], "title": "V1ExtractResult", "type": "object" }, "Warning": { "description": "Human-readable message for a task.", "properties": { "detail": { "anyOf": [ { "additionalProperties": true, "type": "object" }, { "type": "null" } ], "default": null, "description": "Optional detail supporting the warning.", "title": "Detail" }, "message": { "description": "Human-readable message.", "title": "Message", "type": "string" }, "type": { "description": "Type of warning. Note that adding new warning types is considered a backward-compatible change.", "enum": [ "spec_validation_warning", "input_validation_warning", "warning" ], "examples": [ "spec_validation_warning", "input_validation_warning" ], "title": "Type", "type": "string" } }, "required": [ "type", "message" ], "title": "Warning", "type": "object" } }, "description": "Extract response.", "properties": { "errors": { "description": "Extract errors: requested URLs not in the results.", "items": { "$ref": "#/$defs/ExtractError" }, "title": "Errors", "type": "array" }, "extract_id": { "description": "Extract request ID, e.g. `extract_cad0a6d2dec046bd95ae900527d880e7`", "title": "Extract Id", "type": "string" }, "results": { "description": "Successful extract results.", "items": { "$ref": "#/$defs/V1ExtractResult" }, "title": "Results", "type": "array" }, "session_id": { "description": "Session identifier. Echoed back from the request if provided, otherwise generated by the server. Should be passed to future search and extract calls made by the agent as part of the same larger task.", "examples": [ "session_8a911eb27c7a4afaa20d0d9dc98d07c0" ], "title": "Session Id", "type": "string" }, "usage": { "anyOf": [ { "items": { "$ref": "#/$defs/UsageItem" }, "type": "array" }, { "type": "null" } ], "default": null, "description": "Usage metrics for the extract request.", "title": "Usage" }, "warnings": { "anyOf": [ { "items": { "$ref": "#/$defs/Warning" }, "type": "array" }, { "type": "null" } ], "default": null, "description": "Warnings for the extract request, if any.", "title": "Warnings" } }, "required": [ "extract_id", "results", "errors", "session_id" ], "title": "V1ExtractResponse", "type": "object" }, "annotations": { "destructiveHint": false, "idempotentHint": true, "openWorldHint": true, "readOnlyHint": true, "title": "Web fetch" } }, { "name": "send_feedback", "description": "Report a problem with Parallel to the Parallel team. Use it when, while\nworking with Parallel, you see any of these:\n- A Parallel tool returned an error you didn't cause: a 5xx, a timeout, or a\n rate limit you didn't expect.\n- Results were wrong, irrelevant, stale or missing something you know exists:\n a wrong date or number, an excerpt the page doesn't support, an empty fetch of\n a page that has content.\n- Parallel's docs, tool descriptions and behavior disagree, or you couldn't work\n out how to call a tool.\n- An evaluation, benchmark or comparison you ran shows Parallel doing worse than\n expected.\nProblems you worked around count too. It isn't for mistakes in your own\nrequests, or for questions.\n\nAsk the user first. When you tell them about the problem, offer to report it\nand show what you'd send: the message and the IDs. Send it only if they agree,\nthen tell them it was sent.\n\nPut the IDs involved (search_id, extract_id, run_id) in `examples`, with a\nshort note on each. web_decisions returns no ID: put the subject and the\nquestions it answered wrongly in `message`.\n\nParallel receives only the fields you fill in, plus the account and client the\nrequest came from; nothing else from your conversation. Leave out secrets and\npersonal data.\n", "inputSchema": { "$defs": { "FeedbackExample": { "properties": { "expected": { "anyOf": [ { "maxLength": 1000, "type": "string" }, { "type": "null" } ], "default": null, "description": "What you expected instead, such as a fact or URL Parallel missed.", "title": "Expected" }, "id": { "description": "ID of the Parallel request this example is about, such as a search_id, extract_id, task run_id, findall_id or monitor_id.", "maxLength": 128, "minLength": 1, "pattern": "^[A-Za-z0-9_-]+$", "title": "Id", "type": "string" }, "issue": { "anyOf": [ { "maxLength": 1000, "type": "string" }, { "type": "null" } ], "default": null, "description": "What was wrong with this result.", "title": "Issue" } }, "required": [ "id" ], "title": "FeedbackExample", "type": "object" } }, "additionalProperties": false, "properties": { "actual": { "anyOf": [ { "maxLength": 2000, "type": "string" }, { "type": "null" } ], "default": null, "description": "The overall observed behavior.", "title": "Actual" }, "category": { "description": "The kind of problem.", "enum": [ "results_quality", "error", "latency", "missing_capability", "docs", "billing", "other" ], "title": "Category", "type": "string" }, "examples": { "anyOf": [ { "items": { "$ref": "#/$defs/FeedbackExample" }, "maxItems": 50, "type": "array" }, { "type": "null" } ], "default": null, "description": "The specific requests involved, each with a short note.", "title": "Examples" }, "expected": { "anyOf": [ { "maxLength": 2000, "type": "string" }, { "type": "null" } ], "default": null, "description": "The overall expected behavior.", "title": "Expected" }, "message": { "description": "What you were doing, what went wrong, and what you expected. Do not include secrets or personal data.", "maxLength": 4000, "minLength": 20, "title": "Message", "type": "string" }, "product": { "description": "The Parallel product involved.", "enum": [ "search", "extract", "task", "findall", "monitor", "responses", "decisions", "mcp", "cli", "other" ], "title": "Product", "type": "string" }, "severity": { "default": "degraded", "description": "How much the problem affected the work: blocking, degraded (a workaround was needed) or minor (noticeable, but the work went on unchanged).", "enum": [ "blocking", "degraded", "minor" ], "title": "Severity", "type": "string" } }, "required": [ "message", "category", "product" ], "title": "send_feedback_toolArguments", "type": "object" }, "outputSchema": { "$defs": { "FeedbackReport": { "properties": { "actual": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Actual" }, "category": { "enum": [ "results_quality", "error", "latency", "missing_capability", "docs", "billing", "other" ], "title": "Category", "type": "string" }, "context": { "$ref": "#/$defs/FeedbackReportContext" }, "examples": { "items": { "$ref": "#/$defs/FeedbackReportExample" }, "title": "Examples", "type": "array" }, "expected": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Expected" }, "message": { "title": "Message", "type": "string" }, "product": { "enum": [ "search", "extract", "task", "findall", "monitor", "responses", "decisions", "mcp", "cli", "other" ], "title": "Product", "type": "string" }, "recipient": { "description": "Who receives the report and how long it is kept.", "title": "Recipient", "type": "string" }, "redactions": { "description": "How many secrets were removed.", "title": "Redactions", "type": "integer" }, "severity": { "enum": [ "blocking", "degraded", "minor" ], "title": "Severity", "type": "string" } }, "required": [ "message", "category", "product", "severity", "examples", "context", "redactions", "recipient" ], "title": "FeedbackReport", "type": "object" }, "FeedbackReportContext": { "properties": { "llm_model": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Llm Model" }, "org_id": { "title": "Org Id", "type": "string" }, "sender": { "description": "Who Parallel sees as the sender.", "title": "Sender", "type": "string" }, "session_id": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Session Id" }, "surface": { "description": "How the feedback was sent: api, cli, mcp or platform.", "enum": [ "api", "cli", "mcp", "platform" ], "title": "Surface", "type": "string" }, "user_agent": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "User Agent" } }, "required": [ "org_id", "sender", "surface" ], "title": "FeedbackReportContext", "type": "object" }, "FeedbackReportExample": { "properties": { "expected": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Expected" }, "id": { "title": "Id", "type": "string" }, "issue": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Issue" } }, "required": [ "id" ], "title": "FeedbackReportExample", "type": "object" } }, "properties": { "duplicate": { "default": false, "description": "True when the same report was received in the last 24 hours; feedback_id is the original report and nothing new was stored.", "title": "Duplicate", "type": "boolean" }, "feedback_id": { "description": "ID of the stored report.", "title": "Feedback Id", "type": "string" }, "next_step": { "description": "What the agent should do next.", "title": "Next Step", "type": "string" }, "report": { "$ref": "#/$defs/FeedbackReport", "description": "Exactly what Parallel received, with secrets removed." }, "status": { "const": "received", "title": "Status", "type": "string" } }, "required": [ "status", "feedback_id", "report", "next_step" ], "title": "FeedbackResponse", "type": "object" }, "annotations": { "destructiveHint": false, "idempotentHint": false, "openWorldHint": false, "readOnlyHint": false, "title": "Send feedback to Parallel" } } ], "schemaTokens": 5322, "changedAt": "2026-11-07T01:46:44.757089899Z", "check": { "checker": "anchor-check/1.0", "totalTokens": 5322, "counts": { "error": 0, "note": 1, "warn": 3 }, "findings": [ { "rule": "TC15", "severity": "warn", "tool": "send_feedback", "message": "inputSchema uses $ref/$defs", "fix": "Inline the referenced schemas. Pydantic and zod-to-json-schema emit $defs for nested models; most can be told not to." }, { "rule": "TC22", "severity": "warn", "tool": "send_feedback", "message": "the definition is about 1,634 tokens", "fix": "Trim the description and parameter docs, or split the tool." }, { "rule": "TC22", "severity": "warn", "tool": "web_fetch", "message": "the definition is about 1,970 tokens", "fix": "Trim the description and parameter docs, or split the tool." }, { "rule": "TC29", "severity": "note", "message": "about 396 tokens (7% of the definitions) are titles that repeat property or function names", "fix": "Strip \"title\" keys that only restate a name before listing tools." } ] } }, "updatedAt": "2026-11-07T18:21:52.770771808Z" } }, "answer": "Parallel Search and Task APIs scores 75 (BB) on agent readiness against Perplexity Search API's 70.2 (BB), and leads in 4 of 7 scored categories. Perplexity Search API leads on reliability and security \u0026 auth.", "b": { "slug": "perplexity-search-api", "name": "Perplexity Search API", "vendor": "Perplexity", "vendorUrl": "https://www.perplexity.ai/", "kind": "http-api", "category": "search", "summary": "Perplexity's Search API returns ranked web results with extracted page text as JSON from Perplexity's own index, through `POST /search`. The same key reaches the Agent API's web_search tool for cited answers, and a hosted MCP server wraps both.", "url": "https://www.anchorterminal.com/tools/perplexity-search-api", "markdownUrl": "https://www.anchorterminal.com/tools/perplexity-search-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/perplexity-search-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/perplexity-search-api.json", "dns": "perplexity-search-api.grade.anchorterminal.com", "repo": "https://github.com/perplexityai/modelcontextprotocol", "license": "Proprietary service under the Perplexity API Terms of Service. The MCP server is MIT and the official SDKs Apache-2.0", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://api.perplexity.ai/mcp", "packages": [ { "registry": "pypi", "name": "perplexityai" }, { "registry": "npm", "name": "@perplexity-ai/perplexity_ai" }, { "registry": "npm", "name": "@perplexity-ai/mcp-server" } ], "auth": "mixed", "authNotes": "Bearer Perplexity API key in the `Authorization` header. Keys belong to a project in the API console, are shown once, and can be generated and revoked through `/generate_auth_token` and `/revoke_auth_token`, with a rotation guide. No per-key scopes found. The hosted MCP server also accepts Sign in with Perplexity (OAuth), where the user picks the organisation to bill.", "pricing": "usage", "pricingNotes": "$5 per 1,000 successful Search API requests, or $1 with Fast Search, with up to five queries per request billed once. Invalid, rate-limited and failed requests are not billed. Agent API web_search is $2.50 per 1,000 calls plus model tokens. Prepaid credits with a card. No free allowance found.", "priceSummary": "$5 / 1k req", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Search API docs, the pricing page, the OpenAPI description or llms.txt (checked 2026-11-06). An empty balance returns 402 Payment Required with no payment requirements, per the FAQ.", "endpoints": [] }, "toolCount": 4, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.perplexity.ai/docs/search/overview", "llmsTxt": "https://docs.perplexity.ai/llms.txt", "openapi": "https://docs.perplexity.ai/openapi.json", "registryName": "ai.perplexity/mcp-server", "capabilities": [ "web.search", "search.answer", "search.research" ], "tags": [ "hosted", "usage-priced", "prepaid", "card-required", "closed-source", "openapi", "llms-txt", "mcp", "remote-mcp", "mcp-registry", "python", "typescript", "status-page", "soc2" ], "lastRelease": "2026-10-23", "graded": true, "anchor": { "graded": true, "score": 70.2, "grade": "BB", "agentReady": true, "rank": 210, "ranked": true, "rankOf": 1486, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 85, "maintenance": 82, "payments": 25, "reliability": 80, "schema": 89, "security": 56, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Raw ranked results with token-capped page text from Perplexity's own index, $5 per 1,000 requests or $1 with Fast Search, an OpenAPI description and a hosted MCP server with read-only annotations. Uptime is not guaranteed, there is no free allowance, keys carry no scopes, and no guidance on untrusted page text was found.", "bestFor": "Agents on any model that need raw ranked sources with extracted text at a low per-request price, and teams that want cited answers from the same key through the Agent API.", "strengths": [ "OpenAPI 3.1 description of `POST /search` with enums and limits, llms.txt and a Markdown twin of every docs page", "`max_tokens`, `max_tokens_per_page` and `max_results` cap what reaches the model, and up to five queries share one billed request", "Per-request prices published without login, and invalid, rate-limited and failed requests are not billed", "Hosted MCP server with OAuth or a key; the local server is in the official registry under the verified ai.perplexity namespace", "security.txt valid to 31 December 2027, a SOC 2 Type II report and a SECURITY.md that takes private reports" ], "weaknesses": [ "The FAQ says uptime and recovery time are not guaranteed, and the terms carry no SLA", "No free allowance and prepaid credits with a card; Stripe Projects still needs a $10 purchase", "Project keys have no scopes or spending limits, so any key can run every API on the account", "No guidance on treating returned snippets as untrusted text was found in the docs or the MCP server", "The DPA says Perplexity Search may follow different data terms, and no retention period for search queries is stated" ], "agentNotes": [ "Set `max_tokens_per_page` and `max_tokens` before calling; extracted text otherwise fills the context, and the price does not change with size", "Skip results with an empty `snippet` and dedupe by `url` when sending a `query` array; each query costs one rate-limit unit", "Use `search_type: \"fast\"` for $1 per 1,000 when latency and cost matter more than depth", "On 429 wait for Retry-After, then back off; on 402 stop and ask the user to add credits", "Use the Search API for sources and the Agent API's web_search tool for a written answer with citations" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 70.2 } ], "editorialScores": { "ergonomics": 85, "maintenance": 82, "payments": 25, "reliability": 80, "schema": 89, "security": 56, "transparency": 51 }, "provenanceScore": 80, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install perplexityai", "http": "curl -X POST https://api.perplexity.ai/search \\\n -H \"Authorization: Bearer $PERPLEXITY_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"query\": \"renewable energy technologies\", \"max_results\": 10, \"max_tokens\": 50000, \"max_tokens_per_page\": 4096}'", "claudeCode": "claude mcp add --transport http perplexity https://api.perplexity.ai/mcp", "config": { "mcpServers": { "perplexity": { "url": "https://api.perplexity.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/perplexity-search-api" }, "sameCompany": [ "perplexity-space", "pplx-decider", "pplx-decider-flash" ], "area": "web-data", "unitPrices": [ { "item": "Search API request", "unit": "1k-requests", "usd": 5, "note": "Up to five queries in one request billed once; failed and rate-limited requests not billed" }, { "item": "Search API request with Fast Search", "unit": "1k-requests", "usd": 1, "note": "`search_type: \"fast\"`" }, { "item": "Agent API web_search call", "unit": "1k-calls", "usd": 2.5, "note": "Plus model tokens; $1.00 with Fast Search" }, { "item": "Agent API fetch_url call", "unit": "1k-calls", "usd": 0.5, "note": "Plus model tokens" } ], "provenance": { "legalEntity": "Perplexity AI, Inc.", "domain": "perplexity.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.perplexity.ai/hub/legal/perplexity-api-terms-of-service", "privacy": "https://www.perplexity.ai/hub/legal/privacy-notice", "statusPage": "https://status.perplexity.com/", "changelog": "https://docs.perplexity.ai/docs/resources/changelog", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The API Terms of Service (last updated 23 January 2026) name Perplexity AI, Inc. and California law. The Data Processing Addendum (last updated 13 August 2026) deletes personal data within 30 days of the service ending and notes that Perplexity Search may follow different data terms.", "www.perplexity.ai/.well-known/security.txt is valid until 31 December 2027 and links www.perplexity.ai/security.", "The status page moved to incident.io on 10 September 2026 and has Website, App, Computer and API components, with no separate Search component.", "docs.perplexity.ai/robots.txt allows the docs and carries Content-Signal ai-train=yes, search=yes, ai-input=yes. The terms have no clause on automated access to the website.", "The changelog dates entries by month only. Domain registration was not checked." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/perplexity-search-api.json", "live": { "slug": "perplexity-search-api", "probe": { "target": "https://api.perplexity.ai/mcp", "method": "get", "lastAt": "2026-11-07T18:20:46.568623937Z", "lastOk": true, "lastStatus": 401, "lastMs": 254, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 164, "p95ms24h": 262, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.perplexity.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:53.516499278Z" }, "versions": [ { "registry": "mcp-registry", "name": "ai.perplexity/mcp-server", "version": "1.2.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@perplexity-ai/mcp-server", "version": "1.3.0", "seenAt": "2026-11-06T23:55:31.394431614Z" }, { "registry": "npm", "name": "@perplexity-ai/perplexity_ai", "version": "0.41.0", "seenAt": "2026-11-06T23:55:30.575713692Z" }, { "registry": "pypi", "name": "perplexityai", "version": "0.46.1", "released": "2026-10-23", "seenAt": "2026-11-06T23:55:30.34668899Z" } ], "githubStars": 2612, "npmWeekly": 97298, "pypiWeekly": 401537, "securityTxt": { "url": "https://perplexity.ai/.well-known/security.txt", "state": "valid", "expires": "2027-12-31T00:00:00Z", "checkedAt": "2026-11-07T16:01:03.917430365Z" }, "llmsTxt": { "url": "https://docs.perplexity.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:36.681222085Z" }, "pages": [ { "url": "https://docs.perplexity.ai/docs/resources/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:27.675707255Z", "changedAt": "2026-11-06T13:29:48.535494355Z", "fingerprint": "a52a171e1f1f" }, { "url": "https://www.perplexity.ai/hub/legal/privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:32:54.875760985Z", "changedAt": "2026-11-06T13:53:25.792168971Z", "fingerprint": "29c9dd01613d" }, { "url": "https://www.perplexity.ai/hub/legal/perplexity-api-terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:32:50.897959644Z", "changedAt": "2026-11-06T13:53:22.592031411Z", "fingerprint": "6a7e4a95f45b" } ], "mcpTools": { "url": "https://api.perplexity.ai/mcp", "checkedAt": "2026-11-07T01:46:49.011542458Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:49.011542458Z" }, "updatedAt": "2026-11-07T18:21:53.516499278Z" } }, "edges": [ { "by": 50, "category": "payments", "leads": "parallel-search-api", "name": "Payments \u0026 pricing", "reasons": { "a": "Parallel runs a separate gateway at parallelmpp.dev that takes x402 (USDC on Base) and MPP (Stripe or Tempo) for search and extract at $0.01 and an ultra task at $0.30. Our unpaid POST to /api/search on 6 October returned 402 with an x402 v2 challenge for 10000 base units on eip155:8453 and a Tempo MPP challenge. Nothing on api.parallel.ai, and the gateway sells one price per endpoint with no mode choice, so partial (25). Per-unit prices published without login (20). Up to 5,000 free requests a month, $5 monthly credit and up to $80 at signup on the pricing page, which still doesn't say whether a card is needed (10). The hosted Search MCP works with no key, and the gateway needs only a wallet (20).", "b": "No x402, MPP or L402 in the docs, pricing page, OpenAPI or llms.txt (0). $5 per 1,000 successful requests, $1 with Fast Search, published without a login, with failed and rate-limited requests not billed (20). Usage is prepaid with a card on the billing page, and no free allowance was found. The console playground needs no key but is a page for a person, not an API allowance (0). A person signs up in the console. The Stripe Projects route provisions a project, key and credits from a terminal, but needs a person's Stripe account with a payment method and a $10 minimum purchase (5 of 20, as on the Decisions API listing). 0 + 20 + 0 + 5 = 25." }, "scores": { "a": 75, "b": 25 } }, { "by": 11, "category": "security", "leads": "perplexity-search-api", "name": "Security \u0026 auth", "reasons": { "a": "API key in `x-api-key`. The Search MCP takes a Bearer key or OAuth at /mcp-oauth. We found no key scopes (20). Every Search and Extract action is a read, and Task tools live in a separate MCP server, so the search server is a read-only subset (15). Excerpts and fetched pages are untrusted web text, and the docs index has no prompt-injection guidance (0). No audit log found (0). The privacy policy shows a SOC 2 badge and links trust.parallel.ai, which rendered only its title to our reader on 6 October. security.txt is 404 on parallel.ai and docs.parallel.ai, and no bug bounty found (10).", "b": "Project API keys, shown once, revocable, and generated and revoked through two documented endpoints with a rotation guide. No per-key scopes or spending limits were found. The hosted MCP server also takes Sign in with Perplexity (OAuth). Keys go in the Authorization header only (22 of 30, as on the Decisions API listing). Search only reads, and MCP clients can disable tools, but any key reaches every API on the account, including the Agent API's sandbox and MCP tools (8 of 20). Snippets are third-party page text, and no guidance on treating them as untrusted was found in the docs, the MCP server or its SECURITY.md (0 of 15). Responses carry a request `id`, and the console shows usage by key. The Audit API covers enterprise organisations' web app events with its own keys, not API calls (8 of 15). security.txt valid until 31 December 2027 linking a security page, a SOC 2 Type II report, a 2025 HIPAA gap assessment and a CAIQlite listed on the trust centre, and a SECURITY.md on the MCP server that takes private reports through GitHub advisories or security@perplexity.ai. The trust centre is drawn by script and wasn't read (18 of 20). 22 + 8 + 0 + 8 + 18 = 56." }, "scores": { "a": 45, "b": 56 } }, { "by": 5, "category": "reliability", "leads": "perplexity-search-api", "name": "Reliability", "reasons": { "a": "incident.io page at status.parallel.ai with Search, Task, Chat, Monitor, FindAll and Entity Search components and history (20). The feed, re-read on 1 November, has nothing after 13 October, so the 90 days from 3 August hold the same four incidents, all partial or degraded. Elevated 503s on 6 August, about an hour of Task API latency on 2 September, intermittent 4xx errors on 7 September, and transient 502s from the network gateway on 13 October, degraded performance from 01:23 to 01:43 UTC. Most have no duration listed (20). Published limits, 600 a minute for Search, Image Search, Extract, Decisions and Entity Search, 2,000 for Tasks, 300 for Chat and Monitor (15). The errors page marks 429 as retryable with exponential backoff, but there's no `Retry-After` and no idempotency guidance for creating Task runs, which the SDKs retry twice by default (10). No SLA found (0). Search, Extract and Task are GA (10).", "b": "Graded on the hosted lines, for `POST /search` and the hosted MCP server. status.perplexity.com, on incident.io since 10 September 2026, has an API component with an RSS feed and a JSON summary. There is no separate Search component (20). In the 90 days from 8 August the feed lists 'Investigating API issue' on 13 August, resolved with no detail, a usage-based billing issue on 3 September, and on 9 October elevated errors on the website, app and Computer, where the API 'remained operational throughout'. Minor only, with the caveat that history before the migration may be incomplete (20). The Search API is limited to 50 query units a second with a burst of 50 on every tier, and the other APIs publish QPS and token limits per tier (15). 429 carries Retry-After and an `error.type`, the SDKs retry 429 and 5xx twice honouring Retry-After, the Search best-practices page shows backoff, and failed or rate-limited searches are not billed. Searches have no side effects (15). The FAQ says Perplexity does not guarantee uptime, failure frequency or recovery time, and the terms carry no SLA (0). No beta label on the Search API, launched on 25 September 2025 (10). 20 + 20 + 15 + 15 + 0 + 10 = 80." }, "scores": { "a": 75, "b": 80 } }, { "by": 5, "category": "schema", "leads": "parallel-search-api", "name": "Schema \u0026 documentation", "reasons": { "a": "Public OpenAPI at docs.parallel.ai/public-openapi.json, linked from llms.txt (25). llms.txt and Markdown pages (10). A live `tools/list` on search.parallel.ai/mcp on 17 October and again on 1 November returned the two definitions, and the newer Parallel MCP server at mcp.parallel.ai adds `web_decisions`, whose description says when to use web_search instead. `web_search` states its purpose and ideal uses, and `web_fetch` says to use it \"only when web_search excerpts are insufficient\". The docs add that domain filters are hard filters that can cut quality. `web_search` has no when-not-to line of its own (17). Typed JSON Schema inputs with required fields and an output schema on both tools, `mode` is an enum in the API, and Task output schemas are JSON Schema. The MCP inputs carry no enums (12). The errors page lists each code with whether to retry and what to do, and 422s carry a structured `detail` (15). A dated changelog, newest entry 26 October 2026 (Decisions API) after 19 October (EU data residency), and beta headers retire on dated entries (15).", "b": "OpenAPI 3.1.0 at docs.perplexity.ai/openapi.json describes `POST /search` with typed request and response schemas, listed in llms.txt (25). llms.txt indexes every page, each with a Markdown twin (10). The overview says what a result holds, that snippets can be empty, when to use the Search API instead of the Agent API, and that it takes queries not URLs and does not re-fetch pages (19 of 20). `search_type` is an enum, `max_results`, `max_tokens` and `max_tokens_per_page` carry minimum and maximum, country and language codes carry lengths, and `query` is a string or an array. The recency filter is an enum in the docs, and date filters are `MM/DD/YYYY` strings (14 of 15). Python, TypeScript and cURL examples with a recorded response. The spec documents only 200 and 422 for `/search`, and status codes are listed on the SDK error-handling page and the rate-limit page rather than for Search (11 of 15). A public changelog with several entries a month, dated by month only, and an unversioned `/search` path (10 of 15). 25 + 10 + 19 + 14 + 11 + 10 = 89." }, "scores": { "a": 94, "b": 89 } }, { "by": 5, "category": "maintenance", "leads": "parallel-search-api", "name": "Maintenance \u0026 community", "reasons": { "a": "parallel-web 1.3.7 for Python on 2026-10-23 and for TypeScript on 2026-10-28, and changelog entries on 19 and 26 October, the second launching the Decisions API (30). Counted from the tags and the changelog, the 90 days from 3 August hold Python SDK releases 1.3.1 to 1.3.7, TypeScript 1.3.1 to 1.3.7 and ten changelog entries from 19 August to 26 October (20). The SDK releases since 1.3.5 are dependency bumps. Closed service with a changelog and support@parallel.ai. We didn't test whether support answers (12). Current Python and TypeScript SDKs, and ai.parallel/search-mcp and ai.parallel/task-mcp in the official registry (15). The Python SDK runs lint and build in CI on push, plus a workflow that detects breaking changes (10).", "b": "Read as a closed service with official SDKs and an open-source MCP server. perplexityai 0.46.1 on PyPI on 23 October 2026 and the MCP server's last commit on 21 October, with changelog entries into November 2026 (30). In the 90 days from 8 August, perplexityai 0.43.7 to 0.46.1 (six releases from 2 October), MCP server 1.2.1 (27 August) and 1.3.0 (25 September, Fast Search on perplexity_search), and Fast Search itself in September (20). A changelog with several entries a month, a community forum with a bug-report category, a GitHub discussion repository and api@perplexity.ai. MCP issue reply times weren't read (10 of 15). The MCP server is in the official registry under the domain-verified ai.perplexity namespace, and the Python and TypeScript SDKs are current (15). The MCP repository runs tests in CI and validates its plugin manifests. Its 1.4.0, prepared on 16 October, is not on npm, which still serves 1.3.0, and the registry's latest entry is 1.2.1 of 27 August (7 of 10). 30 + 20 + 10 + 15 + 7 = 82." }, "scores": { "a": 87, "b": 82 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Parallel Web Systems", "b": "Perplexity", "name": "Vendor" }, { "a": "https://api.parallel.ai/v1/search", "b": "https://api.perplexity.ai/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "$1 per 1,000 requests", "b": "$1 per 1,000 requests", "name": "Price for web search" }, { "a": "payer tooling only", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under the Perplexity API Terms of Service. The MCP server is MIT and the official SDKs Apache-2.0", "name": "Licence" }, { "a": "6", "b": "4", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "ai.parallel/search-mcp", "b": "ai.perplexity/mcp-server", "name": "MCP registry" }, { "a": "2026-10-28", "b": "2026-10-23", "name": "Last release" }, { "a": "2026-10-17", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-08-11", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "28 stars, 250k npm/wk, 994k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3.6/5 (8)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Parallel Search and Task APIs scores 75 (BB) on agent readiness against Perplexity Search API's 70.2 (BB), and leads in 4 of 7 scored categories. Perplexity Search API leads on reliability and security \u0026 auth.", "question": "Which is better for AI agents, Parallel Search and Task APIs or Perplexity Search API?" }, { "answer": "They cost about the same, $1 per 1,000 requests for Parallel Search and Task APIs and $1 per 1,000 requests for Perplexity Search API. These are the vendors' published prices for the job.", "question": "Which is cheaper for web search, Parallel Search and Task APIs or Perplexity Search API?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Parallel Search and Task APIs and Perplexity Search API need an API key?" }, { "answer": "Yes. Parallel Search and Task APIs has a hosted endpoint at https://api.parallel.ai/v1/search and Perplexity Search API at https://api.perplexity.ai/mcp.", "question": "Can an agent call Parallel Search and Task APIs and Perplexity Search API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 94 against 89", "Payments \u0026 pricing, 75 against 25", "Maintenance \u0026 community, 87 against 82" ], "also": null, "goodFor": "Agents that mix quick search with long research or enrichment jobs and want one vendor and one bill.", "slug": "parallel-search-api", "watchFor": "Search defaults to advanced mode at $5 per 1,000 when `mode` is left out" }, { "aheadOn": [ "Reliability, 80 against 75", "Security \u0026 auth, 56 against 45" ], "also": [ "Runs on your own machine" ], "goodFor": "Agents on any model that need raw ranked sources with extracted text at a low per-request price, and teams that want cited answers from the same key through the Agent API.", "slug": "perplexity-search-api", "watchFor": "The FAQ says uptime and recovery time are not guaranteed, and the terms carry no SLA" } ], "history": { "parallel-search-api": [ { "causes": [ "method" ], "date": "2026-10-30", "delta": -0.1, "from": 75.1, "fromGrade": "BB", "to": 75, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 75, "fromGrade": "BB", "to": 75.1, "toGrade": "BB" }, { "causes": [ "evidence" ], "date": "2026-10-17", "delta": 1, "from": 74, "fromGrade": "BB", "to": 75, "toGrade": "BB" } ], "perplexity-search-api": null }, "job": { "capability": "web.search", "name": "Web search" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-parallel-search-api.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.json", "title": "Grounding with Bing Search vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.json", "title": "Grounding with Bing Search vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-parallel-search-api.json", "title": "Brave Search API + MCP vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-perplexity-search-api.json", "title": "Brave Search API + MCP vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-parallel-search-api.json", "title": "Cloudflare Web Search API vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-search-api.json", "title": "Cloudflare Web Search API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-parallel-search-api.json", "title": "DeepSeek Search and Fetch API vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api.json", "title": "DeepSeek Search and Fetch API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-parallel-search-api.json", "title": "Exa API + MCP vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-perplexity-search-api.json", "title": "Exa API + MCP vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-parallel-search-api.json", "title": "Firecrawl MCP vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api.json", "title": "Firecrawl MCP vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-parallel-search-api.json", "title": "Kagi Search API vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api.json", "title": "Kagi Search API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-parallel-search-api.json", "title": "Linkup vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/linkup-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api.json", "title": "Linkup vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-parallel-search-api.json", "title": "Mojeek Web Search API vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/mojeek-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api.json", "title": "Mojeek Web Search API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-parallel-search-api.json", "title": "NewsCatcher vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.json", "title": "NewsCatcher vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-searchapi-io.json", "title": "Parallel Search and Task APIs vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-serpapi.json", "title": "Parallel Search and Task APIs vs SerpApi", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-serper.json", "title": "Parallel Search and Task APIs vs Serper", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-serphouse.json", "title": "Parallel Search and Task APIs vs SERPHouse", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-serpkite.json", "title": "Parallel Search and Task APIs vs SerpKite", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-specstream.json", "title": "Parallel Search and Task APIs vs SpecStream", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-tavily-mcp.json", "title": "Parallel Search and Task APIs vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-tinyfish-search.json", "title": "Parallel Search and Task APIs vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-valyu.json", "title": "Parallel Search and Task APIs vs Valyu", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-you-com-api.json", "title": "Parallel Search and Task APIs vs You.com APIs", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-searchapi-io.json", "title": "Perplexity Search API vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpapi.json", "title": "Perplexity Search API vs SerpApi", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serper.json", "title": "Perplexity Search API vs Serper", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serphouse.json", "title": "Perplexity Search API vs SERPHouse", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite.json", "title": "Perplexity Search API vs SerpKite", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-specstream.json", "title": "Perplexity Search API vs SpecStream", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tavily-mcp.json", "title": "Perplexity Search API vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tinyfish-search.json", "title": "Perplexity Search API vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu.json", "title": "Perplexity Search API vs Valyu", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-you-com-api.json", "title": "Perplexity Search API vs You.com APIs", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-parallel-search-api.json", "title": "Arcmira vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/arcmira-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api.json", "title": "Arcmira vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-parallel-search-api.json", "title": "Grep AI vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-api.json", "title": "Grep AI vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-parallel-search-api.json", "title": "Fetch (MCP reference server) vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-parallel-search-api" } ], "panel": null, "scores": [ { "by": 5, "edge": "perplexity-search-api", "key": "reliability", "name": "Reliability", "parallel-search-api": 75, "perplexity-search-api": 80, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "parallel-search-api", "key": "schema", "name": "Schema \u0026 documentation", "parallel-search-api": 94, "perplexity-search-api": 89, "weight": 13 }, { "by": 2, "edge": "parallel-search-api", "key": "ergonomics", "name": "Agent ergonomics", "parallel-search-api": 87, "perplexity-search-api": 85, "weight": 13 }, { "by": 11, "edge": "perplexity-search-api", "key": "security", "name": "Security \u0026 auth", "parallel-search-api": 45, "perplexity-search-api": 56, "weight": 14 }, { "by": 50, "edge": "parallel-search-api", "key": "payments", "name": "Payments \u0026 pricing", "parallel-search-api": 75, "perplexity-search-api": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 5, "edge": "parallel-search-api", "key": "maintenance", "name": "Maintenance \u0026 community", "parallel-search-api": 87, "perplexity-search-api": 82, "weight": 7 }, { "by": 1, "edge": "perplexity-search-api", "key": "transparency", "name": "Transparency \u0026 trust", "parallel-search-api": 65, "perplexity-search-api": 66, "weight": 7 } ], "summary": "Parallel Search and Task APIs scores 75 (BB) on agent readiness against Perplexity Search API's 70.2 (BB), and leads in 4 of 7 scored categories. Perplexity Search API leads on reliability and security \u0026 auth. Both do web search.", "tasks": null, "tutorials": [], "verdicts": { "parallel-search-api": "Fast-mode search at $1 per 1,000 with 10 excerpted results, and a keyless two-tool Search MCP annotated read-only. Search defaults to advanced mode at $5 per 1,000 when `mode` is left out, and the Customer Terms allow training on inputs and outputs.", "perplexity-search-api": "Raw ranked results with token-capped page text from Perplexity's own index, $5 per 1,000 requests or $1 with Fast Search, an OpenAPI description and a hosted MCP server with read-only annotations. Uptime is not guaranteed, there is no free allowance, keys carry no scopes, and no guidance on untrusted page text was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api", "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.min.md" }, "markdown": "Parallel Search and Task APIs scores 75 (BB) on agent readiness against Perplexity Search API's 70.2 (BB), and leads in 4 of 7 scored categories. Perplexity Search API leads on reliability and security \u0026 auth. Both do web search.\n\n- Parallel Search and Task APIs: grade BB, 75/100, rank #73 of 1486. Markdown https://www.anchorterminal.com/tools/parallel-search-api.md · JSON https://www.anchorterminal.com/api/v1/tools/parallel-search-api.json\n- Perplexity Search API: grade BB, 70.2/100, rank #210 of 1486. Markdown https://www.anchorterminal.com/tools/perplexity-search-api.md · JSON https://www.anchorterminal.com/api/v1/tools/perplexity-search-api.json\n- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md\n- All 308 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\n\n### Parallel Search and Task APIs (BB)\n\nGood for: Agents that mix quick search with long research or enrichment jobs and want one vendor and one bill.\n\nAhead on:\n- Schema \u0026 documentation, 94 against 89\n- Payments \u0026 pricing, 75 against 25\n- Maintenance \u0026 community, 87 against 82\n\nWatch for: Search defaults to advanced mode at $5 per 1,000 when `mode` is left out\n\n### Perplexity Search API (BB)\n\nGood for: Agents on any model that need raw ranked sources with extracted text at a low per-request price, and teams that want cited answers from the same key through the Agent API.\n\nAhead on:\n- Reliability, 80 against 75\n- Security \u0026 auth, 56 against 45\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: The FAQ says uptime and recovery time are not guaranteed, and the terms carry no SLA\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Parallel Search and Task APIs +50\n\n- Parallel Search and Task APIs (75): Parallel runs a separate gateway at parallelmpp.dev that takes x402 (USDC on Base) and MPP (Stripe or Tempo) for search and extract at $0.01 and an ultra task at $0.30. Our unpaid POST to /api/search on 6 October returned 402 with an x402 v2 challenge for 10000 base units on eip155:8453 and a Tempo MPP challenge. Nothing on api.parallel.ai, and the gateway sells one price per endpoint with no mode choice, so partial (25). Per-unit prices published without login (20). Up to 5,000 free requests a month, $5 monthly credit and up to $80 at signup on the pricing page, which still doesn't say whether a card is needed (10). The hosted Search MCP works with no key, and the gateway needs only a wallet (20).\n- Perplexity Search API (25): No x402, MPP or L402 in the docs, pricing page, OpenAPI or llms.txt (0). $5 per 1,000 successful requests, $1 with Fast Search, published without a login, with failed and rate-limited requests not billed (20). Usage is prepaid with a card on the billing page, and no free allowance was found. The console playground needs no key but is a page for a person, not an API allowance (0). A person signs up in the console. The Stripe Projects route provisions a project, key and credits from a terminal, but needs a person's Stripe account with a payment method and a $10 minimum purchase (5 of 20, as on the Decisions API listing). 0 + 20 + 0 + 5 = 25.\n\n### Security \u0026 auth: Perplexity Search API +11\n\n- Parallel Search and Task APIs (45): API key in `x-api-key`. The Search MCP takes a Bearer key or OAuth at /mcp-oauth. We found no key scopes (20). Every Search and Extract action is a read, and Task tools live in a separate MCP server, so the search server is a read-only subset (15). Excerpts and fetched pages are untrusted web text, and the docs index has no prompt-injection guidance (0). No audit log found (0). The privacy policy shows a SOC 2 badge and links trust.parallel.ai, which rendered only its title to our reader on 6 October. security.txt is 404 on parallel.ai and docs.parallel.ai, and no bug bounty found (10).\n- Perplexity Search API (56): Project API keys, shown once, revocable, and generated and revoked through two documented endpoints with a rotation guide. No per-key scopes or spending limits were found. The hosted MCP server also takes Sign in with Perplexity (OAuth). Keys go in the Authorization header only (22 of 30, as on the Decisions API listing). Search only reads, and MCP clients can disable tools, but any key reaches every API on the account, including the Agent API's sandbox and MCP tools (8 of 20). Snippets are third-party page text, and no guidance on treating them as untrusted was found in the docs, the MCP server or its SECURITY.md (0 of 15). Responses carry a request `id`, and the console shows usage by key. The Audit API covers enterprise organisations' web app events with its own keys, not API calls (8 of 15). security.txt valid until 31 December 2027 linking a security page, a SOC 2 Type II report, a 2025 HIPAA gap assessment and a CAIQlite listed on the trust centre, and a SECURITY.md on the MCP server that takes private reports through GitHub advisories or security@perplexity.ai. The trust centre is drawn by script and wasn't read (18 of 20). 22 + 8 + 0 + 8 + 18 = 56.\n\n### Reliability: Perplexity Search API +5\n\n- Parallel Search and Task APIs (75): incident.io page at status.parallel.ai with Search, Task, Chat, Monitor, FindAll and Entity Search components and history (20). The feed, re-read on 1 November, has nothing after 13 October, so the 90 days from 3 August hold the same four incidents, all partial or degraded. Elevated 503s on 6 August, about an hour of Task API latency on 2 September, intermittent 4xx errors on 7 September, and transient 502s from the network gateway on 13 October, degraded performance from 01:23 to 01:43 UTC. Most have no duration listed (20). Published limits, 600 a minute for Search, Image Search, Extract, Decisions and Entity Search, 2,000 for Tasks, 300 for Chat and Monitor (15). The errors page marks 429 as retryable with exponential backoff, but there's no `Retry-After` and no idempotency guidance for creating Task runs, which the SDKs retry twice by default (10). No SLA found (0). Search, Extract and Task are GA (10).\n- Perplexity Search API (80): Graded on the hosted lines, for `POST /search` and the hosted MCP server. status.perplexity.com, on incident.io since 10 September 2026, has an API component with an RSS feed and a JSON summary. There is no separate Search component (20). In the 90 days from 8 August the feed lists 'Investigating API issue' on 13 August, resolved with no detail, a usage-based billing issue on 3 September, and on 9 October elevated errors on the website, app and Computer, where the API 'remained operational throughout'. Minor only, with the caveat that history before the migration may be incomplete (20). The Search API is limited to 50 query units a second with a burst of 50 on every tier, and the other APIs publish QPS and token limits per tier (15). 429 carries Retry-After and an `error.type`, the SDKs retry 429 and 5xx twice honouring Retry-After, the Search best-practices page shows backoff, and failed or rate-limited searches are not billed. Searches have no side effects (15). The FAQ says Perplexity does not guarantee uptime, failure frequency or recovery time, and the terms carry no SLA (0). No beta label on the Search API, launched on 25 September 2025 (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.\n\n### Schema \u0026 documentation: Parallel Search and Task APIs +5\n\n- Parallel Search and Task APIs (94): Public OpenAPI at docs.parallel.ai/public-openapi.json, linked from llms.txt (25). llms.txt and Markdown pages (10). A live `tools/list` on search.parallel.ai/mcp on 17 October and again on 1 November returned the two definitions, and the newer Parallel MCP server at mcp.parallel.ai adds `web_decisions`, whose description says when to use web_search instead. `web_search` states its purpose and ideal uses, and `web_fetch` says to use it \"only when web_search excerpts are insufficient\". The docs add that domain filters are hard filters that can cut quality. `web_search` has no when-not-to line of its own (17). Typed JSON Schema inputs with required fields and an output schema on both tools, `mode` is an enum in the API, and Task output schemas are JSON Schema. The MCP inputs carry no enums (12). The errors page lists each code with whether to retry and what to do, and 422s carry a structured `detail` (15). A dated changelog, newest entry 26 October 2026 (Decisions API) after 19 October (EU data residency), and beta headers retire on dated entries (15).\n- Perplexity Search API (89): OpenAPI 3.1.0 at docs.perplexity.ai/openapi.json describes `POST /search` with typed request and response schemas, listed in llms.txt (25). llms.txt indexes every page, each with a Markdown twin (10). The overview says what a result holds, that snippets can be empty, when to use the Search API instead of the Agent API, and that it takes queries not URLs and does not re-fetch pages (19 of 20). `search_type` is an enum, `max_results`, `max_tokens` and `max_tokens_per_page` carry minimum and maximum, country and language codes carry lengths, and `query` is a string or an array. The recency filter is an enum in the docs, and date filters are `MM/DD/YYYY` strings (14 of 15). Python, TypeScript and cURL examples with a recorded response. The spec documents only 200 and 422 for `/search`, and status codes are listed on the SDK error-handling page and the rate-limit page rather than for Search (11 of 15). A public changelog with several entries a month, dated by month only, and an unversioned `/search` path (10 of 15). 25 + 10 + 19 + 14 + 11 + 10 = 89.\n\n### Maintenance \u0026 community: Parallel Search and Task APIs +5\n\n- Parallel Search and Task APIs (87): parallel-web 1.3.7 for Python on 2026-10-23 and for TypeScript on 2026-10-28, and changelog entries on 19 and 26 October, the second launching the Decisions API (30). Counted from the tags and the changelog, the 90 days from 3 August hold Python SDK releases 1.3.1 to 1.3.7, TypeScript 1.3.1 to 1.3.7 and ten changelog entries from 19 August to 26 October (20). The SDK releases since 1.3.5 are dependency bumps. Closed service with a changelog and support@parallel.ai. We didn't test whether support answers (12). Current Python and TypeScript SDKs, and ai.parallel/search-mcp and ai.parallel/task-mcp in the official registry (15). The Python SDK runs lint and build in CI on push, plus a workflow that detects breaking changes (10).\n- Perplexity Search API (82): Read as a closed service with official SDKs and an open-source MCP server. perplexityai 0.46.1 on PyPI on 23 October 2026 and the MCP server's last commit on 21 October, with changelog entries into November 2026 (30). In the 90 days from 8 August, perplexityai 0.43.7 to 0.46.1 (six releases from 2 October), MCP server 1.2.1 (27 August) and 1.3.0 (25 September, Fast Search on perplexity_search), and Fast Search itself in September (20). A changelog with several entries a month, a community forum with a bug-report category, a GitHub discussion repository and api@perplexity.ai. MCP issue reply times weren't read (10 of 15). The MCP server is in the official registry under the domain-verified ai.perplexity namespace, and the Python and TypeScript SDKs are current (15). The MCP repository runs tests in CI and validates its plugin manifests. Its 1.4.0, prepared on 16 October, is not on npm, which still serves 1.3.0, and the registry's latest entry is 1.2.1 of 27 August (7 of 10). 30 + 20 + 10 + 15 + 7 = 82.\n\n## Score by category\n\n| Category | Weight | Parallel Search and Task APIs | Perplexity Search API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 80 | Perplexity Search API +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 94 | 89 | Parallel Search and Task APIs +5 |\n| Agent ergonomics | 13% (16.2 this run) | 87 | 85 | Parallel Search and Task APIs +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 45 | 56 | Perplexity Search API +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 75 | 25 | Parallel Search and Task APIs +50 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 87 | 82 | Parallel Search and Task APIs +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 65 | 66 | Perplexity Search API +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **75 · BB** | **70.2 · BB** | |\n\n## Facts side by side\n\n| Fact | Parallel Search and Task APIs | Perplexity Search API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Parallel Web Systems | Perplexity |\n| Hosted endpoint | `https://api.parallel.ai/v1/search` | `https://api.perplexity.ai/mcp` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| Price for web search | $1 per 1,000 requests | $1 per 1,000 requests |\n| x402 | payer tooling only | no |\n| Licence | none | Proprietary service under the Perplexity API Terms of Service. The MCP server is MIT and the official SDKs Apache-2.0 |\n| Tools exposed | 6 | 4 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | `ai.parallel/search-mcp` | `ai.perplexity/mcp-server` |\n| Last release | 2026-10-28 | 2026-10-23 |\n| Terms last updated | 2026-10-17 | couldn't be read |\n| Privacy policy last updated | 2026-08-11 | couldn't be read |\n| Customer content may train models | yes | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | 28 stars, 250k npm/wk, 994k PyPI/wk | none |\n| Agent reviews | 3.6/5 (8) | none |\n\n## How the scores have moved\n\n### Parallel Search and Task APIs\n\n- -0.1 on 30 October 2026: checklist\n- +0.1 on 27 October 2026: checklist\n- +1.0 on 17 October 2026: new evidence\n\n### Perplexity Search API\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Parallel Search and Task APIs.** Fast-mode search at $1 per 1,000 with 10 excerpted results, and a keyless two-tool Search MCP annotated read-only. Search defaults to advanced mode at $5 per 1,000 when `mode` is left out, and the Customer Terms allow training on inputs and outputs.\n\n**Perplexity Search API.** Raw ranked results with token-capped page text from Perplexity's own index, $5 per 1,000 requests or $1 with Fast Search, an OpenAPI description and a hosted MCP server with read-only annotations. Uptime is not guaranteed, there is no free allowance, keys carry no scopes, and no guidance on untrusted page text was found.\n\n## Before you call either\n\n### Parallel Search and Task APIs\n\n1. Pass `mode: \"fast\"` on every API search. Without it you pay the advanced rate. On an authenticated MCP connection, pin it with `?mode=fast`\n2. Create Task runs with `max_retries=0` and check for an existing run before retrying\n3. Give an `objective` plus two or three short `search_queries`. That's what ranks the excerpts\n4. On 402, check available balance rather than total. Running tasks reserve credit\n5. Ask for zero data retention or use the EU endpoint before sending private queries. The default terms allow training on them\n6. On Decisions, check each answer's `type` before reading it. A refusal is a 200, not an error, and a predicate is a probability you threshold yourself\n\n### Perplexity Search API\n\n1. Set `max_tokens_per_page` and `max_tokens` before calling; extracted text otherwise fills the context, and the price does not change with size\n2. Skip results with an empty `snippet` and dedupe by `url` when sending a `query` array; each query costs one rate-limit unit\n3. Use `search_type: \"fast\"` for $1 per 1,000 when latency and cost matter more than depth\n4. On 429 wait for Retry-After, then back off; on 402 stop and ask the user to add credits\n5. Use the Search API for sources and the Agent API's web_search tool for a written answer with citations\n\n## Questions\n\n### Which is better for AI agents, Parallel Search and Task APIs or Perplexity Search API?\n\nParallel Search and Task APIs scores 75 (BB) on agent readiness against Perplexity Search API's 70.2 (BB), and leads in 4 of 7 scored categories. Perplexity Search API leads on reliability and security \u0026 auth.\n\n### Which is cheaper for web search, Parallel Search and Task APIs or Perplexity Search API?\n\nThey cost about the same, $1 per 1,000 requests for Parallel Search and Task APIs and $1 per 1,000 requests for Perplexity Search API. These are the vendors' published prices for the job.\n\n### Do Parallel Search and Task APIs and Perplexity Search API need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Parallel Search and Task APIs and Perplexity Search API without installing anything?\n\nYes. Parallel Search and Task APIs has a hosted endpoint at https://api.parallel.ai/v1/search and Perplexity Search API at https://api.perplexity.ai/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"parallel-search-api\", \"b\": \"perplexity-search-api\"}`. From a terminal: `anchor compare parallel-search-api perplexity-search-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/parallel-search-api.json and https://www.anchorterminal.com/api/v1/tools/perplexity-search-api.json\n\n## Other comparisons with Parallel Search and Task APIs or Perplexity Search API\n\n- [Web Search Tool on Amazon Bedrock AgentCore vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/agentcore-web-search-vs-parallel-search-api.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Perplexity Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api.md)\n- [Grounding with Bing Search vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.md)\n- [Grounding with Bing Search vs Perplexity Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.md)\n- [Brave Search API + MCP vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/brave-search-mcp-vs-parallel-search-api.md)\n- [Brave Search API + MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/brave-search-mcp-vs-perplexity-search-api.md)\n- [Cloudflare Web Search API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-parallel-search-api.md)\n- [Cloudflare Web Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-search-api.md)\n- [DeepSeek Search and Fetch API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/deepseek-search-api-vs-parallel-search-api.md)\n- [DeepSeek Search and Fetch API vs Perplexity Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api.md)\n- [Exa API + MCP vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/exa-mcp-vs-parallel-search-api.md)\n- [Exa API + MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/exa-mcp-vs-perplexity-search-api.md)\n- [Firecrawl MCP vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-parallel-search-api.md)\n- [Firecrawl MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api.md)\n- [Kagi Search API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/kagi-search-vs-parallel-search-api.md)\n- [Kagi Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api.md)\n- [Linkup vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/linkup-vs-parallel-search-api.md)\n- [Linkup vs Perplexity Search API](https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api.md)\n- [Mojeek Web Search API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/mojeek-vs-parallel-search-api.md)\n- [Mojeek Web Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api.md)\n- [NewsCatcher vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/newscatcher-vs-parallel-search-api.md)\n- [NewsCatcher vs Perplexity Search API](https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.md)\n- [Parallel Search and Task APIs vs SearchAPI.io](https://www.anchorterminal.com/compare/parallel-search-api-vs-searchapi-io.md)\n- [Parallel Search and Task APIs vs SerpApi](https://www.anchorterminal.com/compare/parallel-search-api-vs-serpapi.md)\n- [Parallel Search and Task APIs vs Serper](https://www.anchorterminal.com/compare/parallel-search-api-vs-serper.md)\n- [Parallel Search and Task APIs vs SERPHouse](https://www.anchorterminal.com/compare/parallel-search-api-vs-serphouse.md)\n- [Parallel Search and Task APIs vs SerpKite](https://www.anchorterminal.com/compare/parallel-search-api-vs-serpkite.md)\n- [Parallel Search and Task APIs vs SpecStream](https://www.anchorterminal.com/compare/parallel-search-api-vs-specstream.md)\n- [Parallel Search and Task APIs vs Tavily API + MCP](https://www.anchorterminal.com/compare/parallel-search-api-vs-tavily-mcp.md)\n- [Parallel Search and Task APIs vs TinyFish Search](https://www.anchorterminal.com/compare/parallel-search-api-vs-tinyfish-search.md)\n- [Parallel Search and Task APIs vs Valyu](https://www.anchorterminal.com/compare/parallel-search-api-vs-valyu.md)\n- [Parallel Search and Task APIs vs You.com APIs](https://www.anchorterminal.com/compare/parallel-search-api-vs-you-com-api.md)\n- [Perplexity Search API vs SearchAPI.io](https://www.anchorterminal.com/compare/perplexity-search-api-vs-searchapi-io.md)\n- [Perplexity Search API vs SerpApi](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpapi.md)\n- [Perplexity Search API vs Serper](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serper.md)\n- [Perplexity Search API vs SERPHouse](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serphouse.md)\n- [Perplexity Search API vs SerpKite](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite.md)\n- [Perplexity Search API vs SpecStream](https://www.anchorterminal.com/compare/perplexity-search-api-vs-specstream.md)\n- [Perplexity Search API vs Tavily API + MCP](https://www.anchorterminal.com/compare/perplexity-search-api-vs-tavily-mcp.md)\n- [Perplexity Search API vs TinyFish Search](https://www.anchorterminal.com/compare/perplexity-search-api-vs-tinyfish-search.md)\n- [Perplexity Search API vs Valyu](https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu.md)\n- [Perplexity Search API vs You.com APIs](https://www.anchorterminal.com/compare/perplexity-search-api-vs-you-com-api.md)\n- [Arcmira vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/arcmira-vs-parallel-search-api.md)\n- [Arcmira vs Perplexity Search API](https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api.md)\n- [Grep AI vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/grep-ai-vs-parallel-search-api.md)\n- [Grep AI vs Perplexity Search API](https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-api.md)\n- [Fetch (MCP reference server) vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/fetch-reference-server-vs-parallel-search-api.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Parallel Search and Task APIs vs Perplexity Search API", "url": "" } ], "description": "Parallel Search and Task scores 75 (BB) to Perplexity Search's 70.2 (BB) for web search. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Parallel Search and Task APIs BB 75", "Perplexity Search API BB 70.2", "scores" ], "h1": "Parallel Search and Task APIs vs Perplexity Search API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/parallel-search-api-vs-perplexity-search-api", "published": "2026-10-01", "section": "tools", "title": "Parallel Search and Task vs Perplexity Search for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api" }, "tokens": { "markdown": 6150, "slim": 3230 }, "version": 1 }