We just shipped a guide on running a Whop business from inside a coding agent. The Whop CLI is agent neutral: the same binary works standalone in a terminal or inside Claude Code, Cursor, or Codex. Point your agent at it and the dashboard work (metrics, ads, finances, store maintenance, team, app deploys) becomes something you ask for instead of something you click through.
The guide walks seven workflows end to end with the exact commands. Here is the shape of it.
Install and sign in
One command per platform:
# macOS / Linux
curl -fsSL https://whop.com/install.sh | sh
# Homebrew
brew install whopio/tap/whop
# Windows (Node.js 22+)
npm install -g @whop/cli
Verify with whop --version, sign in with whop login (browser sign in or an API key). In Claude Code you do not need to open a terminal at all: ask Claude to install the CLI and sign you in.
Then teach the agent the workflows:
whop skills add
One auth gotcha worth knowing up front: browser login covers most commands, but the ledger and payout commands require API key authentication. If your monthly close fails on whop ledgers report, that is why.
The weekly briefing
The first workflow is the one you will run every Monday. The agent pulls the week's numbers, compares them to the previous week, and flags anything stuck:
whop stats get net_revenue --from 2026-07-20 --to 2026-07-27 --interval day
whop stats get new_users --from 2026-07-20 --to 2026-07-27
whop stats get churn_rate --from 2026-07-20 --to 2026-07-27
whop stats get ad_spend --from 2026-07-20 --to 2026-07-27
whop ads list --first 100
You do not memorize these. You ask "give me my weekly briefing, compare to last week, flag stuck ads" and the agent (with the skill loaded) composes the calls and writes the summary. whop stats list shows the full metric catalog, dozens deep.
The monthly close
The agent generates an income statement, itemizes fees, lists payouts, and compiles the result into a shareable report:
whop ledgers report --report_type income_statement
whop stats get fees --from 2026-07-01 --to 2026-07-31 --breakdown_by fee_type
whop payouts list
This is the workflow that needs the API key auth mentioned above.
The ad testing loop
The most agentic workflow in the guide. The agent generates image variants, launches a draft campaign, watches daily performance, pauses underperformers, and duplicates the winners:
whop media generate --type image --prompt "your creative description" --wait
whop ad-campaigns update adcamp_XXXXXXXX --status active
whop ads list --order cost_per_result --direction desc --stats_from 2026-07-20 --first 100
whop ads pause ad_XXXXXXXX
whop ad-groups duplicate adgrp_XXXXXXXX --count 2 --preserve_engagement
The whop ads create call takes the full campaign structure (headlines, call to action, creatives, ad group, budget) as one command; the guide shows the complete invocation. Generated images and ad spend draw from your company's Whop balance, and whop deposits create --destination biz_XXXXXXXX --amount 50 tops it up.
Store, team, and problem detection
Three quicker workflows round out the operations side. Store maintenance audits products and plans, fixes missing headlines, and archives slow movers (whop products list, whop products update). Team management promotes members across five roles (owner, admin, sales_manager, moderator, advertiser) with whop team-members update. And early problem detection watches dispute and refund rates week over week, pausing ad groups that drive bad traffic before the numbers get expensive:
whop stats get dispute_rate --from 2026-06-29 --to 2026-07-27 --interval week
whop ad-groups pause adgrp_XXXXXXXX
Deploy apps to Whop from the CLI
The last workflow goes past operations into building. The agent scaffolds an app, deploys it live on Whop infrastructure, and reads the logs:
whop apps init --name "my app"
whop apps deploy
whop apps logs --level error --since 1h
Apps land on a *.whop.app address. Combined with the rest of the CLI, the loop from "idea" to "deployed on the business that pays for it" runs in one conversation.
Headless mode
Everything above also runs without an agent: set WHOP_API_KEY in the environment and pass --format json for output that pipes into cron jobs, CI, or your own scripts. The interactive agent path and the headless path are the same binary and the same commands.
Where to take it
The guide closes with twelve prompt ideas beyond the seven workflows: price testing via plan duplication, time limited promotions, regional pricing, affiliate commission tuning, payment threshold webhooks, API key rotation, payout routing by cost, conversion analysis, scheduled revenue digests, and investor update generation.
- Full guide: step by step on the Whop blog
- CLI docs: docs.whop.com/developer/cli
If you already live in Claude Code, Cursor, or Codex, this turns the business side of your whop into part of the same conversation as your code.
Top comments (0)