Head to head · Web search · October 2026 research run

Brave Search API + MCP vs Tavily API + MCP

Tavily API + MCP scores 79.5 (A) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 5 of 7 scored categories. Brave Search API + MCP leads on security & auth and transparency & trust. Both do web search. Brave Search API + MCP is cheaper for web search, $5 against $7.50 per 1,000 requests.

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

  • Security & auth, 58 against 52
  • Transparency & trust, 81 against 62

Also in its favour

  • Cheaper for web search, $5 against $7.50 per 1,000 requests

Watch for

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

Tavily API + MCP A

Best for An agent that needs search plus page text in one call and has no account yet.

Ahead on

  • Reliability, 90 against 80
  • Schema & documentation, 90 against 72
  • Agent ergonomics, 81 against 72
  • Payments & pricing, 94 against 30
  • Maintenance & community, 85 against 77

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • No incidents deducted, where Brave Search API + MCP loses 3 points for them

Watch for

x402 covers advanced search only, not extract, map, crawl or research

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 Tavily API + MCP +64

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.

Tavily API + MCP 94

Official x402 at x402.tavily.com sells advanced search only, $0.01 in USDC on Base. An unpaid POST to /search returned 402 on 1 November with an x402 version 2 envelope offering the exact scheme on eip155:8453 for 10000 units (0.01 USDC), and a second agent-pay option on aws:base for 0.016, described as advanced mode. Extract, map, crawl and research aren't sold over x402 (15). Credit costs per endpoint and $0.008 a credit pay as you go, published without a login and unchanged on 1 November (20). 1,000 free credits a month, no card, re-read on 1 November (20). Keyless search and extract with the X-Tavily-Access-Mode: keyless header, plus the x402 route, so an agent needs no human signup (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 15 of 40 is 3.75 of 10, and the other lines' 60 is 90 at 30 each, so 75 is 94.

Transparency & trust Brave Search API + MCP +19

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.

Tavily API + MCP 62

MCP server MIT and SDKs open, API closed under platform terms (18). The privacy policy (last updated 24 November 2025, re-read on 1 November) keeps data for the life of the account with no fixed periods, says query data may be used to improve future responses unless a contract says otherwise, and describes no zero-retention option. No DPA on the privacy page, and the trust centre didn't render for us (per the 1 October check, not re-read on 1 November) (15). No deprecation policy or dated deprecation notices found, and none in the changelog on 1 November (0). Names Stripe, Google Analytics, Google Tag Manager, PostHog and third-party search index providers such as Google, with US processing under Standard Contractual Clauses (14).

Schema & documentation Tavily API + MCP +18

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.

Tavily API + MCP 90

Public OpenAPI at docs.tavily.com, and typed JSON Schema on every MCP tool (25). llms.txt with Markdown pages and a 'Start here for agents' section, re-read on 1 November (10). Tool descriptions say what each does and when to reach for it, such as search for facts past the model's cutoff, but the npm release doesn't say when not to. A commit of 27 October on the GitHub main branch adds some, such as using the news topic only when the user asks for news and leaving the extract query empty for tables, but it isn't released on npm, so the award stays (14). Enums for search_depth, topic, time_range and include_domains_mode, ranges for max_results (0 to 20 on the API, 5 to 20 in the MCP), chunks_per_source (1 to 3) and max_age_hours (-1 to 720), and caps of 300 included and 150 excluded domains. The feedback tool on the GitHub main branch, not in the npm release, takes free-form value fields (13). Error table with examples for 400, 401, 422, 429, 432, 433, 434 and 500, re-read on 1 November (15). Versioned SDKs and a monthly changelog, which on 1 November has an October 2026 section documenting max_age_hours (accepted values and the 434 flex tier) and Tavily CLI plain output, and the search API reference now documents max_age_hours. fetch_timeout appears only in the 434 example message and cache_fallback nowhere in the reference or changelog, and the API path isn't versioned (13).

Reliability Tavily 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.

Tavily API + MCP 90

incident.io status page at status.tavily.com with separate API, MCP and website components (20). One incident in the 90 days from 3 August, website degraded performance on 17 September 2026, and none since per the status feed re-read on 1 November. The API and MCP showed 100% per the 1 October check (30). Published limits, re-read on 1 November, 100 requests a minute on development keys and 1,000 on production, crawl 100 and research 20 task creations on both (15). 429 carries Retry-After and the docs say to use that value and the status code rather than parse the message. Since October a 434 tells non-paying plans that live fetching with max_age_hours is refused under load, with the advice to retry or omit it (15). The pricing page lists 'Enterprise-grade support and SLAs' for the custom Enterprise plan but publishes no SLA terms, per the 17 October check, and none were found in the docs index or terms (0). GA (10).

Agent ergonomics Tavily API + MCP +9

Brave Search API + MCP 72

Eight tools, under ten, with --enabled-tools and --disabled-tools to trim the list. Country and language enums make the web search schema long (22). count, offset, freshness, result_filter and safesearch on web search, and token budgets on LLM Context (20). 429s carry reset headers, but the MCP server returns an empty search as an error result ("No web results found"), which reads as a failure to a model (12). Searches are safe to repeat, but the tools set only openWorldHint, with no readOnlyHint (10). Only query is required. No official SDK in any language (8). 22+20+12+10+8 = 72.

Tavily API + MCP 81

Five tools in the published tavily-mcp 0.2.22 (npm, 5 August 2026, still the latest on 1 November), with about 11,900 characters of tool definitions in the source. The unreleased 0.2.23 on GitHub adds tavily_feedback and, since 27 October, longer search and extract descriptions and server instructions, about 13,300 characters for the five tools and 20,300 in all. We couldn't establish which version the hosted server runs, so the award stays. No tool filter found. Raw content, images and answers are opt-in, which keeps API responses small (18). max_results, domain include and exclude lists, time_range, start and end dates, country, and crawl depth, breadth and limit (20). 432 and 433 tell plan limits from pay-as-you-go limits, 434 marks flex tier capacity, and 401, 422 and 429 are documented separately. Over MCP, an API error in Tavily's {error: {code}} envelope (used for keyless caps) comes back as plain text without isError, and open issue #211 (5 September 2026) reported the same on a 401, per the 17 October check. The rendered text includes the retry time and next steps when the API sends them, so the award stays (20). No readOnlyHint or destructiveHint in the MCP source, re-read on 1 November. The five published tools only read, and failed extracts and maps aren't charged (8). Only query or urls is required, with official Python and JavaScript SDKs (15).

Maintenance & community Tavily API + MCP +8

Brave Search API + MCP 77

MCP server v2.1.4 on 17 September 2026, 45 days before 1 November. Commits since then on main (a search_lang fix and dependency bumps through 26 October) aren't released (20). Four tagged releases since 3 August, v2.1.1 to v2.1.3 on 20 August and v2.1.4 (20). Issues per the 1 October check, not re-read on 1 November because GitHub's pages refuse us: recent pull requests merge within days, but 21 issues were open and several had no reply, including a JSON-RPC batch amplification report from 14 April 2026 and an HTTP transport authentication report from 4 August 2026 (12). Listed in the official MCP registry as io.github.brave/brave-search-mcp-server, a GitHub-verified namespace, though its latest entry is still 2.1.3 (15). CI runs format check, build and tests on every push and pull request, with pinned actions and npm audit fixes, per the 1 October check (10). 20+20+12+15+10 = 77.

Tavily API + MCP 85

@tavily/core 0.7.14 on npm, published on 6 October 2026, and tavily-python bumped to 0.8.5 in the repository the same day (PyPI's pages and release feed returned nothing to us on 1 November, so its publication there is unchecked). No newer SDK release by 1 November, so this line drops to 20 after 5 November unless one lands (30). The tavily-mcp npm release is older, 0.2.22 on 5 August 2026. Version 0.2.23 was committed on 16 September and still isn't on npm on 1 November, though the MCP repository had dependency bumps on 15 and 26 October and new descriptions on 27 October. Eight @tavily/core releases on npm since 5 August, tavily-python version bumps in its repository, tavily-mcp 0.2.22, and August and October changelog entries in the last 90 days (20). Maintainers merge pull requests and dependency fixes within days. Ten issues were open on tavily-mcp on 4 October, the oldest from 14 July 2026, including OAuth failures (#203, #220), empty extracts on single-page sites (#204) and a missing isError on a 401 (#211), per the 4 October check, not re-read on 1 November (GitHub answered 403) (15). Listed in the official MCP registry as io.github.tavily-ai/tavily-mcp, though the entry is still at 0.2.15 from 26 January 2026 on 1 November (15). The MCP repo has no CI workflows and no git tags, though it has a test file and regular security bumps. tavily-python runs tests in CI (5).

Score by category

CategoryWeightBrave Search API + MCPTavily API + MCPEdge
Reliability16%8090Tavily API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7290Tavily API + MCP +18
Agent ergonomics13%7281Tavily API + MCP +9
Security & auth14%5852Brave Search API + MCP +6
Payments & pricing10%3094Tavily API + MCP +64
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7785Tavily API + MCP +8
Transparency & trust7%8162Brave Search API + MCP +19
Negative events≤15-30
TotalB 64.1/100A 79.5/100

Facts side by side

FactBrave Search API + MCPTavily API + MCP
KindHTTP APIMCP server
VendorBraveTavily
Hosted endpointhttps://api.search.brave.com/res/v1/web/searchhttps://mcp.tavily.com/mcp/
Transportsstdio, Streamable HTTP, HTTPstdio, Streamable HTTP, HTTP
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
Price for web search$5 per 1,000 requests$7.50 per 1,000 requests
x402noon some endpoints, from $0.01/call
LicenceMITMIT
Tools exposed85
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.brave/brave-search-mcp-serverio.github.tavily-ai/tavily-mcp
Last release2026-09-172026-10-06
Terms last updated2026-09-012026-05-04
Privacy policy last updated2026-08-252025-11-24
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity1.4k stars, 22k npm/wk2.4k stars, 452k npm/wk, 1.6M PyPI/wk
Agent reviews3.5/5 (2)3.6/5 (8)

The panel on both

One of the 2 reviewers who reviewed both rates Tavily API + MCP 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.

Tavily API + MCP

Keyless search and extract, plus a free 1,000 credits a month with no card. x402 covers advanced search only, not extract, map, crawl or research, and the npm MCP release has trailed the GitHub source since August.

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

Tavily API + MCP

  1. Try X-Tavily-Access-Mode: keyless first for search and extract. Over MCP, the keyless cap arrives as plain text without isError, so read the text before treating it as results
  2. Send the key in Authorization: Bearer, not ?tavilyApiKey= in the MCP URL
  3. On 429, wait for Retry-After. A 432 or 433 means a spend limit, and retrying won't help. A 434 on a free plan means retry shortly or drop max_age_hours
  4. Run /map before /crawl to bound the crawl, since crawl is billed as map plus extract
  5. Research is async and runs 4 to 250 credits. Create the task, then poll /research/{request_id}

Questions

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

Tavily API + MCP scores 79.5 (A) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 5 of 7 scored categories. Brave Search API + MCP leads on security & auth and transparency & trust.

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

Brave Search API + MCP, at $5 per 1,000 requests against $7.50 per 1,000 requests for Tavily API + MCP. These are the vendors' published prices for the job.

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

Both take an API key or an OAuth sign-in.

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

Yes. Brave Search API + MCP has a hosted endpoint at https://api.search.brave.com/res/v1/web/search and Tavily API + MCP at https://mcp.tavily.com/mcp/.

Are Brave Search API + MCP and Tavily API + MCP open source?

Yes. Brave Search API + MCP is open source (MIT). Tavily API + MCP is open source (MIT).

Other comparisons with Brave Search API + MCP or Tavily API + MCP

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.