bullpen identity show¶
Last updated: August 26, 2026
Show a public Bullpen account identity profile by username or Bullpen user ID
Usage¶
Live Help¶
Show a public Bullpen account identity profile by username or Bullpen user ID
Usage: bullpen identity show [OPTIONS] <USERNAME_OR_USER_ID>
Arguments:
<USERNAME_OR_USER_ID>
Bullpen username or Bullpen user ID. Wallet addresses are rejected; use `bullpen polymarket data trader-profile` for wallet lookup
Options:
--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]
--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.
--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 a Bullpen account identity by username
bullpen identity show alice
# Export a Bullpen account identity profile as JSON
bullpen identity show 018f6b36-5f90-7c2f-a7f2-3b92fb7a7c51 --output json
NOTES:
This command reads Bullpen account identity profiles by username or Bullpen
user ID. Wallet addresses are not Bullpen account identities; use
`bullpen polymarket data trader-profile` for wallet-address lookups.
Example Commands¶
bullpen identity show alice
bullpen identity show 018f6b36-5f90-7c2f-a7f2-3b92fb7a7c51 --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.