bullpen recover redeem¶
Last updated: July 13, 2026
Redeem resolved prediction-market positions
Usage¶
Live Help¶
Redeem resolved prediction-market positions
Usage: bullpen recover redeem [OPTIONS]
Options:
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--condition-ids <CONDITION_IDS>
Condition IDs to redeem (comma-separated)
--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.
--limit <LIMIT>
Limit auto-discovered redeem candidates. Use --condition-ids for exact targeting
--yes
Skip confirmation prompt
--dry-run
Print the redeem plan without submitting
--support-bundle
Build a no-submit support bundle as JSON
--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:
# Preview auto-discovered redeemable positions
bullpen recover redeem --dry-run --output json
# Preview redeeming a specific condition ID
bullpen recover redeem --condition-ids 0xYourConditionId --dry-run --output json
# Submit the reviewed redeem plan
bullpen recover redeem --condition-ids 0xYourConditionId --yes
This checks your account and shows the safest redeem plan before anything moves.
Example Commands¶
bullpen recover redeem --dry-run --output json
bullpen recover redeem --condition-ids 0xYourConditionId --dry-run --output json
bullpen recover redeem --condition-ids 0xYourConditionId --yes
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.