← Articles
Whop: payments, payouts, and MCP for builders logo
payments

Whop: payments, payouts, and MCP for builders

· SEP 1, 2026 ·
Read
Share

First call: GET /api/v1/accounts/me. Pin Api-Version-Date. Keys stay server-side.

devrels.xyz/a/288

Whop is a payments and community platform. Merchants sell courses, SaaS, events, groups, and more. Builders get one API for checkout, memberships, payouts, and identity. Merchant start: docs.whop.com/get-started. Builder start: developer/quickstart. Index: /llms.txt. Dashboard: whop.com/dashboard. GitHub whopio.

Versioned API base is https://api.whop.com/api/v1. Send Authorization: Bearer and pin Api-Version-Date (docs example 2026-06-09). Account keys cover one business. App keys cover accounts that installed your app. Keep keys on the server. Prefer the versioned Whop API over Legacy. CLI: whop.sh.

bash
pnpm add @whop/sdk

curl https://api.whop.com/api/v1/accounts/me \
  -H "Authorization: Bearer WHOP_API_KEY"

That returns your account id, which starts with biz_. SDKs: TypeScript @whop/sdk, Python whop-sdk, Ruby whop_sdk. A checkout configuration create call returns a purchase_url.

Agent surfaces
SurfaceJob
https://docs.whop.com/mcpSearch and read the docs
https://mcp.whop.com/mcpLive API. Browser sign-in. No key in the client config.
Skills cataloghttps://docs.whop.com/.well-known/skills/index.json
bash
claude mcp add --transport http whop-docs https://docs.whop.com/mcp
claude mcp add --transport http whop-api https://mcp.whop.com/mcp

Sign up at whop.com/start. Create an Account API key in the dashboard. Do not put that key in a browser, a mobile app, or a public repo.

Keep reading

Get new articles in your inbox

Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.

Whop: payments, payouts, and MCP for builders | devrels.xyz