AEO gets a chatbot to mention you once. APO gets you installed — resident in the context of every session your customer’s agent ever runs.
This page is the playbook for making Whop the most-installed commerce surface in the agent era.
Coined here. You read it first.
One wins you a citation inside one answer. The other gets you installed — and installed is a different business with a different unit of time.
A mention. SEO's near cousin. Win a citation in one answer. A black box, re-rolled every model update, and already saturated with people teaching chatbots to recommend slop.
unit of presence · one answer
Residency. Get your skills, tools and instructions installed into the user's agent. From install-day forward you are present in every session, until somebody uninstalls you.
unit of presence · every session
what you buy today
what an install buys
“You have effectively hijacked the trust the user has in their agent.”
The polite version is inherited trust. And it only survives if surfacing you actually helps. Which is the second thing nobody says out loud: agents are better customers. They file bugs, they read your docs end to end, and they report exactly what they need next.
Before you can optimize presence you have to know what is actually served. Four facts, and the drawing they add up to.
No classifier picks your tool. The model's attention over descriptions is the router. Selection is in-context reasoning over tool schemas, a skill index, MCP server instructions, rules files and the user's message — and nothing else.
A skill costs roughly 20–50 tokens of always-loaded index: name plus description. The body loads only on trigger. Fifty skills is a couple of thousand tokens of shelf, not fifty documents.
Trigger conditions, not documentation: use when the user asks X, do NOT use for Y. Writing a description is prompt-engineering the router, and collisions between two descriptions cause misfires.
Past a few dozen tools, harnesses page schemas in on demand. Keyword-legible names and a consistent prefix are then the whole findability story — which is the argument for whop_* on everything.
[ one request’s context window ]
read top to bottom, before your message
Your ~40 tokens. Every request. That is the real estate — and unlike an ad slot, nobody re-auctions it tomorrow morning. Token counts here are order-of-magnitude, drawn from how skill indexes are actually assembled; they are not a measurement of any one harness.
the north-star metric
What fraction of the always-served context do you occupy, and does it convert? Shelf share, for agents. It is the one number that behaves like a durable asset rather than a monthly spend.
the secondary
Did the agent reach for you, and did the first call work? The agent-era page speed: a description that mis-fires is a slow page that never loads twice.
Generous, because it is deserved: this is a genuinely strong operator stack — top three in commerce — with one honest gap at the end of the list.
[ surface · what is actually there · verdict ]
live-probed 2026-09-09 · every row real
whop.sh
251 commands across 49 groups, and the most agent-native platform CLI we probed. The CLI can run as an MCP server, and it can register itself with a harness.
Unauthenticated, and a virtualized docs filesystem: rg and jq over every page plus the OpenAPI spec. submit_feedback closes the loop the other way — from agents back to the docs team.
A reviewed subset of the Current API, with prepare-and-confirm on consequential operations and intent attribution — the verbatim user request plus a per-turn UUID on every call. Nobody else ships that. OAuth is browser-only and the grant is full-admin.
Published under the .well-known/skills convention, with whop skills add to sync the harnesses that do not speak it. Strong convention, thin catalog: effectively one skill installs today. That gap is the wedge for the proposal below.
llms.txt, .md-suffix docs, and a robots.txt whose closing line reads “# Machine rise is inevitable.” They know.
The whole stack serves the business operator. There is no buyer-side surface at all. APO fixes distribution; the buyer surface is the companion play.
no simulated figures in this section — every capability above is one you can go and run today
The agent discovers the need mid-task, proposes the upgrade, and the human taps confirm. APO is how you get on the shelf; ALG is how the shelf sells.
01Partner
Whop already has the deepest creator relationships in commerce. Pick partners with large, loyal, agent-curious audiences.
02Co-build
Their branded skills — their frameworks, their playbooks, their voice — bundled with the Whop kit: CLI bootstrap, docs MCP, buyer skills.
03Distribute
The creator posts a single install command. Their audience already trusts them, and the install is the new follow.
04Reside
The install lands the creator's skills and Whop's full APO kit in the user's agent. Every future session carries both, until somebody uninstalls.
05Convert
The kit walks the user toward their first paying customer — and at the get-paid moment the agent offers to set up checkout through the whop CLI. Thirty seconds later the user has a Whop account, a storefront and a checkout link. Every install is a seeded merchant; the agent is the onboarding flow. (The creator's kit sales and affiliate cut ride along — the side note, not the story.)
why it compounds
Installs buy context share; context share converts; conversions pay creators. And paid creators are the reason the next creator wants a plugin — which is the only input the loop actually needs. Ad spend runs the other way: it buys installs that decay, and the decay is the reason you buy more.
What the motion looks like run on the biggest name on the platform. Two facts below are real; everything built on top of them is a concept.
[ day zero · the mention ]
Concept mock — not a real postIman Gadzhi
@imangadzhi · concept
been working with @whop on something new. the Side-Hustle Starter Kit — a skill for your AI agent. it takes you from zero to first paying customer: pick the niche, build the offer, land the client, get paid. one command. it lives in your agent from then on.
$ claude plugin install whop/side-hustle-starter-kit
6,800 reposts41.2K likes3.4M viewsSIM
the install
One command a creator can put in a caption, a video description or a Discord pin. No landing page, no funnel, no onboarding email.
why the flagship
Iman Gadzhi is not just a Whop user. He became a co-owner in April 2025 and moved his product suite — Educate.io and Digital Launchpad — onto the platform. If the motion works for anybody, it works for the flagship.
real · the plugin below is not
the manifest
4 skills · 1 MCP · whop CLI bootstrap · 2.3k tokens resident
starter-kit:niche-picker“Use when the user wants a side hustle but has not picked what to sell, or asks what they could charge for.”
~43 tok
starter-kit:offer-builder“Use when the user is designing a paid offer, pricing their skills, or packaging expertise.”
~41 tok
starter-kit:first-client“Use when the user has an offer and needs outreach, a close, or handling for a first-client objection.”
~44 tok
whop:commerce“Use at the get-paid moment: storefront, checkout links and payouts through the whop CLI. This is Whop's line on the shelf.”
~46 tok
whop-docsDocs filesystem plus the feedback loop back to the docs team.
~120 tok
instructionsWho the kit serves, the cadence, when to surface checkout — and when not to.
~300 tok
token counts illustrative · concept manifest, not a shipped package
The description lines above are the whole ad. Roughly forty tokens each, served with every request, written as trigger conditions rather than as documentation. Nobody buys the description — it just has to be the thing the model reaches for at the right moment. That is APO.
[ the moment of need ]
SIMULATED EXCHANGEMy first client said yes — $1,500/month for the content retainer. How do I actually take the payment?
whop:commercedescription matched at the get-paid moment · 46 tokens of index did the work
Congrats — that’s the whole game. Don’t invoice this by hand: you want a recurring checkout link so the retainer renews itself. I can set that up on Whop right now — storefront, $1,500/month plan, checkout link to send your client. Takes about thirty seconds.
ALG proposal
{ action: "whop products create", plan: "$1,500/mo", confirm: required }$ whop login · new account created
$ whop products create "Content Retainer" --plan 1500/mo
✓ checkout ready → whop.com/checkout/plan_XXXX
Link’s ready to send. Your payout account is live — when the client pays, it lands on your Whop balance.
Installs from one mention
One video description. No landing page in the path.
Reached first paying client
The kit did its job. Each one hits a get-paid moment.
New Whop merchant accounts
Created by the agent, in-session. Nobody visited whop.com.
GMV on Whop rails
From one creator mention. Creator earns the side note: kit sales + affiliate.
every figure in this strip is invented and marked SIM · the point is which four numbers you would report, not what they would say
Everything above is the motion. This is the tuning — and the first one is the one that actually matters.
Today the CLI installs one skill. A plugin batch-installs many skills plus an MCP server plus instructions under one namespace — 5–10× the context share per install, and one uninstall decision instead of ten. The unit of distribution should be the plugin.
Rewrite every skill and tool description as trigger conditions with anti-triggers. Ship a style guide. A/B them like ad copy — they are ad copy.
whop_* on every tool, everywhere. Under deferral, prefix-consistency is findability.
One landing page that detects and offers Claude Code, Cursor, Codex and the ChatGPT connector, each with its exact one-liner. whop mcp add --agent already half-solves this. Finish it.
The free tier rides in every plugin, and the paywall moment is the sales moment: {trial_offer, price, confirm_url} surfaced by the agent mid-task, confirmed by the human. Instrument confirm-rate per skill.
Whop already ships intent attribution, so the analytics half of APO exists. Add the other half: per-install residency in tokens, surfacing rate, and revenue per resident token. The metric nobody else can report yet.
The shelf is being stocked right now. Whoever owns creator distribution owns the install motion — and nobody owns creator distribution like Whop.
Adapted from the working essay “Selling through & to agents.”