bullpen polymarket pnl-series¶
Last updated: July 13, 2026
Show Polymarket user PnL time series for a wallet address
Usage¶
Live Help¶
Show Polymarket user PnL time series for a wallet address
Usage: bullpen polymarket pnl-series [OPTIONS] --address <ADDRESS>
Options:
--address <ADDRESS>
Polymarket wallet 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]
--interval <INTERVAL>
PnL interval: all, 1m, 1w, 1d, 12h, 6h, or max
[default: 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.
--fidelity <FIDELITY>
PnL point fidelity: 1d, 18h, 12h, 3h, or 1h
[default: 1h]
--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:
# Show all-time hourly user PnL points for a Polymarket wallet
bullpen polymarket pnl-series --address 0x1111111111111111111111111111111111111111 --interval all --fidelity 1h
# Use the web-app vocabulary alias and export 1-week user PnL points as JSON
bullpen polymarket user-pnl --address 0x1111111111111111111111111111111111111111 --interval 1w --fidelity 3h --output json
Example Commands¶
bullpen polymarket pnl-series --address 0x1111111111111111111111111111111111111111 --interval all --fidelity 1h
bullpen polymarket user-pnl --address 0x1111111111111111111111111111111111111111 --interval 1w --fidelity 3h --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.