# How to connect Railway to ChatGPT

> Set up Railway for ChatGPT with Agent200, then check which tools are available to your agent.

- Page: https://www.agent200.com/connectors/railway/framework/chatgpt/
- Connector: [Railway](https://www.agent200.com/connectors/railway.md)
- Framework: ChatGPT
- Updated: 2026-11-18

## Instructions for AI agents

Goal: connect Railway to ChatGPT with Agent200.
Guide: https://www.agent200.com/connectors/railway/framework/chatgpt/

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 Railway 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. Give every request a stable id for the end user. Agent200 uses only that user's own connections.
5. Connect the user's Railway account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on Railway.
6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "railway" in the tools. The model decides when a Railway tool is needed; Agent200 executes the call.
7. Check it works with this request: "Ask ChatGPT to list the Agent200 tools available for Railway, including which are read-only."
   What should come back:
   - A list of the Railway tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.
8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Railway, then retry.

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

## Overview

This guide connects Railway to ChatGPT through Agent200. When you finish, ChatGPT can call the Railway tools for each of your users.

Every call runs with that user's own Railway connection: Agent200 runs the OAuth flow, stores and refreshes the tokens, and executes the call. You do not build or maintain a Railway integration.

- **Connector:** [Railway](https://www.agent200.com/connectors/railway/)
- **Works with:** ChatGPT · Your own agent code
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [7 tools](https://www.agent200.com/connectors/railway/framework/chatgpt/#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.
- **Railway enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Railway account.** They approve access once, on Railway's own page.
- **A model for your agent.** The examples use openai/gpt-5.6-sol, through the same Agent200 API key.

## Connect Railway to ChatGPT

### 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 Railway 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: 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 3: Let your user connect Railway

Each end user authorizes their own Railway account once, through managed OAuth. If the user has not connected yet, Agent200 returns an authorization link: show it to them, and they approve access on Railway's own page. Agent200 handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Railway account, once.
const connection = await agent200
  .user("user_123")
  .connect("railway");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 4: Run with the Railway tools

Name the user, the model and Railway in the tools. The model decides when a Railway 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: "Why did the last deploy of my API fail",
    tools: ["railway"],
  });

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

(Conceptual example of the Agent200 SDK.)

## Test your connection

Ask: "Ask ChatGPT to list the Agent200 tools available for Railway, including which are read-only."

What should come back:

- A list of the Railway tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.

If no tools appear, check your Agent200 project access for Railway and make sure its tools are enabled. Tool availability depends on your project setup.

## Railway tools ChatGPT can call

- **List projects** (`railway_list_projects`, read): List the user's Railway projects.
- **List services** (`railway_list_services`, read): List the services in a project.
- **List deployments** (`railway_list_deployments`, read): List recent deployments of a service with their status.
- **Get deployment logs** (`railway_get_deployment_logs`, read): Read the build or runtime logs of a deployment.
- **Redeploy** (`railway_redeploy_deployment`, write): Redeploy an existing deployment.
- **Restart a deployment** (`railway_restart_deployment`, write): Restart a running deployment.
- **Set a variable** (`railway_upsert_variable`, write): Create or update an environment variable for a service.

## How it works

1. **Your app sends the request.** It calls Agent200 with the model, instructions, the input, the end user's id and the Railway tools.
2. **The model picks a tool.** The model decides whether a Railway tool is needed, and with which arguments.
3. **Agent200 runs the call.** It uses that user's own Railway connection, within the endpoints and scopes 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.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's Railway account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Railway enforces what its API grants.

## Troubleshooting

### Why not add Agent200 to ChatGPT as an MCP server?

ChatGPT’s custom MCP servers sign in with OAuth or with no sign-in, and cannot send an API key. Agent200’s MCP server uses your API key, so for ChatGPT users the SDK route on this page is the one that works.

### The request says Railway authorization is required

The end user has not connected Railway yet, or the connection needs to be approved again. Agent200 returns an authorization link: show it to the user, let them approve access on Railway's own page, then run the request again.

### ChatGPT does not use the Railway tools

Check that Railway is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming Railway 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 (services, endpoints and scopes), and Railway returns only what the end user authorized. Widen the endpoints or scopes in the dashboard if the agent needs more, then ask the user to connect Railway again so they can approve the new access.

### The results come from the wrong account

Every request names an end user (`user_123` in the examples). Pass the id of the person your agent is working for: Agent200 then uses only that user's Railway connection, never another user's.

### 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 Railway with another framework

- [Railway + Claude](https://www.agent200.com/connectors/railway/framework/claude.md)
- [Railway + Claude Code](https://www.agent200.com/connectors/railway/framework/claude-code.md)
- [Railway + Muse](https://www.agent200.com/connectors/railway/framework/muse.md)
- [Railway + Grok Bot](https://www.agent200.com/connectors/railway/framework/grok-bot.md)
- [Railway + OpenAI Dots](https://www.agent200.com/connectors/railway/framework/openai-dots.md)
- [Railway + Claude Duet](https://www.agent200.com/connectors/railway/framework/claude-duet.md)
- [Railway + Hermes Agent](https://www.agent200.com/connectors/railway/framework/hermes-agent.md)
- [Railway + OpenClaw](https://www.agent200.com/connectors/railway/framework/openclaw.md)

---

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