strategy_type describes activity recorded for a Polymarket wallet. Use it to compare wallets by two-sided positions, category focus, trade density, or activity spread across categories.
The label summarizes stored history. Profit, win rate, and grade do not choose it, and a losing wallet keeps the same style as a profitable wallet with the same activity.
Request a wallet’s style
Passexpand=strategy to Trader or Batch traders.
The entire
strategy section is absent if you omit the expansion or the wallet has no stored classification. An explicit unclassified value means the classifier ran but could not establish a style from the available history.
Current styles
The classifier uses the lifetime market records 0xinsider has stored, rather than a recent trading window. That history can cover fewer markets or fills than the wallet’s complete Polymarket history. Every measure below counts the wallet’s sports and esports markets only. A market in any other category, or with no category, does not enter the style. “Stored markets” in the table means the wallet’s stored sports and esports markets.
Category shares use the stored cost basis in USD of the wallet’s sports and esports markets. This is not the wallet’s lifetime trading volume.
Each of those markets has a known sports or esports category, so the 80% coverage requirement is always met. A market with no category cannot be placed in sports or esports and is left out; it does not become another category or evidence of diversification.
How labels are assigned
A wallet needs at least 20 stored sports and esports markets before the classifier compares patterns. A wallet that traded many markets but fewer than 20 sports and esports markets isunclassified. Each qualifying pattern receives the rule score shown above, so a wallet can match more than one pattern.
The strongest pattern needs a score of at least 0.5 and a lead of at least 0.15 over the next pattern. Without that separation, or when no pattern qualifies, usable history receives mixed rather than whichever rule appears first.
The API reads the latest stored classification. Your request does not run the classifier. When the rules change, a background process rewrites every stored label, and a wallet keeps its older label until its turn comes.
Filter the leaderboard
Pass one of the 6 current IDs to Leaderboard:strategy_type without an expansion when a classification exists. An unrecognized strategy filter returns 400 with error.param set to strategy.
Historical labels and client compatibility
The classifier wrote 10 other IDs before October 1, 2026:accumulator, algo_trader, arbitrageur, directional, event_driven, market_maker, momentum, scalper, speculator, and swing_trader. Every wallet has been reclassified since, so no response carries one.
Leaderboard still accepts them as strategy filters, and each returns an empty list. They are not aliases for the new styles. The OpenAPI document, the SDK and the MCP tools list only the 6 current IDs.
If your client validates a fixed enum or uses an exhaustive switch, regenerate its types from the OpenAPI document and drop the historical values.
Limits
- Two-sided positions do not establish arbitrage or market making. They do not prove that both sides were held at the same time or that the combined cost guaranteed a profit.
- High trade density does not establish scalping, holding duration, or automation. It counts recorded fills per stored market.
- Category focus does not establish reactions to news, and diversified activity does not establish lower risk.
- The label does not identify intent, maker or taker order role, or future trades.
- The API does not publish a confidence probability. The internal rule score measures support for a pattern, not the chance that a trading strategy is correct.
pnl.in_scope on Trader, to assess performance separately.