# Stripe for AI agents. Managed auth, ready-made tools.

> Look up Stripe customers, payments and invoices, and create invoices and payment links, on behalf of each of your users.

- Page: https://www.agent200.com/tools/stripe/
- Category: CRM and sales
- Authentication: Managed OAuth
- Identifier in code: `stripe`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

Connector: Stripe, through Agent200. In code: "stripe".
What it does: Look up Stripe customers, payments and invoices, and create invoices and payment links, on behalf of each of your users.
Page: https://www.agent200.com/tools/stripe/

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. Sign-in is managed OAuth. Each end user approves access once, on Stripe's own page, through the authorization link Agent200 returns. Never ask a user for a Stripe password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: stripe_search_customers, stripe_list_payments, stripe_get_balance, stripe_list_invoices, stripe_list_subscriptions. Write tools: stripe_create_customer, stripe_create_invoice, stripe_send_invoice, stripe_create_payment_link. Name "stripe" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/stripe/framework/claude/
   https://www.agent200.com/tools/stripe/framework/chatgpt/
   https://www.agent200.com/tools/stripe/framework/claude-code/
   https://www.agent200.com/tools/stripe/framework/muse/
   https://www.agent200.com/tools/stripe/framework/grok-bot/
   https://www.agent200.com/tools/stripe/framework/openai-dots/
   https://www.agent200.com/tools/stripe/framework/claude-duet/
   https://www.agent200.com/tools/stripe/framework/hermes-agent/
   https://www.agent200.com/tools/stripe/framework/openclaw/

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

## About

With the Stripe connector, your agent works with each user's Stripe account: it looks up customers, payments, invoices and subscriptions, checks the balance, and creates customers, invoices and payment links. Each user connects their own Stripe account through managed OAuth, and your agent stays within the permissions they approve and the operations your project allows.

Stripe is a payments platform that businesses use to accept payments, send invoices and run subscriptions.

## Stripe tools

- **Search customers** (`stripe_search_customers`, read): Find customers by email, name or metadata.
- **Create a customer** (`stripe_create_customer`, write): Add a customer with a name and email address.
- **List payments** (`stripe_list_payments`, read): List recent payments with their amount and status.
- **Get the balance** (`stripe_get_balance`, read): Read the account's available and pending balance.
- **List invoices** (`stripe_list_invoices`, read): List invoices by customer or status, such as open or paid.
- **Create an invoice** (`stripe_create_invoice`, write): Create a draft invoice for a customer.
- **Send an invoice** (`stripe_send_invoice`, write): Email a finalized invoice to the customer.
- **Create a payment link** (`stripe_create_payment_link`, write): Create a link where a customer can pay for a product.
- **List subscriptions** (`stripe_list_subscriptions`, read): List subscriptions by customer or status.

## Limits you can set

**Turn single tools on or off.** Keep the read tools on, and switch off `stripe_create_invoice` and `stripe_send_invoice` if your agent should only report on the account.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

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 2: Let your user connect Stripe

Each end user authorizes their own Stripe account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

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

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

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the Stripe tools

Name the user, the model and the tools. The model decides which Stripe tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "How much did we take in payments this week",
    tools: ["stripe"],
  });

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

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, on Stripe's own page, choosing the Stripe account to connect. You never see or store their Stripe password or secret keys.

**What access is requested.** The permissions listed on Stripe's consent screen, such as reading customers and payments or writing invoices.

## Example requests

- "How much did we take in payments this week"
- "Which invoices are past due"
- "Create an invoice for Acme for this month's retainer"
- "Make a payment link for the annual plan"

## Guides: Stripe with your AI framework

- [Stripe + Claude](https://www.agent200.com/tools/stripe/framework/claude.md): Connect Stripe to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Stripe + ChatGPT](https://www.agent200.com/tools/stripe/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Stripe into your own agent with OpenAI's models and the Agent200 SDK.
- [Stripe + Claude Code](https://www.agent200.com/tools/stripe/framework/claude-code.md): Have Claude Code build a Stripe agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Stripe + Muse](https://www.agent200.com/tools/stripe/framework/muse.md): Connect Stripe to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Stripe + Grok Bot](https://www.agent200.com/tools/stripe/framework/grok-bot.md): Connect Stripe to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Stripe + OpenAI Dots](https://www.agent200.com/tools/stripe/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Stripe agent with OpenAI's models and the Agent200 SDK.
- [Stripe + Claude Duet](https://www.agent200.com/tools/stripe/framework/claude-duet.md): Connect Stripe to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Stripe + Hermes Agent](https://www.agent200.com/tools/stripe/framework/hermes-agent.md): Connect Stripe to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Stripe + OpenClaw](https://www.agent200.com/tools/stripe/framework/openclaw.md): Connect Stripe to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### Who handles the Stripe OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Stripe.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Stripe connection, never another user's. It cannot reach anything the user or Stripe has not authorized.

### Can I limit what my agent can do in Stripe?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [HubSpot](https://www.agent200.com/tools/hubspot.md): Look up and update contacts, companies and deals in your users' HubSpot CRM.
- [Salesforce](https://www.agent200.com/tools/salesforce.md): Query and update accounts, contacts and opportunities in Salesforce.
- [LinkedIn](https://www.agent200.com/tools/linkedin.md): Share posts and read profile details on LinkedIn on behalf of each of your users, where the relevant API permissions are available.
- [Zendesk](https://www.agent200.com/tools/zendesk.md): Search, read, create and update Zendesk tickets, and reply to customers, on behalf of each of your users.

---

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