Skip to content

bullpen tracker add

Last updated: July 13, 2026

Track a Polymarket address

Usage

bullpen tracker add [OPTIONS] <ADDRESS>

Live Help

Track a Polymarket address

Usage: bullpen tracker add [OPTIONS] <ADDRESS>

Arguments:
  <ADDRESS>
          Ethereum address to track

Options:
      --nickname <NICKNAME>
          Display name for this address

      --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]

      --group <GROUP>
          Assign to a wallet group

      --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.

      --notify-trades <NOTIFY_TRADES>
          Enable trade notifications

          [possible values: true, false]

      --notify-comments <NOTIFY_COMMENTS>
          Enable comment notifications

          [possible values: true, false]

      --trade-threshold <TRADE_THRESHOLD>
          Min trade size (USD) for notifications

      --specific-markets <SPECIFIC_MARKETS>
          Restrict trade tracking to comma-separated market slugs

      --category <CATEGORY>
          Restrict trade tracking to one category

      --read-only
          Enable read-only mode: blocks all mutating commands

      --min-position-size <MIN_POSITION_SIZE>
          Minimum position size (USD) to track

      --non-interactive
          Suppress interactive prompts; does NOT imply --yes for money-moving commands

          [env: BULLPEN_NON_INTERACTIVE=]

      --action <ACTION>
          Restrict trade tracking to an action such as buy or sell

  -h, --help
          Print help (see a summary with '-h')

EXAMPLES:
  # Review tracked addresses before adding another one
  bullpen tracker list

  # Track a Polymarket wallet and label it; this changes tracker state
  bullpen tracker add 0x1111111111111111111111111111111111111111 --nickname whale-1

  # Track and assign the address to a group; this changes tracker state
  bullpen tracker add 0x1111111111111111111111111111111111111111 --group group-123

  # Export the add result as JSON
  bullpen tracker add 0x1111111111111111111111111111111111111111 --nickname whale-1 --output json

Example Commands

bullpen tracker list
bullpen tracker add 0x1111111111111111111111111111111111111111 --nickname whale-1
bullpen tracker add 0x1111111111111111111111111111111111111111 --group group-123
bullpen tracker add 0x1111111111111111111111111111111111111111 --nickname whale-1 --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.