bullpen polymarket withdraw¶
Last updated: May 29, 2026
Withdraw USDC.e from a Deposit Wallet on Polygon; other withdrawals use the web app
Usage¶
Live Help¶
Withdraw USDC.e from a Deposit Wallet on Polygon; other withdrawals use the web app
Usage: bullpen polymarket withdraw [OPTIONS]
Options:
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--to <TO>
Destination address
--amount <AMOUNT>
Amount to withdraw (e.g. "100.00")
--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.
--token <TOKEN>
Token to withdraw. CLI supports USDC.e / usdce from Deposit Wallet only
--chain <CHAIN>
Destination chain. CLI supports Polygon USDC.e only; other chains use the web app
--yes
Skip confirmation prompt
--i-know-this-token-is-not-supported-on-destination
Explicitly allow sending pUSD/USDe to a destination that may not support it
--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:
bullpen polymarket withdraw --help
Show options for this command without signing, submitting, or changing state.
Example Commands¶
bullpen polymarket withdraw [OPTIONS]
bullpen polymarket withdraw --help
bullpen polymarket withdraw --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.