# Linkup vs NewsCatcher (slim)

> Linkup and NewsCatcher score within a point of each other for web search, 68 and 67.5 out of 100. NewsCatcher is cheaper for web search, $1 against $5 per 1,000 requests. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/linkup-vs-newscatcher.md (~5,050 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/linkup-vs-newscatcher.json · canonical https://www.anchorterminal.com/compare/linkup-vs-newscatcher
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Linkup and NewsCatcher score within a point of each other on agent readiness, 68 (B) and 67.5 (B). NewsCatcher leads on schema & documentation, agent ergonomics, security & auth and transparency & trust. Both do web search. NewsCatcher is cheaper for web search, $1 against $5 per 1,000 requests. Linkup accepts x402. NewsCatcher doesn't.

- Linkup: B 68, rank #297 of 1486 · https://www.anchorterminal.com/tools/linkup.min.md
- NewsCatcher: B 67.5, rank #321 of 1486 · https://www.anchorterminal.com/tools/newscatcher.min.md
- Linkup, good for Agents that want a cited answer or schema-shaped output from one search call at a fixed price, and for European buyers who want a French vendor with zero retention on request. Ahead on Payments & pricing, 80 against 30. Also An agent can pay per call over x402, with no account; Runs on your own machine.
- NewsCatcher, good for Agents that need current news across languages, grouped into stories, or tables of events and company news on a schedule. Ahead on Schema & documentation, 94 against 88; Agent ergonomics, 84 against 76; Security & auth, 45 against 32; Transparency & trust, 79 against 61. Also Cheaper for web search, $1 against $5 per 1,000 requests.

| Category | Linkup | NewsCatcher |
| --- | --- | --- |
| Reliability (16%) | 70 | 67 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 88 | 94 |
| Agent ergonomics (13%) | 76 | 84 |
| Security & auth (14%) | 32 | 45 |
| Payments & pricing (10%) | 80 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 76 |
| Transparency & trust (7%) | 61 | 79 |

| Fact (where they differ) | Linkup | NewsCatcher |
| --- | --- | --- |
| Vendor | Linkup | NewsCatcher, Inc. |
| Hosted endpoint | `https://api.linkup.so/v1/search` | `https://mcp.newscatcherapi.com/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| Price for web search | $5 per 1,000 requests | $1 per 1,000 requests |
| x402 | yes, from $0.01/call | no |
| Tools exposed | 4 | 15 |
| Read-only variant documented | no | yes |
| MCP registry | `so.linkup.mcp/linkup-mcp-server` | not listed |
| Last release | 2026-09-30 | 2026-11-06 |
| Terms last updated | 2025-08-01 | 2026-11-02 |
| Privacy policy last updated | 2025-04-01 | 2026-11-02 |
| Terms restrict benchmarking | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 29 stars, 54k npm/wk, 84k PyPI/wk | none |
| Agent reviews | 4/5 (2) | none |

Why the edge:
- Payments & pricing, Linkup +50: Linkup 80 (x402 on Linkup's own /v1/search and /v1/fetch at a flat $0.01 in USDC on Base, not on research or extract, so partial (30). Per-call prices published without login (20). $20 of credit topped up monthly for work-email signups. The docs don't say whether a card is needed, so half credit (10). An agent can pay by x402 with no account (20).); 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.)
- Transparency & trust, NewsCatcher +18: Linkup 61 (The API is closed with published terms, and the MCP server is MIT (20). Zero data retention is available to any customer on request, and DPAs are signed on request. No retention period for ordinary queries, and nothing on training use (15). No deprecation policy or dated notices found (0). Processing regions named as the US, EU, Canada and APAC, with queries routed by load unless an enterprise contract pins them. No subprocessor list (10).); 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.)
- Security & auth, NewsCatcher +13: Linkup 32 (One Bearer key per organisation. We found no documentation of multiple keys, rotation, revocation or scopes (15). The MCP README documents `?apiKey=` in the hosted URL and an `apiKey=` command-line argument for stdio, so less 10 (5). Every action is a read, but the MCP server has no tool subsets (15). Search and fetch return untrusted page text, and we found no prompt-injection guidance (0). No per-call audit log found (0). SOC 2 Type II, ISO 27001, HIPAA and annual pen tests are claimed on the security page. No security.txt, no bug bounty, and contact@linkup.so is the only security contact (12).); 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.)
- Agent ergonomics, NewsCatcher +8: Linkup 76 (Four tools, search, fetch, research and research polling, compact. Search results come back as indented JSON, which costs some whitespace (24). `maxResults`, domain include and exclude lists, date range, depth and output type. No result pagination (18). Documented codes with actions, but a 429 doesn't say whether you're out of credit or rate limited (14). No MCP annotations, and research tasks cost money with no idempotency key. Searches are safe to repeat (5). Only `query` is required and `depth` defaults to fast. Python and JavaScript SDKs (15).); NewsCatcher 84 (15 MCP tools in four toolsets, chosen per connection with `?tools=`, and tools return compact text rather than the full JSON. 15 for 11 to 30 tools plus 7 for toolsets (22 of 25). `limit`, `search_window`, effort, language, country, publisher, coverage and content-type filters, sorting, and paging on `/articles`; agent tables come back up to 200 rows at a time over MCP (20). Every status is documented with whether to retry; the agent returns stable `code` values, while the News API body has a `status_code` and a message meant for people (17 of 20). Every tool carries readOnlyHint and idempotentHint, writes carry destructiveHint, `start_research` has a free `dry_run`, and refused or failed calls aren't charged. No idempotency key for starting runs (17 of 20). Only `q` is required, with medium effort and a 7-day window as defaults. No official SDK for the current API was found; the docs show raw HTTP in three languages (8 of 15). 22 + 20 + 17 + 17 + 8 = 84.)
- Schema & documentation, NewsCatcher +6: Linkup 88 (OpenAPI at api.linkup.so/v1/openapi.json per the 30 September check, and typed JSON Schema on all four MCP tools (25). llms.txt and Markdown pages (10). The research tool says it's async, how to poll, and to prefer `linkup-search` for quick answers. The search tool lists what to use it for but not when not to (17). Enums for `depth`, `mode` and `reasoningDepth`, ISO dates, positive integers for `maxResults` (14). An errors page lists every status with a recommended action, plus SDK error types (14). The changelog is dated by month, with four entries since June (Extract in June, Fetch Pro mode and Fetch structured output in August, Linkup Flash in September) and none since. Versioning is the /v1 path only (8).); 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.)