CRM and sales
Whop for AI agents.
Managed auth, ready-made tools.
List products, memberships and payments and create promo codes in Whop on behalf of each of your users.
About Whop
With the Whop connector, your agent works with each user’s own Whop business. It can list products, list and read memberships, list payments and create a promo code, using only the tools your project allows.
Whop is a platform for selling digital products, memberships and communities online.
Tools
What your agent can do in Whop.
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 Whop connection.
-
List products
Readwhop_list_productsList the products the business sells.
-
List memberships
Readwhop_list_membershipsList memberships and their status.
-
Get a membership
Readwhop_get_membershipRead a membership's details.
-
List payments
Readwhop_list_paymentsList payments and their status.
-
Create a promo code
Writewhop_create_promo_codeCreate a discount code for a product.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Whop, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read memberships and payments, and switch off
whop_create_promo_codeso it can never create a discount. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example memberships but not payments. A call outside them is refused.
Get started
Connect Whop
in three steps.
-
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.jsConceptual exampleSet 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
Let your user connect Whop
Each end user authorizes their own Whop account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Whop account, once. const connection = await agent200 .user("user_123") .connect("whop"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Whop tools
Name the user, the model and the tools. The model decides which Whop tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "How many active memberships do I have on Whop", tools: ["whop"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Whop's own sign-in page. You never see or store their Whop password.
-
What access is requested
The scopes the connection needs, such as reading memberships, reading payments or managing promo codes, listed on Whop's authorization screen. Users can remove the app later from their Whop account settings.
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 Whop connector and how to use it.
Connector: Whop, through Agent200. In code: "whop". What it does: List products, memberships and payments and create promo codes in Whop on behalf of each of your users. Page: https://www.agent200.com/connectors/whop/ 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 Whop's own page, through the authorization link Agent200 returns. Never ask a user for a Whop 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: whop_list_products, whop_list_memberships, whop_get_membership, whop_list_payments. Write tools: whop_create_promo_code. Name "whop" 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/connectors/whop/framework/claude/ https://www.agent200.com/connectors/whop/framework/chatgpt/ https://www.agent200.com/connectors/whop/framework/claude-code/ https://www.agent200.com/connectors/whop/framework/muse/ https://www.agent200.com/connectors/whop/framework/grok-bot/ https://www.agent200.com/connectors/whop/framework/openai-dots/ https://www.agent200.com/connectors/whop/framework/claude-duet/ https://www.agent200.com/connectors/whop/framework/hermes-agent/ https://www.agent200.com/connectors/whop/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: /connectors/whop.md
Guides
Use Whop with the AI you build on.
Step-by-step setup for Whop with a specific model, assistant or agent framework.
-
Whop + Claude
How to connect Whop to Claude
-
Whop + ChatGPT
How to connect Whop to ChatGPT
-
Whop + Claude Code
How to connect Whop to Claude Code
-
Whop + Muse
How to connect Whop to Muse
-
Whop + Grok Bot
How to connect Whop to Grok Bot
-
Whop + OpenAI Dots
How to connect Whop to OpenAI Dots
-
Whop + Claude Duet
How to connect Whop to Claude Duet
-
Whop + Hermes Agent
How to connect Whop to Hermes Agent
-
Whop + OpenClaw
How to connect Whop to OpenClaw
FAQ
Whop and Agent200, answered.
Who handles the Whop 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 Whop.
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 Whop connection, never another user's. It cannot reach anything the user or Whop has not authorized.
Can I limit what my agent can do in Whop?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.