Stripe

CRM and sales

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.

About Stripe

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.

Tools

What your agent can do in Stripe.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Stripe connection.

  • Search customers

    Read
    stripe_search_customers

    Find customers by email, name or metadata.

  • Create a customer

    Write
    stripe_create_customer

    Add a customer with a name and email address.

  • List payments

    Read
    stripe_list_payments

    List recent payments with their amount and status.

  • Get the balance

    Read
    stripe_get_balance

    Read the account's available and pending balance.

  • List invoices

    Read
    stripe_list_invoices

    List invoices by customer or status, such as open or paid.

  • Create an invoice

    Write
    stripe_create_invoice

    Create a draft invoice for a customer.

  • Send an invoice

    Write
    stripe_send_invoice

    Email a finalized invoice to the customer.

  • Create a payment link

    Write
    stripe_create_payment_link

    Create a link where a customer can pay for a product.

  • List subscriptions

    Read
    stripe_list_subscriptions

    List subscriptions by customer or status.

Control

Limits you can set.

You decide what your agent may do in Stripe, and Agent200 runs every call within those limits.

  • 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

Connect Stripe
in three steps.

  1. 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.

    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,
    });
  2. 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.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // 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);
    }
  3. 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.

    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: "How much did we take in payments this week",
        tools: ["stripe"],
      });
    
    console.log(result.output);

Access

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.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Stripe connector and how to use it.

Agent brief
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/

This page is also available as Markdown, for agents and LLMs: /tools/stripe.md

Guides

Use Stripe with the AI you build on.

Step-by-step setup for Stripe with a specific model, assistant or agent framework.

FAQ

Stripe and Agent200, answered.

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.

  • HubSpot

    HubSpot

    Look up and update contacts, companies and deals in your users' HubSpot CRM.

    Managed OAuth CRM and sales
  • Salesforce

    Salesforce

    Query and update accounts, contacts and opportunities in Salesforce.

    Managed OAuth CRM and sales
  • LinkedIn

    LinkedIn

    Share posts and read profile details on LinkedIn on behalf of each of your users, where the relevant API permissions are available.

    Managed OAuth CRM and sales
  • Zendesk

    Zendesk

    Search, read, create and update Zendesk tickets, and reply to customers, on behalf of each of your users.

    Managed OAuth CRM and sales
200 OK

Start with Stripe.
Your agent does the rest.

Your users connect their own Stripe accounts. Agent200 handles the OAuth, the tokens and every tool call.

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)