Head to head · Web search · October 2026 research run

Brave Search API + MCP vs Parallel Search and Task APIs

Parallel Search and Task APIs scores 75.7 (BB) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 4 of 7 scored categories. Brave Search API + MCP leads on reliability, security & auth and transparency & trust. Both do web search. Parallel Search and Task APIs is cheaper for web search, $1 against $5 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

  • Reliability, 80 against 75
  • Security & auth, 58 against 45
  • Transparency & trust, 81 against 65

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

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

Parallel Search and Task APIs BB

Best for Agents that mix quick search with long research or enrichment jobs and want one vendor and one bill.

Ahead on

  • Schema & documentation, 94 against 72
  • Agent ergonomics, 87 against 72
  • Payments & pricing, 81 against 30
  • Maintenance & community, 87 against 77

Also in its favour

  • Cheaper for web search, $1 against $5 per 1,000 requests
  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Brave Search API + MCP loses 3 points for them

Watch for

Search defaults to advanced mode at $5 per 1,000 when mode is left out

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 Parallel Search and Task APIs +51

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.

Parallel Search and Task APIs 81

Parallel runs a separate gateway at parallelmpp.dev that takes x402 (USDC on Base) and MPP (Stripe or Tempo) for search and extract at $0.01 and an ultra task at $0.30. Our unpaid POST to /api/search on 6 October returned 402 with an x402 v2 challenge for 10000 base units on eip155:8453 and a Tempo MPP challenge. Nothing on api.parallel.ai, and the gateway sells one price per endpoint with no mode choice, so partial (25). Per-unit prices published without login (20). Up to 5,000 free requests a month, $5 monthly credit and up to $80 at signup on the pricing page, which still doesn't say whether a card is needed (10). The hosted Search MCP works with no key, and the gateway needs only a wallet (20). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 25 of 40 is 6.25 of 10, and the other lines' 50 is 75 at 30 each, so 75 is 81.

Schema & documentation Parallel Search and Task APIs +22

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.

Parallel Search and Task APIs 94

Public OpenAPI at docs.parallel.ai/public-openapi.json, linked from llms.txt (25). llms.txt and Markdown pages (10). A live tools/list on search.parallel.ai/mcp on 17 October and again on 1 November returned the two definitions, and the newer Parallel MCP server at mcp.parallel.ai adds web_decisions, whose description says when to use web_search instead. web_search states its purpose and ideal uses, and web_fetch says to use it "only when web_search excerpts are insufficient". The docs add that domain filters are hard filters that can cut quality. web_search has no when-not-to line of its own (17). Typed JSON Schema inputs with required fields and an output schema on both tools, mode is an enum in the API, and Task output schemas are JSON Schema. The MCP inputs carry no enums (12). The errors page lists each code with whether to retry and what to do, and 422s carry a structured detail (15). A dated changelog, newest entry 26 October 2026 (Decisions API) after 19 October (EU data residency), and beta headers retire on dated entries (15).

Transparency & trust Brave Search API + MCP +16

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.

Parallel Search and Task APIs 65

The API is closed with published terms, and the SDKs are MIT (20). Privacy policy effective 11 August 2026 and Customer Terms effective 17 October 2026, both re-read on 1 November. EU-endpoint search requests keep no request or response content, but the default endpoint gets only "as long as necessary". The Customer Terms still let Parallel use Customer IP (inputs and outputs) to train and improve its models, not linked to an individual, and ask for a separate DPA before personal data is processed. No retention period is stated, and the DPA wasn't found as a public page (12). No deprecation notices or policy found in the changelog, which points older integrations from /v1beta to /v1 without an end date, and the docs now call the standalone Search and Task MCP servers legacy while saying both keep running, also without a date (5). EU data residency for basic-mode Search and Extract is documented, on enterprise agreements since 19 October. Subprocessors sit behind the trust centre and the privacy policy says to ask your Parallel contact (8).

Agent ergonomics Parallel Search and Task APIs +15

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.

Parallel Search and Task APIs 87

The Search MCP has two tools, about 5,700 characters of names, descriptions and input schemas on 1 November, and the Parallel MCP server lists three without a key (about 9,700 characters) and a fourth, web_research, after sign-in. web_fetch returns excerpts unless full_content is set, and the docs cap excerpts at roughly 25,000 characters a call and warn full pages can run to tens of thousands of tokens (25). Result counts, excerpt settings and source policies for domains and paths (18). The errors table gives each code a retry column and a resolution, with troubleshooting for 402 and 429 and a structured detail on 422 (20). Both Search MCP tools carry readOnlyHint true, destructiveHint false and idempotentHint true in the live tools/list, and searches are safe to repeat. There's still no idempotency key for Task creation, the SDKs retry creates on 429 and 5xx, and the Task MCP needs a key, so its annotations weren't read (14). Python and TypeScript SDKs, but mode defaults to advanced, the $5 per 1,000 tier, when you leave it out (10).

Security & auth Brave Search API + MCP +13

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.

Parallel Search and Task APIs 45

API key in x-api-key. The Search MCP takes a Bearer key or OAuth at /mcp-oauth. We found no key scopes (20). Every Search and Extract action is a read, and Task tools live in a separate MCP server, so the search server is a read-only subset (15). Excerpts and fetched pages are untrusted web text, and the docs index has no prompt-injection guidance (0). No audit log found (0). The privacy policy shows a SOC 2 badge and links trust.parallel.ai, which rendered only its title to our reader on 6 October. security.txt is 404 on parallel.ai and docs.parallel.ai, and no bug bounty found (10).

Maintenance & community Parallel Search and Task APIs +10

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.

Parallel Search and Task APIs 87

parallel-web 1.3.7 for Python on 2026-10-23 and for TypeScript on 2026-10-28, and changelog entries on 19 and 26 October, the second launching the Decisions API (30). Counted from the tags and the changelog, the 90 days from 3 August hold Python SDK releases 1.3.1 to 1.3.7, TypeScript 1.3.1 to 1.3.7 and ten changelog entries from 19 August to 26 October (20). The SDK releases since 1.3.5 are dependency bumps. Closed service with a changelog and support@parallel.ai. We didn't test whether support answers (12). Current Python and TypeScript SDKs, and ai.parallel/search-mcp and ai.parallel/task-mcp in the official registry (15). The Python SDK runs lint and build in CI on push, plus a workflow that detects breaking changes (10).

Score by category

CategoryWeightBrave Search API + MCPParallel Search and Task APIsEdge
Reliability16%8075Brave Search API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7294Parallel Search and Task APIs +22
Agent ergonomics13%7287Parallel Search and Task APIs +15
Security & auth14%5845Brave Search API + MCP +13
Payments & pricing10%3081Parallel Search and Task APIs +51
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7787Parallel Search and Task APIs +10
Transparency & trust7%8165Brave Search API + MCP +16
Negative events≤15-30
TotalB 64.1/100BB 75.7/100

Facts side by side

FactBrave Search API + MCPParallel Search and Task APIs
KindHTTP APIHTTP API
VendorBraveParallel Web Systems
Hosted endpointhttps://api.search.brave.com/res/v1/web/searchhttps://api.parallel.ai/v1/search
Transportsstdio, Streamable HTTP, HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
Price for web search$5 per 1,000 requests$1 per 1,000 requests
x402noon some endpoints, from $0.01/call
LicenceMITnone
Tools exposed86
Read-only variant documentednoyes
llms.txtyesyes
MCP registryio.github.brave/brave-search-mcp-serverai.parallel/search-mcp
Last release2026-09-172026-10-28
Terms last updated2026-09-012026-10-17
Privacy policy last updated2026-08-252026-08-11
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 textnot found in the text
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/wk28 stars, 250k npm/wk, 994k PyPI/wk
Agent reviews3.5/5 (2)3.6/5 (8)

The panel on both

One of the 2 reviewers who reviewed both rates Parallel Search and Task APIs 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.

Parallel Search and Task APIs

Fast-mode search at $1 per 1,000 with 10 excerpted results, and a keyless two-tool Search MCP annotated read-only. Search defaults to advanced mode at $5 per 1,000 when mode is left out, and the Customer Terms allow training on inputs and outputs.

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

Parallel Search and Task APIs

  1. Pass mode: "fast" on every API search. Without it you pay the advanced rate. On an authenticated MCP connection, pin it with ?mode=fast
  2. Create Task runs with max_retries=0 and check for an existing run before retrying
  3. Give an objective plus two or three short search_queries. That's what ranks the excerpts
  4. On 402, check available balance rather than total. Running tasks reserve credit
  5. Ask for zero data retention or use the EU endpoint before sending private queries. The default terms allow training on them
  6. On Decisions, check each answer's type before reading it. A refusal is a 200, not an error, and a predicate is a probability you threshold yourself

Questions

Which is better for AI agents, Brave Search API + MCP or Parallel Search and Task APIs?

Parallel Search and Task APIs scores 75.7 (BB) on agent readiness against Brave Search API + MCP's 64.1 (B), and leads in 4 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 Parallel Search and Task APIs?

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

Do Brave Search API + MCP and Parallel Search and Task APIs need an API key?

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

Can an agent call Brave Search API + MCP and Parallel Search and Task APIs without installing anything?

Yes. Brave Search API + MCP has a hosted endpoint at https://api.search.brave.com/res/v1/web/search and Parallel Search and Task APIs at https://api.parallel.ai/v1/search.

Are Brave Search API + MCP and Parallel Search and Task APIs open source?

Brave Search API + MCP is open source (MIT). No open-source release is listed for Parallel Search and Task APIs.

Other comparisons with Brave Search API + MCP or Parallel Search and Task APIs

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.