Whop API

Name: Whop API
Brand: Whop API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment Processingbearer13 EndpointsREST

For Agents

Programmatically get user profile, list payments. Covers 13 operations with bearer authentication.

Install Jentic One Beta

Connect the Whop API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Whop API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fwhop.com%2Fwhop" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fwhop.com%2Fwhop" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Whop API.

Get user profile

List payments

Integrate Whop API into automated workflows

Query and filter Whop API records by parameters

GET STARTED

Start building with Whop API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Whop API for, with concrete tasks.

★ Payments Operations

Use the Whop API to perform payments operations programmatically. The API provides 13 endpoints covering core functionality including get user profile, list payments, list memberships.

Call GET /users/{username} to get user profile

Automated Experiences Management

Automate experiences operations by combining multiple Whop API endpoints. Agents can list payments and then list memberships in a single workflow.

Call GET /payments to list payments, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Whop API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'get user profile', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

13 endpoints — whop digital commerce platform api for managing users, memberships, products, and payments.

METHOD

PATH

DESCRIPTION

GET

/users/{username}

Get user profile

GET

/payments

List payments

GET

/memberships

List memberships

GET

/memberships/{id}

Get membership

GET

/products

List products

GET

/products/{id}

Get product

GET

/plans

List plans

GET

/plans/{id}

Get plan

GET

/users/{username}

Get user profile

GET

/payments

List payments

GET

/memberships

List memberships

GET

/memberships/{id}

Get membership

GET

/products

List products

GET

/products/{id}

Get product

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Whop API by hand means learning its bearer auth, targeting api.whop.com, and paging through payments, memberships, and products yourself. Through Jentic you install once, import the Whop API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Whop puts the resource id in the URL path (/memberships/{id}, /products/{id}), so a rule can pin your agent to reading one membership or product and nothing else. You choose the operations it may call, so the endpoints outside that set are not included unless you add them.

Credential isolation

Your Whop token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'look up a user profile' or 'list active memberships', and Jentic returns the matching Whop operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Whop API through Jentic.

What authentication does the Whop API use?

The Whop API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I get user profile with the Whop API?

Yes. Use the GET /users/{username} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Whop API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get user profile through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get user profile'. Jentic returns the matching Whop API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Whop API have?

The Whop API exposes 13 endpoints covering experiences, memberships, payments operations.

Can I limit what my agent is allowed to do with the Whop API?

Yes. Because you run Jentic One yourself, your own rules decide which Whop operations and credentials the agent may use. Whop puts the resource id in the URL path, such as GET /memberships/{id} and GET /products/{id}, so you can pin the agent to reading a single membership or product and nothing else. Since you choose the operations it may call, endpoints like GET /payments or GET /plans stay off limits unless you add them.

Whop API

Connect the Whop API to your agent

Capabilities

Start building with Whop API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs