Is Brave Search API agent-ready?

Brave Search API scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is MCP and agent posture; its weakest is webhooks and events.

Does Brave Search API publish an OpenAPI spec?

No published OpenAPI specification was found when Brave Search API was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is Brave Search API's Headless Index score?

Brave Search API scores 62/100 on the Headless Index thesis-fit rubric and sits in Band B in the Search & Vector DBs category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Search & Vector DBs

Brave Search API

Headless Index

62/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Brave Search API earns Band B in the Search & Vector DBs category of The Headless Index, with a thesis-fit score of 62/100. Its strongest dimension is MCP and agent posture (20/20); its weakest scored dimension is webhooks and events (4/20). No public OpenAPI specification was found when Brave Search API was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Brave Search API is solidly built for programmatic consumption. The Headless Index thesis-fit score of 62/100 lands it in the upper-middle of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Brave Search API lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Brave Search has no product other than its API. Endpoints under api.search.brave.com cover web, image, video, news, suggest, spellcheck and summarizer (/res/v1/web/search, /res/v1/news/search, /res/v1/summarizer/search), authenticated with a single X-Subscription-Token header. An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Search itself is entirely programmatic, which is the point, but everything around it is not. Subscription selection, plan upgrades and key issuance happen only in the browser (api-dashboard.search.brave.com); there is no key provisioning API, no Terraform provider and no CLI. An agent can query Brave all day, and cannot obtain the credential it needs to start.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: One of the most deployed MCP servers anywhere, and it is vendor-owned (github.com/brave/brave-search-mcp-server), carrying roughly 1,390 stars with commits into August 2026, shipping on npm, and exposing the search endpoints as tools directly. Brave got here early and kept maintaining it. For an agent this is the path of least resistance into web search, ahead of the raw REST API.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. There are no events, and for a synchronous search API that is close to expected. Brave registers no callbacks, signs no payloads and publishes no event types. The only asynchronous signal a caller receives is rate limit accounting in response headers (X-RateLimit-Limit, X-RateLimit-Remaining), which tells an agent about quota and nothing about anything else. Net assessment: Brave Search API can be operated by agents for the majority of practical workflows. The closest thing to a gap is webhooks and events^[3], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent16/20

scored

Brave Search has no product other than its API. Endpoints under api.search.brave.com cover web, image, video, news, suggest, spellcheck and summarizer (/res/v1/web/search, /res/v1/news/search, /res/v1/summarizer/search), authenticated with a single X-Subscription-Token header. The omission is client libraries: the brave GitHub org publishes no official Python, Go or JavaScript SDK, so callers hand-roll HTTP against documented response shapes.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 34 probe paths
·GraphQL endpointDiscovered at https://brave.com/graphql, introspection disabled or scoped
−SDKs maintainedNone detected in vendor org

cite (1)

ai_review_browser.auth@2026-08-19

Headless operation12/20

scored

Search itself is entirely programmatic, which is the point, but everything around it is not. Subscription selection, plan upgrades and key issuance happen only in the browser (api-dashboard.search.brave.com); there is no key provisioning API, no Terraform provider and no CLI. An agent can query Brave all day, and cannot obtain the credential it needs to start.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture20/20

scored

One of the most deployed MCP servers anywhere, and it is vendor-owned (github.com/brave/brave-search-mcp-server), carrying roughly 1,390 stars with commits into August 2026, shipping on npm, and exposing the search endpoints as tools directly. Brave got here early and kept maintaining it. For an agent this is the path of least resistance into web search, ahead of the raw REST API.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/brave/brave-search-mcp-server (1390 stars, last commit 5 days ago)
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability10/20

scored

No machine-readable spec is served. The documentation describes response objects in prose tables (WebSearchApiResponse, Query, SearchResult), and api.search.brave.com returns 422 to an unauthenticated probe rather than anything descriptive. The nearest thing to a schema an agent can fetch is the TypeScript type definitions inside the MCP server repo, which is a workaround, not a contract.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 34 standard probe paths
·GraphQL introspectionGraphQL endpoint at https://brave.com/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events4/20

scored

There are no events, and for a synchronous search API that is close to expected. Brave registers no callbacks, signs no payloads and publishes no event types. The only asynchronous signal a caller receives is rate limit accounting in response headers (X-RateLimit-Limit, X-RateLimit-Remaining), which tells an agent about quota and nothing about anything else.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

ai_review_browser.pages_fetched@2026-08-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:B band: JAIRF=N/A HeadlessIndex=62

04 / Embed

Show Brave Search API's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Search & Vector DBs

WeaviateB

Headless Index 62/100

ParadeDBB

Headless Index 62/100

ChromaB

Headless Index 62/100

See full Search & Vector DBs ranking →

FAQ

Brave Search API and agent readiness

Is Brave Search API agent-ready?: Brave Search API scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is MCP and agent posture; its weakest is webhooks and events.
Does Brave Search API publish an OpenAPI spec?: No published OpenAPI specification was found when Brave Search API was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Brave Search API's Headless Index score?: Brave Search API scores 62/100 on the Headless Index thesis-fit rubric and sits in Band B in the Search & Vector DBs category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.