bullpen polymarket data leaderboard¶
Last updated: May 29, 2026
View top traders on the leaderboard
Usage¶
Live Help¶
View top traders on the leaderboard
Usage: bullpen polymarket data leaderboard [OPTIONS]
Options:
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--period <PERIOD>
Legacy time period alias: day, week, month, all
--env <ENV>
Target environment to connect to (overrides config.toml)
[env: BULLPEN_ENV=]
[possible values: staging, production]
--time-period <TIME_PERIOD>
Time period: 1d, 7d, 30d, 90d, all
--config <CONFIG>
Path to a custom config.toml file (overrides $BULLPEN_CONFIG and the default location).
Explicit --config and BULLPEN_CONFIG paths fail closed: if the file is missing, the CLI exits validation instead of silently loading defaults. Credentials still resolve via BULLPEN_HOME, so set BULLPEN_HOME too when isolating a session.
--sort <SORT>
Bullpen-indexed sort: pnl, volume, win-rate, positions, copyability, newest
--badge <BADGES>
Filter by badge (repeatable)
--style <STYLES>
Filter by trading style (repeatable)
--read-only
Enable read-only mode: blocks all mutating commands
--risk-tier <RISK_TIERS>
Filter by risk tier: low, medium, high (repeatable)
--hide-farmers
Hide likely farmers
--non-interactive
Suppress interactive prompts; does NOT imply --yes for money-moving commands
[env: BULLPEN_NON_INTERACTIVE=]
--hide-bots
Hide likely bots
--search <SEARCH>
Search by display name, wallet address, or Twitter handle
--limit <LIMIT>
Maximum number of traders to show
[default: 25]
-h, --help
Print help (see a summary with '-h')
EXAMPLES:
bullpen polymarket data leaderboard --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen polymarket data leaderboard [OPTIONS]
bullpen polymarket data leaderboard --help
bullpen polymarket data leaderboard --output json
JSON Output¶
Contract: JSON Output Contract.
This command supports --output json, but this generated reference page intentionally does not include a synthetic success schema or example.
Use the live command in your target environment to inspect command-specific success fields. Error output follows the shared JSON output contract linked above.
Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.
Stability¶
Patch releases may add nullable or optional fields. Minor releases may add required fields or increment schema_version. Major releases may remove or rename fields.