Brave Search Api

Fresh depth-11 runtime review passed for Brave Search search.query through Rhumb Resolve. Managed and direct executions matched on result count, top result fields, and top-3 URL ordering for the same live query.

Fresh depth-6 runtime rerun passed for Brave Search search.query through Rhumb Resolve. Managed and direct executions matched on result count, top title, and top URL for the same live query, lifting the public runtime-backed review stack from 5 to 6.

Fresh current-depth runtime rerun passed for Brave Search search.query through Rhumb Resolve. Managed and direct executions matched on result count, top title, and top URL for the same live query, lifting the public runtime-backed review stack another layer.

Fresh current-depth runtime rerun passed for Brave Search search.query through Rhumb Resolve. Managed and direct executions matched on result count, top title, and top URL for the same live query.

Fresh production rerun matched direct Brave Search control on result count, top title, and top URL for the same query through the managed execution rail.

A fresh production rerun through Rhumb Resolve matched direct Brave Search control on search.query for the same query, confirming the managed Brave path remains healthy after the earlier alias and param-mapping fixes.

Brave direct control was healthy, Rhumb-managed execution was healthy after the execution-layer fix, telemetry captured the live call, and the top search result matched the direct provider response.

The API is straightforward REST with query parameters for search type, count, offset, country, language, and freshness filtering. Results include standard fields: title, URL, description, and metadata. The web search endpoint is the primary surface, with news, images, and videos as additional verticals. For agents, the simplicity is a strength — there is no complex query language or configuration to learn.

Authentication uses a subscription token passed as a header. The model is simple and effective. There are no multi-tenant or permission complexities. Rate limits are tied to the subscription tier. For agents, the main consideration is managing rate limits across concurrent searches.

Error responses are structured and predictable. Missing parameters, invalid queries, and rate limit violations return clear HTTP status codes and error messages. The main reliability concern is result quality for niche or specialized queries where Brave's index may be thinner than Google's. Agents should be prepared for fewer results on long-tail queries.

Brave Search is notable because it operates its own independent search index rather than reselling Google or Bing results. For agents, this means a genuinely different perspective on web content, which can be valuable for research, fact-checking, and content discovery where diversity of sources matters. The API covers web results, news, images, and videos with a clean interface.

Documentation is clean and well-organized, with clear endpoint descriptions, parameter references, and response schemas. The API is simple enough that the docs are not large, which is actually a benefit for agents that need to learn the full surface quickly.