# Build a X agent with Claude Code

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

- Page: https://www.agent200.com/tools/x/framework/claude-code/
- Connector: [X](https://www.agent200.com/tools/x.md)
- Framework: Claude Code
- Updated: 2026-11-15

## Instructions for AI agents

Goal: connect X to Claude Code with Agent200.
Guide: https://www.agent200.com/tools/x/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 X 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 "x" in the tools. The model decides when a X tool is needed; Agent200 executes the call.
5. Check it works with this request: "What are people posting about our launch today"
   What should come back:
   - An answer in `result.output`, built from X results.
   - Behind the scenes, the model calls a X tool, such as `x_search_posts`, 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/

## Overview

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

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

- **Connector:** [X](https://www.agent200.com/tools/x/)
- **Works with:** Claude Code · Coding agent, with the SDK
- **Authentication:** Your Agent200 API key
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [4 tools](https://www.agent200.com/tools/x/framework/claude-code/#tools)
- **Model in examples:** `openai/gpt-5.6-sol`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **X 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 X to Claude Code

### 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 X and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.

Create an API key: https://agent200.com/platform/apikeys/

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

### 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 X connection and the first request. Review the code it writes before you run it.

### Step 3: Set up the Agent200 SDK

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

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 4: Run with the X tools

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

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "What are people posting about our launch today",
    tools: ["x"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Test your connection

Ask: "What are people posting about our launch today"

What should come back:

- An answer in `result.output`, built from X results.
- Behind the scenes, the model calls a X tool, such as `x_search_posts`, and Agent200 runs it.

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

## X tools Claude Code can call

- **Search recent posts** (`x_search_posts`, read): Find posts from the last seven days that match a query.
- **Get a post** (`x_get_post`, read): Read a post with its author and engagement counts.
- **Get a user** (`x_get_user`, read): Look up an account by username: name, bio and follower counts.
- **List a user's posts** (`x_list_user_posts`, read): Read the most recent posts from an account.

## How it works

1. **Your app sends the request.** It calls Agent200 with the model, instructions, the input and the X tools.
2. **The model picks a tool.** The model decides whether a X tool is needed, and with which arguments.
3. **Agent200 runs the call.** It reaches X with your Agent200 API key, within the endpoints your project allows, and returns the result to the model.
4. **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 X tools

Check that X is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming X 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 X 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](https://agent200.com/platform/apikeys/), 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 X with another framework

- [X + Claude](https://www.agent200.com/tools/x/framework/claude.md)
- [X + ChatGPT](https://www.agent200.com/tools/x/framework/chatgpt.md)
- [X + Muse](https://www.agent200.com/tools/x/framework/muse.md)
- [X + Grok Bot](https://www.agent200.com/tools/x/framework/grok-bot.md)
- [X + OpenAI Dots](https://www.agent200.com/tools/x/framework/openai-dots.md)
- [X + Claude Duet](https://www.agent200.com/tools/x/framework/claude-duet.md)
- [X + Hermes Agent](https://www.agent200.com/tools/x/framework/hermes-agent.md)
- [X + OpenClaw](https://www.agent200.com/tools/x/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
