{ "data": { "a": { "slug": "newscatcher", "name": "NewsCatcher", "vendor": "NewsCatcher, Inc.", "vendorUrl": "https://www.newscatcherapi.com", "kind": "http-api", "category": "search", "summary": "NewsCatcher's API searches the last 30 days of news in every language, grouped into stories, and runs a background agent that builds tables of events or company news, through REST and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/newscatcher", "markdownUrl": "https://www.anchorterminal.com/tools/newscatcher.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/newscatcher.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/newscatcher.json", "dns": "newscatcher.grade.anchorterminal.com", "repo": "https://github.com/Newscatcher/newscatcher-mcp", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.newscatcherapi.com/mcp", "packages": [], "auth": "api-key", "authNotes": "API key from the NewsCatcher platform after a browser signup, sent in the `x-api-key` header. One key works for the News API and the agent; several keys can be made and revoked in the platform. The MCP server also accepts `Authorization: Bearer` or `?apiKey=` in the URL; OAuth is announced as coming soon. No scopes found.", "pricing": "usage", "pricingNotes": "Prepaid credits at $1 per 1,000 (top-ups from $25, valid 12 months). Search costs 1, 5 or 10 credits by effort, a story 1, `/articles` 5 per call. Agent runs 1,000 to 6,000 credits. 10,000 free credits every 30 days. Failed and refused requests aren't charged.", "priceSummary": "$1 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the docs, the pricing page or the OpenAPI specs (checked 2026-11-06). An empty balance returns 402 with no payment requirements; top-ups go through the platform.", "endpoints": [] }, "toolCount": 15, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://www.newscatcherapi.com/docs/get-started/overview", "llmsTxt": "https://www.newscatcherapi.com/docs/llms.txt", "openapi": "https://github.com/NewscatcherAPI/docs/blob/main/api-reference/news-api/openapi.json", "capabilities": [ "search.news", "search.research", "web.search" ], "tags": [ "hosted", "usage", "prepaid", "free-tier", "mcp", "remote-mcp", "openapi", "llms-txt", "status-page", "yc" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 67.5, "grade": "B", "agentReady": false, "rank": 322, "ranked": true, "rankOf": 1510, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 84, "maintenance": 76, "payments": 30, "reliability": 67, "schema": 94, "security": 45, "transparency": 79 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "One key and one credit balance cover a ranked news search, a background research agent and a hosted MCP server with toolsets and annotated tools, under OpenAPI 3.1 specs and a dated changelog. The current API launched on 30 October 2026, the MCP server accepts the key in its URL, and no SLA is published below Enterprise.", "bestFor": "Agents that need current news across languages, grouped into stories, or tables of events and company news on a schedule.", "strengths": [ "OpenAPI 3.1 specs for the News API and the agent, llms.txt, Markdown pages and a docs MCP server", "Hosted MCP server with 15 tools in four toolsets, selectable with `?tools=`, and read-only, destructive and idempotent hints on every tool", "Documented errors with retry advice per status, 429 with Retry-After, and refused or failed requests never charged", "Published credit prices, $1 per 1,000 credits, and 10,000 free credits every 30 days", "Terms say inputs and generated data are never used to train models, with a dated sub-processor list" ], "weaknesses": [ "The current News API and agent launched on 30 October 2026 and the MCP repository went public on 6 November 2026", "The MCP server documents `?apiKey=` in the URL for clients without headers, and keys have no scopes found", "No SLA below a signed Enterprise agreement; the status page monitors one News API component", "API logs, which can include query text, are archived indefinitely after 90 days", "The pricing page and the docs disagree on whether empty agent runs are charged and on the price of `/articles`" ], "agentNotes": [ "Send the key in the `x-api-key` header, and use a separate key for the MCP server so it can be revoked alone", "Call `start_research` with `dry_run` first, since agent runs cost 1,000 to 6,000 credits", "Use `effort=low` for quick lookups; the default `medium` costs five times as much", "Use `/articles` or `list_articles` for news older than 30 days or exact counts; `/search` covers 30 days only", "On 429 or 503 wait for Retry-After, and quote the Correlation-ID header to support" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.5 } ], "editorialScores": { "ergonomics": 84, "maintenance": 76, "payments": 30, "reliability": 67, "schema": 94, "security": 45, "transparency": 73 }, "provenanceScore": 85, "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": { "http": "curl -X POST \"https://api.newscatcherapi.com/news-api/search\" \\\n -H \"x-api-key: $NEWSCATCHER_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"q\": \"hurricane recovery florida\", \"limit\": 5}'", "claudeCode": "claude mcp add --transport http newscatcher https://mcp.newscatcherapi.com/mcp --header \"x-api-key: YOUR_API_KEY\"", "config": { "mcpServers": { "newscatcher": { "headers": { "x-api-key": "YOUR_API_KEY" }, "url": "https://mcp.newscatcherapi.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/search.news", "tool": "https://letme.dev/newscatcher" }, "area": "web-data", "unitPrices": [ { "item": "News search, low effort", "unit": "1k-requests", "usd": 1, "note": "1 credit a search at $1 per 1,000 credits" }, { "item": "News search, medium effort (default)", "unit": "1k-requests", "usd": 5, "note": "5 credits" }, { "item": "News search, high effort", "unit": "1k-requests", "usd": 10, "note": "10 credits" }, { "item": "Articles listing", "unit": "1k-requests", "usd": 5, "note": "5 credits a call per the docs; the pricing page says 15 a page" }, { "item": "Agent event research, fast run", "unit": "tx", "usd": 1, "note": "1,000 credits, 50 rows included; standard $3, max $6" }, { "item": "Credit", "unit": "credit", "usd": 0.001, "note": "Top-ups from $25 for 25,000 credits, valid 12 months" } ], "provenance": { "legalEntity": "NewsCatcher, Inc.", "domain": "newscatcherapi.com", "domainRegistered": "2020-02-16", "endpointOnVendorDomain": true, "terms": "https://www.newscatcherapi.com/company/legal/terms-and-conditions", "privacy": "https://www.newscatcherapi.com/company/legal/privacy-policy", "statusPage": "https://status.newscatcherapi.com/", "changelog": "https://www.newscatcherapi.com/docs/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The service terms (Terms and Conditions) and the website Terms of Service are both dated 2 November 2026 and name NewsCatcher, Inc. under Delaware law.", "The website Terms of Service forbid using the site or its content 'to spam, phish, pharm, pretext, spider, crawl, or scrape'. Recorded as a fact; only public pages were read, within robots.txt.", "www.newscatcherapi.com/robots.txt disallows /~gitbook, /*?ref= and /api/ for all agents; none of the pages read is under those paths. status.newscatcherapi.com allows all.", "/.well-known/security.txt answers 404. The MCP repository's SECURITY.md takes private reports through GitHub with a 3-business-day acknowledgement target.", "Status page on Hyperping with one News API component, 99.820% uptime for August to November 2026 and one incident in the 90 days, on 1 September 2026.", "RDAP gives newscatcherapi.com a registration date of 16 February 2020." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/newscatcher.json", "live": { "slug": "newscatcher", "probe": { "target": "https://mcp.newscatcherapi.com/mcp", "method": "get", "lastAt": "2026-11-07T22:56:10.777186743Z", "lastOk": true, "lastStatus": 405, "lastMs": 154, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 167, "p95ms24h": 313, "samples24h": 244, "samples30d": 246, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 233, "ok": 233 } ] }, "vendorStatus": { "page": "https://status.newscatcherapi.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:15.638845153Z" }, "githubStars": 0, "securityTxt": { "url": "https://newscatcherapi.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:58.85886795Z" }, "llmsTxt": { "url": "https://www.newscatcherapi.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:19.853404264Z" }, "pages": [ { "url": "https://www.newscatcherapi.com/docs/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:32:00.60078463Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "849b66383503" }, { "url": "https://www.newscatcherapi.com/company/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:31:56.385466242Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "818e0cf9f82d" }, { "url": "https://www.newscatcherapi.com/company/legal/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:31:58.548719689Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "79f84eff4353" } ], "mcpTools": { "url": "https://mcp.newscatcherapi.com/mcp", "checkedAt": "2026-11-07T01:46:25.078047109Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:25.078047109Z" }, "updatedAt": "2026-11-07T22:56:10.777186743Z" } }, "answer": "Perplexity Search API scores 70.2 (BB) on agent readiness against NewsCatcher's 67.5 (B), and leads in 4 of 7 scored categories. NewsCatcher leads on schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust.", "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": 211, "ranked": true, "rankOf": 1510, "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-07T22:56:14.148158353Z", "lastOk": true, "lastStatus": 401, "lastMs": 151, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 166, "p95ms24h": 279, "samples24h": 244, "samples30d": 246, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 233, "ok": 233 } ] }, "vendorStatus": { "page": "https://status.perplexity.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T22:57:38.131603448Z" }, "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-07T22:57:38.131603448Z" } }, "edges": [ { "by": 13, "category": "reliability", "leads": "perplexity-search-api", "name": "Reliability", "reasons": { "a": "Read with the hosted lines, for the News API, the agent and the hosted MCP server. status.newscatcherapi.com (Hyperping) shows one News API component with 99.820% uptime from August to November 2026 and an incident history. The agent and the MCP server have no component of their own (20). In the 90 days from 8 August, one incident, on 1 September 2026, when the vendor wrote that for about four hours a higher-than-usual number of requests to the production News API timed out because of one client's queries. Read as one major (10). Rate limits published per plan, 1 request a second free and up to 10 on pay as you go, with exact limits from the free `GET /subscription` (15). 429 carries Retry-After with instructions to retry the same request, 503 carries Retry-After, and failed or refused requests are not charged. Agent runs and monitor creation have no idempotency keys (12 of 15). An uptime SLA exists only in signed Enterprise agreements; none is published (0). Generally available since 30 October 2026, with OAuth for the MCP server announced as coming soon (10). 20 + 10 + 15 + 12 + 0 + 10 = 67.", "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": 67, "b": 80 } }, { "by": 13, "category": "transparency", "leads": "newscatcher", "name": "Transparency \u0026 trust", "reasons": { "a": "The API is closed under terms of 2 November 2026 naming NewsCatcher, Inc., and the MCP server is MIT, so between the two bands (20 of 30). The terms say inputs and generated data are not used to train models, a DPA applies automatically, and the privacy policy gives retention periods (server logs 7 days, API logs with query text 90 days, then archived indefinitely, billing records about seven years). They agree with each other, but indefinite archives of query logs hold it back (22 of 30). The terms promise 30 days' email notice before a paid product or API version is discontinued, with refunds of unused credits, and the v3 News API has a migration guide (15 of 20). A sub-processor list dated 2 November 2026 with each provider's location and the data it handles. The MCP repository deploys to Vercel and can send pseudonymised analytics to PostHog, and neither appears on the list (16 of 20). 20 + 22 + 15 + 16 = 73.", "b": "Closed service under terms naming Perplexity AI, Inc. and California law. The MCP server is MIT and the SDKs Apache-2.0 (18 of 30). The terms and DPA say Customer Content and personal data don't train Perplexity's models, the DPA deletes personal data within 30 days of the service ending, and the Privacy and Security page says retention varies by API and zero data retention is not the default. The DPA also says Perplexity Search may follow different data terms, which weren't found, and no retention period for search queries is stated (15 of 30). Sonar Chat Completions support ended on 27 September 2026 with a migration guide and requests reformulated rather than refused, and sonar-reasoning was removed on 15 December 2025 with a named replacement. Notices are dated by month and there is no standing notice period beyond the terms' 30 days for termination (10 of 20). A sub-processor list on the trust centre, which is drawn by script and wasn't read, ten business days' notice of new non-model subprocessors, and SCCs for EU and UK transfers. No data location is stated (8 of 20). 18 + 15 + 10 + 8 = 51." }, "scores": { "a": 79, "b": 66 } }, { "by": 11, "category": "security", "leads": "perplexity-search-api", "name": "Security \u0026 auth", "reasons": { "a": "API keys in the `x-api-key` header, several per account, revocable in the platform, with advice to keep one per application. A 403 for 'a key that may not use this API' suggests per-key API access, but no scopes are documented (20). The MCP server documents `?apiKey=` on the server URL for Claude.ai custom connectors, with a warning, so less 10 (10 of 30). The MCP repository's SECURITY.md says URL keys are rejected unless the operator enables them, which the hosted server does per the docs. Toolsets let an operator load only the read-only `news` tools, write tools carry destructiveHint, and the server tells the assistant to confirm large or hourly agent jobs (14 of 20). Results are third-party article text and summaries, and no prompt-injection guidance was found in the docs or the MCP server's instructions (0 of 15). Every response carries a Correlation-ID, `GET /subscription` shows usage and balance, and runs are listed in the platform. No per-call audit log for the customer was found (7 of 15). The security page and footer claim SOC 2 Type II and link a trust centre on Oneleet, which wasn't read. A vulnerability disclosure policy covers the MCP server. No security.txt (404) and no bug bounty found (14 of 20). 10 + 14 + 0 + 7 + 14 = 45.", "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": 6, "category": "maintenance", "leads": "perplexity-search-api", "name": "Maintenance \u0026 community", "reasons": { "a": "Read for a closed service, with the MCP repository read as code. News API 1.1.0 and Agent 1.5.0 on 4 November 2026, MCP server 0.1.0 on 6 November and v3 News API 3.25.0 on 6 November (30). In the 90 days from 8 August, the 30 October launch, News API 1.1.0, Agent 1.5.0, MCP 0.1.0 and v3 releases 3.19.0 to 3.25.0 (20). Public dated changelogs, support by email and Pylon, and a security policy with a 3-business-day target. The MCP repository is a day old, so there are no issues to judge (10 of 15). The CatchAll MCP server is in the official registry under the verified namespace com.newscatcherapi, but the new server isn't, and no official SDK for the current API was found; the Enterprise APIs list libraries (8 of 15). The MCP repository runs its test suite in CI with a read-only token; pass state not read (8 of 10). 30 + 20 + 10 + 8 + 8 = 76.", "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": 76, "b": 82 } }, { "by": 5, "category": "schema", "leads": "newscatcher", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 for the News API (version 1.3.9, 4 paths) and the agent (version 1.5.1, 33 paths), linked from llms.txt, and typed JSON Schema on every MCP tool through Pydantic (25). llms.txt, a Markdown copy of every page and a docs MCP server (10). MCP tool descriptions say when to use each and which tool to use instead, such as `list_articles` for older news; the REST reference explains each endpoint and the 'Choose an API' page compares them (17 of 20). Inputs are typed with enums for effort, mode and dimensions, length and range limits such as a 500-character query and limit 1 to 100, and required fields marked (13 of 15). Runnable examples in curl, Python and JavaScript, and an error table with retry advice for every status. The agent spec carries no response examples (14 of 15). Versioned APIs with a dated changelog, the latest entries on 4 November 2026, and separate changelogs for the v3 News API and CatchAll (15). 25 + 10 + 17 + 13 + 14 + 15 = 94.", "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": "payments", "leads": "newscatcher", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Credit prices per call published without login, and credits cost $1 per 1,000 through top-ups from $25 (20). 10,000 free credits every 30 days on a $0 plan, and the first top-up moves an account to pay as you go. No page says whether a card is needed to open the free plan, so half (10). A person signs up in the platform in a browser to get a key (0). NewsMCP's keyless tier belongs to a separate product and isn't counted. 0 + 20 + 10 + 0 = 30.", "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": 30, "b": 25 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "NewsCatcher, Inc.", "b": "Perplexity", "name": "Vendor" }, { "a": "https://mcp.newscatcherapi.com/mcp", "b": "https://api.perplexity.ai/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$1 per 1,000 requests", "b": "$1 per 1,000 requests", "name": "Price for web search" }, { "a": "no", "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": "15", "b": "4", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "ai.perplexity/mcp-server", "name": "MCP registry" }, { "a": "2026-11-06", "b": "2026-10-23", "name": "Last release" }, { "a": "2026-11-02", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-11-02", "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": "yes", "b": "couldn't be read", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Perplexity Search API scores 70.2 (BB) on agent readiness against NewsCatcher's 67.5 (B), and leads in 4 of 7 scored categories. NewsCatcher leads on schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, NewsCatcher or Perplexity Search API?" }, { "answer": "They cost about the same, $1 per 1,000 requests for NewsCatcher 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, NewsCatcher or Perplexity Search API?" }, { "answer": "NewsCatcher needs an API key. Perplexity Search API takes an API key or an OAuth sign-in.", "question": "Do NewsCatcher and Perplexity Search API need an API key?" }, { "answer": "Yes. NewsCatcher has a hosted endpoint at https://mcp.newscatcherapi.com/mcp and Perplexity Search API at https://api.perplexity.ai/mcp.", "question": "Can an agent call NewsCatcher and Perplexity Search API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 94 against 89", "Payments \u0026 pricing, 30 against 25", "Transparency \u0026 trust, 79 against 66" ], "also": null, "goodFor": "Agents that need current news across languages, grouped into stories, or tables of events and company news on a schedule.", "slug": "newscatcher", "watchFor": "The current News API and agent launched on 30 October 2026 and the MCP repository went public on 6 November 2026" }, { "aheadOn": [ "Reliability, 80 against 67", "Security \u0026 auth, 56 against 45", "Maintenance \u0026 community, 82 against 76" ], "also": [ "Agent-ready, a grade of BB or better", "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": null, "job": { "capability": "web.search", "name": "Web search" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-newscatcher.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-newscatcher" }, { "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-newscatcher.json", "title": "Grounding with Bing Search vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher" }, { "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-newscatcher.json", "title": "Brave Search API + MCP vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-newscatcher" }, { "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-newscatcher.json", "title": "Cloudflare Web Search API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-newscatcher" }, { "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-newscatcher.json", "title": "DeepSeek Search and Fetch API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-newscatcher" }, { "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-newscatcher.json", "title": "Exa API + MCP vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-newscatcher" }, { "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-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-newscatcher.json", "title": "Kagi Search API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-newscatcher" }, { "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-newscatcher.json", "title": "Linkup vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/linkup-vs-newscatcher" }, { "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-newscatcher.json", "title": "Mojeek Web Search API vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/mojeek-vs-newscatcher" }, { "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-tinyfish-search.json", "title": "NewsCatcher vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.json", "title": "Parallel Search and Task APIs vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-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-newscatcher.json", "title": "Arcmira vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/arcmira-vs-newscatcher" }, { "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-newscatcher.json", "title": "Grep AI vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-newscatcher" }, { "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/liner-mcp-vs-newscatcher.json", "title": "Liner Search MCP vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-search-api.json", "title": "Liner Search MCP vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-specstream.json", "title": "NewsCatcher vs SpecStream", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-searchapi-io.json", "title": "NewsCatcher vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-serpapi.json", "title": "NewsCatcher vs SerpApi", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-serper.json", "title": "NewsCatcher vs Serper", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-serphouse.json", "title": "NewsCatcher vs SERPHouse", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-serpkite.json", "title": "NewsCatcher vs SerpKite", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-tavily-mcp.json", "title": "NewsCatcher vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-valyu.json", "title": "NewsCatcher vs Valyu", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-you-com-api.json", "title": "NewsCatcher vs You.com APIs", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-you-com-api" } ], "panel": null, "scores": [ { "by": 13, "edge": "perplexity-search-api", "key": "reliability", "name": "Reliability", "newscatcher": 67, "perplexity-search-api": 80, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "newscatcher", "key": "schema", "name": "Schema \u0026 documentation", "newscatcher": 94, "perplexity-search-api": 89, "weight": 13 }, { "by": 1, "edge": "perplexity-search-api", "key": "ergonomics", "name": "Agent ergonomics", "newscatcher": 84, "perplexity-search-api": 85, "weight": 13 }, { "by": 11, "edge": "perplexity-search-api", "key": "security", "name": "Security \u0026 auth", "newscatcher": 45, "perplexity-search-api": 56, "weight": 14 }, { "by": 5, "edge": "newscatcher", "key": "payments", "name": "Payments \u0026 pricing", "newscatcher": 30, "perplexity-search-api": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 6, "edge": "perplexity-search-api", "key": "maintenance", "name": "Maintenance \u0026 community", "newscatcher": 76, "perplexity-search-api": 82, "weight": 7 }, { "by": 13, "edge": "newscatcher", "key": "transparency", "name": "Transparency \u0026 trust", "newscatcher": 79, "perplexity-search-api": 66, "weight": 7 } ], "summary": "Perplexity Search API scores 70.2 (BB) on agent readiness against NewsCatcher's 67.5 (B), and leads in 4 of 7 scored categories. NewsCatcher leads on schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust. Both do web search.", "tasks": null, "tutorials": [], "verdicts": { "newscatcher": "One key and one credit balance cover a ranked news search, a background research agent and a hosted MCP server with toolsets and annotated tools, under OpenAPI 3.1 specs and a dated changelog. The current API launched on 30 October 2026, the MCP server accepts the key in its URL, and no SLA is published below Enterprise.", "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/newscatcher-vs-perplexity-search-api", "json": "https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.min.md" }, "markdown": "Perplexity Search API scores 70.2 (BB) on agent readiness against NewsCatcher's 67.5 (B), and leads in 4 of 7 scored categories. NewsCatcher leads on schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust. Both do web search.\n\n- NewsCatcher: grade B, 67.5/100, rank #322 of 1510. Markdown https://www.anchorterminal.com/tools/newscatcher.md · JSON https://www.anchorterminal.com/api/v1/tools/newscatcher.json\n- Perplexity Search API: grade BB, 70.2/100, rank #211 of 1510. 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 326 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\n\n### NewsCatcher (B)\n\nGood for: Agents that need current news across languages, grouped into stories, or tables of events and company news on a schedule.\n\nAhead on:\n- Schema \u0026 documentation, 94 against 89\n- Payments \u0026 pricing, 30 against 25\n- Transparency \u0026 trust, 79 against 66\n\nWatch for: The current News API and agent launched on 30 October 2026 and the MCP repository went public on 6 November 2026\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 67\n- Security \u0026 auth, 56 against 45\n- Maintenance \u0026 community, 82 against 76\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\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### Reliability: Perplexity Search API +13\n\n- NewsCatcher (67): Read with the hosted lines, for the News API, the agent and the hosted MCP server. status.newscatcherapi.com (Hyperping) shows one News API component with 99.820% uptime from August to November 2026 and an incident history. The agent and the MCP server have no component of their own (20). In the 90 days from 8 August, one incident, on 1 September 2026, when the vendor wrote that for about four hours a higher-than-usual number of requests to the production News API timed out because of one client's queries. Read as one major (10). Rate limits published per plan, 1 request a second free and up to 10 on pay as you go, with exact limits from the free `GET /subscription` (15). 429 carries Retry-After with instructions to retry the same request, 503 carries Retry-After, and failed or refused requests are not charged. Agent runs and monitor creation have no idempotency keys (12 of 15). An uptime SLA exists only in signed Enterprise agreements; none is published (0). Generally available since 30 October 2026, with OAuth for the MCP server announced as coming soon (10). 20 + 10 + 15 + 12 + 0 + 10 = 67.\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### Transparency \u0026 trust: NewsCatcher +13\n\n- NewsCatcher (79): The API is closed under terms of 2 November 2026 naming NewsCatcher, Inc., and the MCP server is MIT, so between the two bands (20 of 30). The terms say inputs and generated data are not used to train models, a DPA applies automatically, and the privacy policy gives retention periods (server logs 7 days, API logs with query text 90 days, then archived indefinitely, billing records about seven years). They agree with each other, but indefinite archives of query logs hold it back (22 of 30). The terms promise 30 days' email notice before a paid product or API version is discontinued, with refunds of unused credits, and the v3 News API has a migration guide (15 of 20). A sub-processor list dated 2 November 2026 with each provider's location and the data it handles. The MCP repository deploys to Vercel and can send pseudonymised analytics to PostHog, and neither appears on the list (16 of 20). 20 + 22 + 15 + 16 = 73.\n- Perplexity Search API (66): Closed service under terms naming Perplexity AI, Inc. and California law. The MCP server is MIT and the SDKs Apache-2.0 (18 of 30). The terms and DPA say Customer Content and personal data don't train Perplexity's models, the DPA deletes personal data within 30 days of the service ending, and the Privacy and Security page says retention varies by API and zero data retention is not the default. The DPA also says Perplexity Search may follow different data terms, which weren't found, and no retention period for search queries is stated (15 of 30). Sonar Chat Completions support ended on 27 September 2026 with a migration guide and requests reformulated rather than refused, and sonar-reasoning was removed on 15 December 2025 with a named replacement. Notices are dated by month and there is no standing notice period beyond the terms' 30 days for termination (10 of 20). A sub-processor list on the trust centre, which is drawn by script and wasn't read, ten business days' notice of new non-model subprocessors, and SCCs for EU and UK transfers. No data location is stated (8 of 20). 18 + 15 + 10 + 8 = 51.\n\n### Security \u0026 auth: Perplexity Search API +11\n\n- NewsCatcher (45): API keys in the `x-api-key` header, several per account, revocable in the platform, with advice to keep one per application. A 403 for 'a key that may not use this API' suggests per-key API access, but no scopes are documented (20). The MCP server documents `?apiKey=` on the server URL for Claude.ai custom connectors, with a warning, so less 10 (10 of 30). The MCP repository's SECURITY.md says URL keys are rejected unless the operator enables them, which the hosted server does per the docs. Toolsets let an operator load only the read-only `news` tools, write tools carry destructiveHint, and the server tells the assistant to confirm large or hourly agent jobs (14 of 20). Results are third-party article text and summaries, and no prompt-injection guidance was found in the docs or the MCP server's instructions (0 of 15). Every response carries a Correlation-ID, `GET /subscription` shows usage and balance, and runs are listed in the platform. No per-call audit log for the customer was found (7 of 15). The security page and footer claim SOC 2 Type II and link a trust centre on Oneleet, which wasn't read. A vulnerability disclosure policy covers the MCP server. No security.txt (404) and no bug bounty found (14 of 20). 10 + 14 + 0 + 7 + 14 = 45.\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### Maintenance \u0026 community: Perplexity Search API +6\n\n- NewsCatcher (76): Read for a closed service, with the MCP repository read as code. News API 1.1.0 and Agent 1.5.0 on 4 November 2026, MCP server 0.1.0 on 6 November and v3 News API 3.25.0 on 6 November (30). In the 90 days from 8 August, the 30 October launch, News API 1.1.0, Agent 1.5.0, MCP 0.1.0 and v3 releases 3.19.0 to 3.25.0 (20). Public dated changelogs, support by email and Pylon, and a security policy with a 3-business-day target. The MCP repository is a day old, so there are no issues to judge (10 of 15). The CatchAll MCP server is in the official registry under the verified namespace com.newscatcherapi, but the new server isn't, and no official SDK for the current API was found; the Enterprise APIs list libraries (8 of 15). The MCP repository runs its test suite in CI with a read-only token; pass state not read (8 of 10). 30 + 20 + 10 + 8 + 8 = 76.\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### Schema \u0026 documentation: NewsCatcher +5\n\n- NewsCatcher (94): OpenAPI 3.1 for the News API (version 1.3.9, 4 paths) and the agent (version 1.5.1, 33 paths), linked from llms.txt, and typed JSON Schema on every MCP tool through Pydantic (25). llms.txt, a Markdown copy of every page and a docs MCP server (10). MCP tool descriptions say when to use each and which tool to use instead, such as `list_articles` for older news; the REST reference explains each endpoint and the 'Choose an API' page compares them (17 of 20). Inputs are typed with enums for effort, mode and dimensions, length and range limits such as a 500-character query and limit 1 to 100, and required fields marked (13 of 15). Runnable examples in curl, Python and JavaScript, and an error table with retry advice for every status. The agent spec carries no response examples (14 of 15). Versioned APIs with a dated changelog, the latest entries on 4 November 2026, and separate changelogs for the v3 News API and CatchAll (15). 25 + 10 + 17 + 13 + 14 + 15 = 94.\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### Payments \u0026 pricing: NewsCatcher +5\n\n- NewsCatcher (30): No x402, MPP or L402 (0). Credit prices per call published without login, and credits cost $1 per 1,000 through top-ups from $25 (20). 10,000 free credits every 30 days on a $0 plan, and the first top-up moves an account to pay as you go. No page says whether a card is needed to open the free plan, so half (10). A person signs up in the platform in a browser to get a key (0). NewsMCP's keyless tier belongs to a separate product and isn't counted. 0 + 20 + 10 + 0 = 30.\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## Score by category\n\n| Category | Weight | NewsCatcher | Perplexity Search API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 67 | 80 | Perplexity Search API +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 94 | 89 | NewsCatcher +5 |\n| Agent ergonomics | 13% (16.2 this run) | 84 | 85 | Perplexity Search API +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 45 | 56 | Perplexity Search API +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 25 | NewsCatcher +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 76 | 82 | Perplexity Search API +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 79 | 66 | NewsCatcher +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **67.5 · B** | **70.2 · BB** | |\n\n## Facts side by side\n\n| Fact | NewsCatcher | Perplexity Search API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | NewsCatcher, Inc. | Perplexity |\n| Hosted endpoint | `https://mcp.newscatcherapi.com/mcp` | `https://api.perplexity.ai/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for web search | $1 per 1,000 requests | $1 per 1,000 requests |\n| x402 | no | 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 | 15 | 4 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `ai.perplexity/mcp-server` |\n| Last release | 2026-11-06 | 2026-10-23 |\n| Terms last updated | 2026-11-02 | couldn't be read |\n| Privacy policy last updated | 2026-11-02 | 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 | yes | couldn't be read |\n\n## Verdicts\n\n**NewsCatcher.** One key and one credit balance cover a ranked news search, a background research agent and a hosted MCP server with toolsets and annotated tools, under OpenAPI 3.1 specs and a dated changelog. The current API launched on 30 October 2026, the MCP server accepts the key in its URL, and no SLA is published below Enterprise.\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### NewsCatcher\n\n1. Send the key in the `x-api-key` header, and use a separate key for the MCP server so it can be revoked alone\n2. Call `start_research` with `dry_run` first, since agent runs cost 1,000 to 6,000 credits\n3. Use `effort=low` for quick lookups; the default `medium` costs five times as much\n4. Use `/articles` or `list_articles` for news older than 30 days or exact counts; `/search` covers 30 days only\n5. On 429 or 503 wait for Retry-After, and quote the Correlation-ID header to support\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, NewsCatcher or Perplexity Search API?\n\nPerplexity Search API scores 70.2 (BB) on agent readiness against NewsCatcher's 67.5 (B), and leads in 4 of 7 scored categories. NewsCatcher leads on schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust.\n\n### Which is cheaper for web search, NewsCatcher or Perplexity Search API?\n\nThey cost about the same, $1 per 1,000 requests for NewsCatcher and $1 per 1,000 requests for Perplexity Search API. These are the vendors' published prices for the job.\n\n### Do NewsCatcher and Perplexity Search API need an API key?\n\nNewsCatcher needs an API key. Perplexity Search API takes an API key or an OAuth sign-in.\n\n### Can an agent call NewsCatcher and Perplexity Search API without installing anything?\n\nYes. NewsCatcher has a hosted endpoint at https://mcp.newscatcherapi.com/mcp 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/newscatcher-vs-perplexity-search-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"newscatcher\", \"b\": \"perplexity-search-api\"}`. From a terminal: `anchor compare newscatcher perplexity-search-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/newscatcher.json and https://www.anchorterminal.com/api/v1/tools/perplexity-search-api.json\n\n## Other comparisons with NewsCatcher or Perplexity Search API\n\n- [Web Search Tool on Amazon Bedrock AgentCore vs NewsCatcher](https://www.anchorterminal.com/compare/agentcore-web-search-vs-newscatcher.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 NewsCatcher](https://www.anchorterminal.com/compare/bing-grounding-vs-newscatcher.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 NewsCatcher](https://www.anchorterminal.com/compare/brave-search-mcp-vs-newscatcher.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 NewsCatcher](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-newscatcher.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 NewsCatcher](https://www.anchorterminal.com/compare/deepseek-search-api-vs-newscatcher.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 NewsCatcher](https://www.anchorterminal.com/compare/exa-mcp-vs-newscatcher.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 Perplexity Search API](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api.md)\n- [Kagi Search API vs NewsCatcher](https://www.anchorterminal.com/compare/kagi-search-vs-newscatcher.md)\n- [Kagi Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api.md)\n- [Linkup vs NewsCatcher](https://www.anchorterminal.com/compare/linkup-vs-newscatcher.md)\n- [Linkup vs Perplexity Search API](https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api.md)\n- [Mojeek Web Search API vs NewsCatcher](https://www.anchorterminal.com/compare/mojeek-vs-newscatcher.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 TinyFish Search](https://www.anchorterminal.com/compare/newscatcher-vs-tinyfish-search.md)\n- [Parallel Search and Task APIs vs Perplexity Search API](https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-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 NewsCatcher](https://www.anchorterminal.com/compare/arcmira-vs-newscatcher.md)\n- [Arcmira vs Perplexity Search API](https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api.md)\n- [Grep AI vs NewsCatcher](https://www.anchorterminal.com/compare/grep-ai-vs-newscatcher.md)\n- [Grep AI vs Perplexity Search API](https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-api.md)\n- [Liner Search MCP vs NewsCatcher](https://www.anchorterminal.com/compare/liner-mcp-vs-newscatcher.md)\n- [Liner Search MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-search-api.md)\n- [NewsCatcher vs SpecStream](https://www.anchorterminal.com/compare/newscatcher-vs-specstream.md)\n- [NewsCatcher vs SearchAPI.io](https://www.anchorterminal.com/compare/newscatcher-vs-searchapi-io.md)\n- [NewsCatcher vs SerpApi](https://www.anchorterminal.com/compare/newscatcher-vs-serpapi.md)\n- [NewsCatcher vs Serper](https://www.anchorterminal.com/compare/newscatcher-vs-serper.md)\n- [NewsCatcher vs SERPHouse](https://www.anchorterminal.com/compare/newscatcher-vs-serphouse.md)\n- [NewsCatcher vs SerpKite](https://www.anchorterminal.com/compare/newscatcher-vs-serpkite.md)\n- [NewsCatcher vs Tavily API + MCP](https://www.anchorterminal.com/compare/newscatcher-vs-tavily-mcp.md)\n- [NewsCatcher vs Valyu](https://www.anchorterminal.com/compare/newscatcher-vs-valyu.md)\n- [NewsCatcher vs You.com APIs](https://www.anchorterminal.com/compare/newscatcher-vs-you-com-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": "NewsCatcher vs Perplexity Search API", "url": "" } ], "description": "Perplexity Search scores 70.2 (BB) to NewsCatcher's 67.5 (B) for web search. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "NewsCatcher B 67.5", "Perplexity Search API BB 70.2", "scores" ], "h1": "NewsCatcher vs Perplexity Search API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/newscatcher-vs-perplexity-search-api", "published": "2026-10-01", "section": "tools", "title": "NewsCatcher vs Perplexity Search for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api" }, "tokens": { "markdown": 6500, "slim": 3880 }, "version": 1 }