Tools

Brave Search

Web, image, video, news, and other Brave Search verticals
View as Markdown

Fronts the vertical endpoints of Brave Search, mounting them at /brave; the gateway supplies Brave’s /res/v1 base path itself:

GET /brave/<vertical>/search   → https://api.search.brave.com/res/v1/<vertical>/search

Only GET is mounted. Controls such as q, count, and country ride in the query string, which is relayed to Brave without modification.

Verticals

Exactly these verticals are admitted — anything else is refused with the gateway’s own 404 and never reaches Brave.

VerticalUpstream
web, images, videos, news, suggest, spellcheck, summarizerhttps://api.search.brave.com/res/v1/<vertical>/search

The AI “Answers” endpoints on Brave’s side (/chat/completions, /llm/context) are intentionally left unexposed.

Credential handling

  • X-Subscription-Token is injected; a client-supplied value is overwritten.
  • Authorization is dropped before the request goes upstream — your gateway token is meaningless to Brave.

Examples

$curl "$GATEWAY/brave/web/search?q=cloudflare+workers" \
>  -H "Authorization: Bearer $TOKEN"

Responses arrive as Brave’s JSON, untouched. Field-level request and response detail lives in Brave Search’s documentation; the gateway modifies neither.