Can local recall disable adult-content filtering in Brave LLM Context?

Definition: No. In Brave LLM Context, local recall is location-aware retrieval controlled by enable_local; when local recall is active, the safesearch setting remains strict, so safesearch=off does not remove adult-content filtering for that request. Brave states this exception in its LLM Context documentation.

Key facts

• Brave lists off, moderate, and strict as the safesearch options in LLM Context, with local recall staying strict when the setting is not supplied.
• enable_local is null by default, can auto-detect local recall from location headers, and accepts true or false to force local or standard web ranking.
• Brave's LLM Context documentation says local queries can use location headers such as X-Loc-Lat, X-Loc-Long, X-Loc-City, and X-Loc-Country.
• In the Brave Web Search API reference, off means no filtering, moderate filters explicit images and videos while allowing adult domains, and strict drops all adult content from search results.
• The Web Search reference gives moderate as the default safesearch value for that endpoint.

How does the local recall exception work?

Local recall is Brave's location-aware retrieval mode for queries such as restaurants, businesses, and directions. In LLM Context, enable_local=true forces local recall, while enable_local=false forces standard web ranking even when location headers are present. When enable_local is left unset, the API enables local recall automatically when a location header is provided.

The safesearch setting is evaluated alongside that retrieval choice. The LLM Context parameter table says that the setting controls adult-content filtering and that an unset value means no filtering except when local recall stays strict. That sentence is the documented exception: local recall retains strict filtering even when a request asks for off.

Which request settings matter?

The request can combine a local switch, a SafeSearch value, and location context. Brave documents GET and POST forms for the LLM Context endpoint, with location context supplied through headers. A request can make the two relevant settings explicit:

curl -X GET "https://api.search.brave.com/res/v1/llm/context?q=restaurants+near+me&enable_local=true&safesearch=off" \
  -H "X-Subscription-Token: <YOUR_API_KEY>"

With those location headers and no explicit enable_local, the documented auto-detection path applies. Adding enable_local=true makes the choice explicit. Adding safesearch=off does not change the strict local-recall rule. To use the general off behavior described in the Web Search reference, the request must use standard web ranking with enable_local=false.

How does this differ from ordinary Web Search SafeSearch?

Brave's Web Search API reference describes off as no filtering. It describes moderate as filtering explicit content such as images and videos while allowing adult domains in results, and strict as dropping all adult content from search results. That endpoint lists moderate as its default.

LLM Context exposes the same three labels but documents a narrower result for local recall. The general meaning of off therefore does not override the LLM Context exception when location-aware retrieval is active. The distinction is between the SafeSearch option itself and the retrieval mode that applies it.

How can you check the setting in an integration?

Inspect the outgoing request for enable_local, safesearch, and any X-Loc- headers. A request with location headers and no enable_local relies on auto-detection. A request with enable_local=true forces local recall. A request with enable_local=false forces standard web ranking even if location headers remain present, which is the documented route for the general safesearch=off behavior.

Related terms

• When does Brave LLM Context switch to local place results?
• How can low-relevance chunks be filtered from Brave LLM Context?
• How does Brave LLM Context differ from ordinary web results?

FAQ

If you set safesearch=off, does local recall remove adult-content filtering?

No. The LLM Context documentation says local recall stays strict, so off does not disable that exception.

How do you keep local recall with strict filtering?

Set enable_local=true and use safesearch=strict. The request then states both the local retrieval choice and the strict filtering choice explicitly.

How do you use the general off behavior?

Set enable_local=false so the request uses standard web ranking. The Web Search reference defines off as no filtering for its general SafeSearch setting.

Sources

1. Brave Search API, "LLM Context: Web search for AI agents and chatbots", undated
2. Brave Search API, "Web Search", undated

---

Check how a page reads to answer engines. Open the GEO score analyzer