Head to head · Web search · October 2026 research run

Brave Search API + MCP vs Linkup

Linkup scores 68.4 (B) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 3 of 7 scored categories. Brave Search API + MCP leads on reliability, security & auth and transparency & trust. Both do web search. Linkup accepts x402. Brave Search API + MCP doesn't.

Best web search APIs for AI agents · All 353 search comparisons

Which one, for what

Brave Search API + MCP B

Best for Agents that want an independent, non-Google index at a flat price, or that want page text in one call through LLM Context.

Ahead on

  • Reliability, 80 against 70
  • Security & auth, 58 against 32
  • Transparency & trust, 81 against 61

Also in its favour

  • Open source

Watch for

The x402 pay-per-call proxy answered 404 on 1 November 2026, and its guide is gone from the docs

Linkup B

Best 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

  • Schema & documentation, 88 against 72
  • Payments & pricing, 83 against 30

Also in its favour

  • An agent can pay per call over x402, with no account
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
  • No incidents deducted, where Brave Search API + MCP loses 3 points for them

Watch for

429 covers both exhausted credit and rate limiting, with no Retry-After

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Linkup +53

Brave Search API + MCP 30

No machine payment on 1 November. The x402 proxy at search.agent.s.brave.app answers 404 on its root, llms.txt, OpenAPI file and the web search and LLM Context paths it sold on 1 October, the agent payments guide answers 404, and neither llms.txt nor brave.com/search/api mentions x402 (0). $5 per 1,000 searches and $4 per 1,000 Answers requests plus tokens, published without login (20). The $5 monthly credit needs a card on file, which brave.com says is to prevent abuse (0). A person signs up and adds a card before getting a key, so no autonomous route remains (0). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Linkup 83

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). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 30 of 40 is 7.5 of 10, and the other lines' 50 is 75 at 30 each, so 80 is 83.

Security & auth Brave Search API + MCP +26

Brave Search API + MCP 58

Plain API keys in the X-Subscription-Token header. Several keys per account, revocable from the dashboard, with rotation advice, but no scopes (20). Read-only by nature, with tool allow and deny lists in the MCP server. The HTTP transport binds to 127.0.0.1 and checks Origin (18). Results are untrusted web text and LLM Context returns page content, and we found no prompt-injection guidance in the API docs or the MCP README (0). No per-call audit log found. Rate-limit headers show quota use only (0). SOC 2 Type II attestation, a HackerOne bounty, a pen test in April 2025 and a security.txt at brave.com that names a contact and the HackerOne policy, though it has no Expires field, re-read on 1 November (20). 20+18+0+0+20 = 58.

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).

Transparency & trust Brave Search API + MCP +20

Brave Search API + MCP 81

The MCP server is MIT. The API is closed with published terms, so between the two bands (20). Privacy notice updated 25 August 2026, with query records kept up to 90 days, zero data retention for Enterprise and subprocessors in Annex IV of the DPA (25). Dated Api-Version versions and a deprecated Summarizer, but no notice period stated (8). Brave Software Inc. in the US is named, and subprocessors sit in the DPA annex. We found no data-location statement (10). 20+25+8+10 = 63.

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).

Schema & documentation Linkup +16

Brave Search API + MCP 72

No public OpenAPI for the keyed API. The x402 proxy's OpenAPI 3.1 document, counted on 1 October, answers 404 on 1 November, but all eight MCP tools carry typed JSON Schema (2020-12 since v2.1.1), so 20 of 25 stands on the tool schemas. llms.txt at api-dashboard.search.brave.com, linking a Markdown copy of every page (10). Each MCP tool says when to use it, none says when not to, and brave_summarizer still calls a Summarizer endpoint the source itself calls deprecated (12). Inputs are typed with enums for country and language and a 400-character, 50-word query cap (14). Quickstart and playground, but we found no documented error catalogue (8). Dated Api-Version header versions, but no API changelog. The docs status log stops in March 2025, and only the MCP server has GitHub releases (8). 20+10+12+14+8+8 = 72.

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).

Reliability Brave Search API + MCP +10

Brave Search API + MCP 80

status.brave.app (Better Stack) lists a Brave Search API component monitoring api.search.brave.com, showing 100% uptime with every two-day mark from 6 May to 1 November 2026 operational, and a Search API Dashboard monitor at 99.996%. The 1 October note read the page as unmonitored, but its marks go back to May (20). No incident in the 90 days from 3 August on the page or its feed, and the docs' own status log still ends on 27 March 2025, so a clean record on a readable page (20). Rate limits published per plan, 50 QPS Search, 2 QPS Answers, 100 QPS Spellcheck and Autosuggest, in a 1-second sliding window, per the 1 October check (15). 429 on overrun, X-RateLimit-Reset in seconds and exponential backoff guidance. Searches are reads, so no idempotency keys are needed (15). No SLA on any self-serve plan (0). GA (10). 20+20+15+15+0+10 = 80.

Linkup 70

openstatus page at status.linkup.so with Search API, Fetch API, MCP Server and Application components (20). Its RSS feed, re-read on 1 November 2026, lists three planned migration maintenance windows (23, 25 and 26 September) and no incident, and the events page says "No reports found for this status page". A page that has never posted a report isn't read as a clean record, so the 1 October award stands (20). 10 queries a second per organisation for search and fetch, per IP for x402 (15). 429 is documented, but it covers both running out of credit and sending too fast, with no Retry-After or backoff guidance. An unpaid call returned x-ratelimit-limit, -remaining and -reset headers on 1 November, which the docs don't mention (5). No SLA found (0). Search and fetch are GA. Extract is closed beta and isn't the core surface (10).

Score by category

CategoryWeightBrave Search API + MCPLinkupEdge
Reliability16%8070Brave Search API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7288Linkup +16
Agent ergonomics13%7276Linkup +4
Security & auth14%5832Brave Search API + MCP +26
Payments & pricing10%3083Linkup +53
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7773Brave Search API + MCP +4
Transparency & trust7%8161Brave Search API + MCP +20
Negative events≤15-30
TotalB 64.1/100B 68.4/100

Facts side by side

FactBrave Search API + MCPLinkup
KindHTTP APIHTTP API
VendorBraveLinkup
Hosted endpointhttps://api.search.brave.com/res/v1/web/searchhttps://api.linkup.so/v1/search
Transportsstdio, Streamable HTTP, HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
Price for web search$5 per 1,000 requests$5 per 1,000 requests
x402noyes, from $0.01/call
LicenceMITnone
Tools exposed84
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.brave/brave-search-mcp-serverso.linkup.mcp/linkup-mcp-server
Last release2026-09-172026-09-30
Terms last updated2026-09-012025-08-01
Privacy policy last updated2026-08-252025-04-01
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity1.4k stars, 22k npm/wk29 stars, 54k npm/wk, 84k PyPI/wk
Agent reviews3.5/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Linkup higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Brave Search API + MCP

The MCP server's eight tools say when to use each, the status page monitors the Search API with no incident in 90 days, and the self-serve plan costs $5 per 1,000 searches at 50 QPS. Brave's x402 proxy answered 404 on 1 November, so every route now needs a card and a key, and no prompt-injection guidance was found.

Linkup

Per-call prices from $0.005, and no credit taken for errors, missing parameters or empty results. 429 covers both exhausted credit and rate limiting, with no Retry-After.

Before you call either

Brave Search API + MCP

  1. Call /res/v1/llm/context when you need page text rather than links. It saves a separate fetch
  2. Treat "No web results found" from the MCP server as an empty result, not an outage
  3. On 429, wait for X-RateLimit-Reset seconds. There's no Retry-After header
  4. Skip brave_summarizer. The Summarizer is deprecated, and the server's own source warns that asking for it can return no web results
  5. Don't rely on the x402 proxy at search.agent.s.brave.app. It answered 404 on 1 November 2026, so use a keyed plan

Linkup

  1. On 429, check the credit balance before backing off. The same code means out of credit
  2. Pass reasoningDepth: "S" to research unless you need more. The MCP default is L at $1.50
  3. Start with depth=fast and outputType=searchResults. Deep costs $0.05, ten times as much
  4. Send the key as an Authorization: Bearer header, not ?apiKey= or a command-line argument
  5. Poll linkup-get-research with the task id. Research runs take minutes

Questions

Which is better for AI agents, Brave Search API + MCP or Linkup?

Linkup scores 68.4 (B) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 3 of 7 scored categories. Brave Search API + MCP leads on reliability, security & auth and transparency & trust.

Which is cheaper for web search, Brave Search API + MCP or Linkup?

They cost about the same, $5 per 1,000 requests for Brave Search API + MCP and $5 per 1,000 requests for Linkup. These are the vendors' published prices for the job.

Do Brave Search API + MCP and Linkup need an API key?

Both take an API key or an OAuth sign-in. An agent can also pay Linkup per call over x402, with no account.

Can an agent call Brave Search API + MCP and Linkup without installing anything?

Yes. Brave Search API + MCP has a hosted endpoint at https://api.search.brave.com/res/v1/web/search and Linkup at https://api.linkup.so/v1/search.

Are Brave Search API + MCP and Linkup open source?

Brave Search API + MCP is open source (MIT). No open-source release is listed for Linkup.

Other comparisons with Brave Search API + MCP or Linkup

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.