If you want to use the Brave Search inside app, script, AI tool, chatbot or automation project, you need a Brave API key. This key lets your project send requests to Brave Search API and get search results back.
A Brave API key is not something you get from normal Brave Browser settings. It comes from the Brave Search API dashboard. So if you are looking inside the browser menu and cannot find it, that is why.
This article is for beginners, developers, students, and AI tool builders who want to get a Brave API key and use it the right way. I’ll explain where to create the key, what you need before signup, how to test it and how to keep it safe.
What Is a Brave API Key?
A Brave API key is a private access key for the Brave Search API. You can think of it like a password for your app, but only for API requests. When your app sends a search request, the key proves that the request belongs to your API account.
This key is used for developer work. It is different from manually searching on Brave Search. If you open Brave Search and type a query, you do not need an API key. But if your app wants to fetch search results programmatically, you need one.
The Brave Search API can be used for web, news, image and video search, as well as for search-based tools. It is often used in AI agents, research tools, chatbots, internal search apps and automation workflows. Brave’s API documentation lists Web, News, Image and Video Search APIs as available search options.
Before You Get a Brave Search API Key
Before creating your key, you should have an email address ready for the Brave Search API account. You may also need to choose a plan in the API dashboard before the key can be used properly.
Pricing and credits can change, so always check the dashboard before starting a serious project. At the time of writing, the Brave Search API pricing page shows metered plans for Search and Answers, with monthly free credits applied to the account.
For a small test, you do not need a big setup. But for a real app, you should think about usage limits, request volume, billing, and how you will store the key. It is better to plan this early instead of fixing it after the key gets exposed.
How to Get a Brave API Key Step by Step
The basic process is simple. You create a Brave Search API account, open the dashboard, choose the plan that fits your use case, then create or copy your API key.
Start from the Brave Search API page or API dashboard. This is where the API account is managed. The login page is separate from normal browser use and the registration page is made for creating a new Search API account.
Here is the simple flow:
- Go to the Brave Search API page.
- Sign up or log in to the API dashboard.
- Choose a Search API plan if the dashboard prompts you to do so.
- Open the API key section in your dashboard.
- Generate a new API key.
- Copy the key and save it somewhere safe.
- Use the key in your API request header.
The dashboard design may change over time, so do not worry if the button names look slightly different. The idea stays the same. You need an API account, an active plan or credits and an API key generated from the dashboard.
Brave API Key Is Not in Brave Browser Settings
This is a common confusion. Brave Browser and Brave Search API are related to Brave, but they are not the same thing.
Brave Browser is the app you use to browse the web. Brave Search is the search engine you can use like Google or Bing. Brave Search API is for developers who want to use Brave Search results inside code.
So if you are trying to find the API key in browser settings, bookmarks, search settings, or Brave Rewards, you will not find it there. The key is created inside the Brave Search API dashboard, not inside the normal browser.
How to Use the Brave API Key
After you copy your Brave API key, you use it in API requests. Brave Search API uses a request header called X-Subscription-Token. Your key goes inside that header.
This is important because many users put the key in the wrong place. Do not put it as a normal query keyword. Do not paste it into the search box. It belongs in the request header when your code calls the API.
A simple curl example looks like this:
curl -s “https://api.search.brave.com/res/v1/web/search?q=test” \
-H “Accept: application/json” \
-H “X-Subscription-Token: YOUR_API_KEY“
In that example, replace YOUR_API_KEY with the real key from your dashboard. The Brave API authentication guide uses the X-Subscription-Token header for requests, and the quickstart also explains that API requests require the key in that header.
How to Store Your Brave API Key Safely
Do not paste your Brave API key directly into public code. If you upload that code to GitHub or share a screenshot, someone else may use your key. That can affect your usage, billing, or account limits.
A better way is to store the key in an environment variable. For example, you can keep it as BRAVE_API_KEY on your computer or server, then let your app read it from there.
For backend projects, you can also use a.env file, but do not upload that file publicly. Add.env to your.gitignore file if you are using Git.
Avoid putting the key inside front-end JavaScript, public HTML, mobile app source files, or browser code that users can inspect. API keys are safer on the server side.
Common Problems When Getting or Using a Brave API Key
Sometimes the API key is created but the request still does not work. Usually the problem is not huge. It may be a wrong header name, missing query, no active plan, or a copied key with extra spaces.
| Problem | Possible Fix |
|---|---|
| Key not showing | Finish account setup and check the API dashboard |
| 401 error | Check your API key and X-Subscription-Token header |
| 422 error | Check required query parameters like q |
| No response | Check endpoint URL, internet and request format |
| Rate limit error | Check plan usage, limits and request volume |
| Key exposed | Delete or rotate the key and create a new one |
If you get a 401 error, check the token first. Make sure the header name is written exactly as X-Subscription-Token. If you get a 422 error, check the request parameters. For web search, your request usually needs a query like q=test.
Also check if your plan or credits are active. A key may exist, but the API may not work the way you expect if your account setup is incomplete.
What Can You Use Brave Search API For?
Brave Search API is useful when your project needs search results from the web. You can use it in a normal search app, AI chatbot, research assistant, browser extension, content tool or internal company tool.
Common use cases include:
- Building a web search feature
- Adding search results to an AI agent
- Finding fresh sources for a chatbot
- Creating a research tool
- Searching news results in an app
- Getting image or video search results
- Making automation tools that need web results
For AI projects, the API can be useful because many AI tools need current web results. A chatbot without search may only know what is already in its model or database. A search API can help it fetch newer or more specific information.
Should You Use Brave API for AI Projects?
Brave API can be a good option if your AI project needs web search results, news results, or search context. It can be used in chatbots, agents, research apps and tools that need live search data.
But you still need to handle the results properly. An API key only gives access to the data. Your app still needs to choose what to show, how to summarize it, and how to handle errors or empty results.
Also watch your usage. AI tools can make many requests quickly, especially if users ask long questions or your agent searches multiple times. For small tests, that may not matter much. For a real product, usage limits and cost matter.
Final Thoughts
Getting a Brave API key is simple once you know where to go. You need to create a Brave Search API account, open the dashboard, choose a plan if required, generate the key, and use it in requests with the X-Subscription-Token header.
The most important thing after getting the key is keeping it safe. Do not paste it into public code or screenshots. Store it in an environment variable and use it from your backend when possible.
What are you planning to build with the Brave API: a chatbot, AI agent, search tool, or a small test script?