The New York Times sues Brave over allegations that Brave copied publisher content, bypassed paywalls and sold access to its search index for AI use on November 2, 2026, according to The Verge.
The Verge reported that The New York Times filed one lawsuit, while the New York Daily News, the Chicago Tribune and the Orlando Sentinel filed another against Brave Software on the same date. The complaints allege that Brave monetized scraped publisher content through Brave Index access and supplied content to AI companies including Anthropic, Perplexity, Mistral, xAI and Cohere. Brave did not immediately reply to The Verge's request for comment.
Why the New York Times sues Brave
The publishers say Brave copied journalism without permission, enabled paywall bypassing and sold content access to AI companies. The Verge quoted Graham James, a New York Times spokesperson, saying, "While we believe in the ethical and responsible use and development of AI, Brave has flouted established copyright law and ignored repeated requests by The Times to stop its infringing conduct." Search Engine Journal reported that the Times complaint also alleges Brave ignored cease-and-desist letters sent in August 2025 and April 2026.
The second complaint, filed by the New York Daily News, the Chicago Tribune and the Orlando Sentinel, says Brave provided paid access to "real-time online content from the Brave Index," according to The Verge. Steven Lieberman, the attorney who filed that lawsuit, told The Verge, "AI giants are now desperate to avoid getting caught red-handed stealing news from publishers, so Brave Software is selling them a back door to the journalism they know they have no right to." Perplexity disputed the premise in a statement from chief communications officer Jesse Dwyer, who told The Verge, "The New York Times is overpaying its attorneys and underpaying its journalists. (Who could've easily identified the disinformation in this suit.)"
The case is about distribution, not only crawling. The complaints allege that Brave copied publisher pages into an index, converted that material into products such as API access and AI answers, and then let customers use the content for model training, user-query responses, or both.
How Brave's AI content pipeline works
Brave's own product pages describe the pipeline as an independent search index feeding API products for search and AI systems. Brave's Search API page says every result comes from Brave's own index, with no Google or Bing fallback. The same Brave page says its LLM Context API returns pre-extracted, relevance-scored content chunks, including text, tables and code, for machine consumption.
| Product or claim | What the evidence says | What remains unresolved |
|---|---|---|
| Brave Search API | Brave says the API gives customers access to Brave's independent index and lists Search pricing at $5 per 1,000 requests. | The evidence does not show which customers accessed which publisher pages. |
| LLM Context API | Brave says it extracts and scores page content chunks for machine use, and its February 24, 2026 post says the workflow converts raw HTML into chunks. | The record here does not show how Brave treats paywalled HTML in every publisher case. |
| Training and storage rights | Brave's FAQ says customers can store results or use them to train models if their plan includes storage rights. | The evidence does not identify the exact plans used by Anthropic, Perplexity, Mistral, xAI or Cohere. |
| Ask Brave | Brave said on February 24, 2026 that the LLM Context API powered Ask Brave and more than 22 million answers per day. | The evidence does not quantify publisher traffic loss from those answers. |
Brave's February 24, 2026 announcement gives the technical sequence that matters for search teams. Brave said the system uses standard web search on its independent index to identify relevant pages, then digs into each page's content in real time and converts raw HTML into chunks. That description explains why a publisher can see the same content appear in search retrieval, retrieval-augmented generation pipelines and answer products even when the user never visits the source page.
Where the evidence conflicts
The public record conflicts on crawler identity, index size and whether Brave is a scraper. The r/browsers discussion on November 2, 2026 repeated the allegation that Brave used an unidentified crawler and left publishers unable to block it, but that subreddit thread had seven comments and is useful only as practitioner signal. Brave's own AI page says Brave is "not a scraper or aggregator," while the lawsuits described by The Verge and Search Engine Journal allege unauthorized scraping and copying.
Brave's own pages also use different index-size figures. One Brave AI page says Brave Search has more than 30 billion pages, the same page also lists more than 35 billion pages as a differentiator, and Brave's February 24, 2026 Search API growth post says the index had 40 billion web pages. The difference may be timing, wording or product-page maintenance, but the evidence does not resolve it. Search teams should treat the exact count as unsettled and the API architecture as the more material fact.
The strongest confirmed fact is that Brave sells API access to an independent web index and describes AI uses for that access. The disputed fact is whether Brave obtained and distributed publisher content unlawfully, especially paywalled content, and that question now sits with the lawsuits filed on November 2, 2026.
What publishers should check now
Publishers should preserve evidence before changing access controls, because the complaints turn on copying, paywall access and downstream API use. Keep raw server logs, CDN logs, WAF events and paywall entitlement logs for the August 2025 and April 2026 warning window reported by Search Engine Journal, plus the November 2, 2026 filing date. Do not rely on analytics suites alone, because API retrieval and answer generation may not create a normal pageview or referral session.
Review robots.txt, paywall metering rules and subscriber-only route handling, but document the pre-change state first. The complaints allege that Brave prevented publishers from blocking access, so a missing or ignored robots directive could become part of an evidentiary question rather than a simple SEO setting. If your team can reproduce publisher excerpts in Brave Search, Ask Brave or Brave API outputs, save the query, timestamp, returned text, page URL, access status and whether the article was behind a paywall.
Content licensing teams should also read customer storage terms with the same care as crawler rules. Brave's Search API FAQ says customers can store results or use results to train models when their plan includes storage rights. That language matters for publishers negotiating AI licenses, because a search API contract can become a second path into content that the publisher thought it controlled through direct licensing, paywalls or technical blocks.
What it means for search visibility
The immediate search impact is not a Google ranking change. The stronger inference is distribution risk: Brave's index and LLM Context API can feed chatbots, RAG pipelines, model training workflows and MCP use cases, according to Brave's own pages. If publisher content is converted into answer-ready chunks, the content can create value for AI answers without producing a visit that appears in Google Search Console or standard referral analytics.
For paid media and revenue teams, the relevant allegation is ad substitution and paywall bypass, not only scraping. Search Engine Journal reported that the Times complaint accuses Brave of removing Times advertising and substituting its own, while The Verge reported that Brave promoted publishers as accessible through a Paywall blocker feature. If proved, that would connect browser behavior, search indexing and monetization in one chain: the same content could be read without a subscription, stripped of publisher ads and resold as machine-readable input.
The next trigger is Brave's formal response to the November 2, 2026 lawsuits or any court order on injunctive relief. Until then, the reliable facts are the filings reported by The Verge, Brave's own API documentation and the unresolved conflict between Brave's "not a scraper or aggregator" claim and the publishers' copyright allegations.