canonical: https://jentic.com/apis/whop.com/whop

# Whop API

Whop digital commerce platform API for managing users, memberships, products, and payments. The API exposes 13 endpoints secured with bearer authentication.

## For AI agents

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

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Get user profile
- List payments
- Integrate Whop API into automated workflows
- Query and filter Whop API records by parameters
- Monitor Whop API operational status and events

## Use cases

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

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Experiences** — Operations related to Experiences
- **Memberships** — Operations related to Memberships
- **Payments** — Operations related to Payments
- **Plans** — Operations related to Plans
- **Products** — Operations related to Products

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/whop.com/whop/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

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