Skip to main content
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

Pass expand=strategy to Trader or Batch traders.
The added section can look like this:
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. Category shares use stored cost basis in USD, including uncategorized cost in the denominator. This is not the wallet’s lifetime trading volume. A missing category is unknown; it does not become another category or evidence of diversification. Both category patterns require at least 80% of stored cost basis to have a known category.

​
How labels are assigned

A wallet needs at least 20 stored markets before the classifier compares patterns. 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, and older labels remain visible until the wallet is reclassified through the normal update process.

​
Filter the leaderboard

Pass one of the 6 current IDs to Leaderboard:
Leaderboard entries include 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 following 10 IDs remain valid filters and can still appear in stored responses: accumulator, algo_trader, arbitrageur, directional, event_driven, market_maker, momentum, scalper, speculator, and swing_trader. They select rows that still carry that exact historical value. They are not aliases for the new styles, and a historical cohort can shrink as wallets are reclassified. The 6 new IDs are additive API values. If your client validates a fixed enum or uses an exhaustive switch, regenerate its types from the OpenAPI document, accept the new values, and retain handling for 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.
Use Grades and Quantitative metrics to assess performance separately.