Tools

Brave Search

Brave Search verticals — web, images, videos, news, and more

View as Markdown

Proxies Brave Search’s verticals. The gateway exposes them under /brave, absorbing Brave’s /res/v1 base path:

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

GET only. Every control (q, count, country, …) travels in the query string and is forwarded byte-for-byte.

Verticals

The gateway accepts exactly this whitelist; any other vertical returns the gateway’s 404 without reaching Brave.

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

Brave’s AI “Answers” endpoints (/chat/completions, /llm/context) are deliberately not exposed.

What the gateway injects and strips

  • The X-Subscription-Token header is injected, overwriting any client-supplied one.
  • The Authorization header is stripped before forwarding — Brave has no use for your gateway token.

Examples

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

The response is Brave’s JSON, returned unchanged. For request and response fields, follow Brave Search’s documentation — the gateway does not alter them.