Brave Search + Claude Code

Build a Brave Search agent with Claude Code

Have Claude Code build a Brave Search agent with the Agent200 SDK: no separate key, ready-made tools and one API key.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Brave Search tools
  7. How it works
  8. Troubleshooting

Overview

This guide has Claude Code build a Brave Search agent with the Agent200 SDK, in your own project. When you finish, your agent can call the Brave Search tools for each of your users.

Claude Code writes the code from the steps below; Agent200 runs the Brave Search calls with your Agent200 API key. You do not build or maintain a Brave Search integration.

Connector
Brave Search
Works with
Claude Code ยท Coding agent, with the SDK
Authentication
Your Agent200 API key
Tools
5 tools
Model in examples
openai/gpt-5.6-sol

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Brave Search enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • Claude Code in your project. It writes the code with the Agent200 SDK; you review it.

Connect Brave Search to Claude Code

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. Copy the key and store it as an environment variable, AGENT200_API_KEY, or in your secrets manager. One key covers Brave Search and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Give this guide to Claude Code

    Start Claude Code in your project and paste the agent brief from this page, or give it the address of this guide's Markdown version. Claude Code follows the steps below in order: the SDK, the Brave Search connection and the first request. Review the code it writes before you run it.

  3. 3

    Step 3: Set up the Agent200 SDK

    Add the SDK to your project and create a client with the key from the environment.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  4. 4

    Step 4: Run with the Brave Search tools

    Name the user, the model and Brave Search in the tools. The model decides when a Brave Search tool is needed, and Agent200 executes the call with the user's own connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "What are people saying about the new iPhone this week",
        tools: ["brave_search"],
      });
    
    console.log(result.output);

Test your connection

Run one request to check everything is wired up.

Ask

What are people saying about the new iPhone this week

What should come back

  • An answer in result.output, built from Brave Search results.
  • Behind the scenes, the model calls a Brave Search tool, such as brave_search_query_web, and Agent200 runs it.

If the tools are missing, check that Brave Search is enabled for your project in the dashboard.

Get your API key

Create a key in the Agent200 dashboard. It reaches Brave Search and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Brave Search to Claude Code.

Agent brief
Goal: connect Brave Search to Claude Code with Agent200.
Guide: https://www.agent200.com/tools/brave-search/framework/claude-code/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Make sure Brave Search is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "brave_search" in the tools. The model decides when a Brave Search tool is needed; Agent200 executes the call.
5. Check it works with this request: "What are people saying about the new iPhone this week"
   What should come back:
   - An answer in `result.output`, built from Brave Search results.
   - Behind the scenes, the model calls a Brave Search tool, such as `brave_search_query_web`, and Agent200 runs it.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

The whole guide is also available as Markdown, for agents and LLMs: /tools/brave-search/framework/claude-code.md

Brave Search tools Claude Code can call

  • Search the web

    Read
    brave_search_query_web

    Get ranked web results with titles, snippets and URLs.

  • Search news

    Read
    brave_search_query_news

    Find recent news articles, filtered by freshness.

  • Search images

    Read
    brave_search_query_images

    Find images that match a query.

  • Search videos

    Read
    brave_search_query_videos

    Find videos that match a query.

  • Suggest queries

    Read
    brave_search_get_suggestions

    Get autocomplete suggestions for a partial query.

How it works

  1. 01

    Your app sends the request

    It calls Agent200 with the model, instructions, the input and the Brave Search tools.

  2. 02

    The model picks a tool

    The model decides whether a Brave Search tool is needed, and with which arguments.

  3. 03

    Agent200 runs the call

    It reaches Brave Search with your Agent200 API key, within the endpoints your project allows, and returns the result to the model.

  4. 04

    Your app gets the result

    Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

Permissions at every level. Your project settings decide which services and endpoints the agent may use.

Troubleshooting

Claude Code does not use the Brave Search tools

Check that Brave Search is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming Brave Search in the request, or in the instructions, also helps the model choose the right tool.

A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that the Brave Search endpoints the agent needs are enabled in the dashboard's Connectors settings.

The API key was pasted into a chat or committed

Create a new key on the API keys page, update AGENT200_API_KEY wherever your app reads it, and stop using the old one. Keep keys in environment variables or a secrets manager, never in prompts, chats or source control.

Use Brave Search with another framework

200 OK

Brave Search, connected to Claude Code.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)