`bullpen polymarket consolidate`¶

Last updated: August 26, 2026

Preview or recover eligible Polymarket funds without changing wallet selection.

Usage¶

bullpen polymarket consolidate [OPTIONS]

Live Help¶

Preview or recover eligible Polymarket funds without changing wallet selection.

Orchestrates: open-order cancellation, position transfer, pUSD/USDC.e/USDC sweep, direct transfer from a wallet address you control when local control and gas are proven, and order credit warning (manual web-app withdrawal). Dry-run by default; pass `--yes` to execute. It refreshes the source, destination, and exact transfer details before submit, validates the full plan before any transfer, and never changes the selected trading wallet.

Usage: bullpen polymarket consolidate [OPTIONS]

Options:
      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --owner <ADDRESS>
          Restrict to a single Bullpen-managed 0x wallet. Default: every Bullpen-managed 0x wallet in your account

      --env <ENV>
          Target environment to connect to (overrides config.toml)

          [env: BULLPEN_ENV=]
          [possible values: staging, production]

      --wallet-kind <KIND>
          Force the target wallet kind for all owners, overriding the server-selected default. Pass `safe` or `dw` (alias `deposit`)

          [possible values: safe, dw]

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

      --include <LIST>
          Comma-separated list of asset classes to handle: `positions,orders,balances`. Default: all

          [default: positions,orders,balances]

      --dry-run
          Print the plan without executing. Default behavior unless `--yes`

      --yes
          Required to execute the reviewed plan. Without this flag, prints dry-run only

      --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 the funds recovery plan without submitting anything
  bullpen polymarket consolidate --dry-run --output json

  # Execute the server-selected funds recovery plan after reviewing the dry-run
  bullpen polymarket consolidate --yes

  # Preview only balance sweeps for one Bullpen-managed 0x wallet
  bullpen polymarket consolidate --owner 0x1111111111111111111111111111111111111111 --include balances --dry-run

Prefer the guided alias for customer recovery:
  bullpen recover funds --dry-run --output json
  bullpen recover funds --yes

Example Commands¶

bullpen polymarket consolidate --help

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.

Error Envelope¶

When a Polymarket CLOB or gasless-relayer rejection coincides with a degraded Polymarket status page, the error envelope may include a polymarket_status object:

{
  "polymarket_status": {
    "page_status": "HASISSUES",
    "status_url": "https://status.polymarket.com",
    "affected_components": [
      {"name": "CLOB API", "status": "PARTIALOUTAGE"}
    ],
    "advisory": "Polymarket is experiencing issues; this rejection is most likely a Polymarket-side outage."
  }
}

The field is omitted on local validation/auth/balance errors and when the status-page fetch times out or reports healthy relevant components.

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.

bullpen polymarket consolidate¶