Can Brave Answers use a response language different from its search country?

The Citead team, updated

In short. Brave Answers documents country for search results and language for the response as separate request fields.

Definition: Yes, at the request level. Brave Answers documents country as the target country for search results and language as the response language, so the two settings are supplied as separate fields.

Key facts

  • Brave's Answers documentation says additional OpenAI SDK parameters are passed through extra_body.
  • The same page defines country as the target country for search results and gives us as its default.
  • It defines language as the response language and gives en as its default.
  • Brave's Web Search API reference uses a separate search_lang field for the language in which search results are provided.
  • The Web Search reference describes ui_lang as the preferred user interface language in the response, usually in a language-country format.

How are the two Answers settings separated?

Brave's Answers page places both settings in the request body passed through extra_body. Its example uses country with the value IT and language with the value it, alongside the citation and research controls:

extra_body={
    "country": "IT",
    "language": "it",
    "enable_citations": True,
    "enable_research": False,
}

The parameter list gives each field a different job. country is the target country for search results, while language is the response language. That separation means a request can specify a search country and a different response language in their respective fields. Brave's page does not show a mismatched pair as a worked response, so this conclusion concerns the documented request controls.

What does country control?

In the Answers documentation, country targets the country for search results and defaults to us. The page demonstrates the value IT in its advanced-parameter example. The country setting therefore belongs to the web-search side of the Answers request, while the answer's language belongs to the separate language field.

The Answers service uses the endpoint below:

https://api.search.brave.com/res/v1/chat/completions

The documentation describes this service as an API for answers backed by real-time web search and verifiable sources. A country value is consequently a search-targeting input, not a declaration of the language in which the returned answer must be written.

How does this differ from Web Search API naming?

Brave's Web Search reference defines country as the two-character country code where search results come from. Its search_lang parameter is the two or more character language code for which search results are provided. It also lists ui_lang, whose purpose is the preferred interface language in the response, usually written as a language code followed by a country code.

These names matter when one application uses both services. In an Answers request, use the documented language field for the response language. In a Web Search request, search_lang describes result language and ui_lang describes interface language. The Web Search reference lists US, en, and en-US as the respective defaults for country, search_lang, and ui_lang.

FAQ

Can I place IT and en in the same Answers request?

Yes. The Answers documentation presents country and language as separate fields, so IT can be supplied for the search country and en for the response language at request level.

Is Answers language the same as Web Search search_lang?

No. Brave labels the Answers field as the response language. In the Web Search reference, search_lang is the language for which search results are provided.

What happens when I omit both fields?

The Answers documentation lists us as the country default and en as the language default.

Sources

  1. Brave, "Answers", undated
  2. Brave, "Web Search: Search", undated

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

Test a page and see what to fix first

The analysis usually takes less than 10 seconds and needs no account.

400,000+ pages scored in the public benchmark