bullpen polymarket markets¶
Last updated: July 13, 2026
List and filter markets
Usage¶
Live Help¶
List and filter markets
Usage: bullpen polymarket markets [OPTIONS]
Options:
--limit <LIMIT>
Maximum results (default 25)
[default: 25]
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--env <ENV>
Target environment to connect to (overrides config.toml)
[env: BULLPEN_ENV=]
[possible values: staging, production]
--sort <SORT>
Sort by: volume (default), liquidity, volume_24hr (alias: volume24h)
[default: volume]
--active
Only active markets
--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.
--closed
Only closed markets
--tag-id <TAG_ID>
Filter by tag ID
--min-volume <MIN_VOLUME>
Minimum volume
--min-liquidity <MIN_LIQUIDITY>
Minimum liquidity
--read-only
Enable read-only mode: blocks all mutating commands
--non-interactive
Suppress interactive prompts; does NOT imply --yes for money-moving commands
[env: BULLPEN_NON_INTERACTIVE=]
-h, --help
Print help (see a summary with '-h')
EXAMPLES:
# List active markets by volume
bullpen polymarket markets --active --sort volume --limit 10
# Export active markets for scripting
bullpen polymarket markets --active --sort volume --limit 10 --output json
# Browse recently closed markets
bullpen polymarket markets --closed --limit 10
Example Commands¶
bullpen polymarket markets --active --sort volume --limit 10
bullpen polymarket markets --active --sort volume --limit 10 --output json
bullpen polymarket markets --closed --limit 10
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.