`bullpen polymarket merge`¶

Last updated: May 29, 2026

Merge YES and NO tokens back into USDC

Usage¶

bullpen polymarket merge [OPTIONS] --condition <CONDITION> --amount <AMOUNT>

Live Help¶

Merge YES and NO tokens back into USDC

Usage: bullpen polymarket merge [OPTIONS] --condition <CONDITION> --amount <AMOUNT>

Options:
      --condition <CONDITION>
          Condition ID (0x-prefixed 32-byte hex, e.g. 0xbd31dc8a...)

      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --amount <AMOUNT>
          Amount in USDC sets to merge (e.g. "10" for 10 sets)

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

      --partition <PARTITION>
          Custom partition as comma-separated index sets (e.g. "1,2" for binary)

      --parent-collection <PARENT_COLLECTION>
          Parent collection ID for nested positions (defaults to zero)

      --neg-risk
          Route through NegRiskAdapter (required for neg-risk conditions)

      --read-only
          Enable read-only mode: blocks all mutating commands

      --yes
          Skip confirmation prompt

      --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 merge --help
      Show options for this command without signing, submitting, or changing state.

Example Commands¶

bullpen polymarket merge [OPTIONS] --condition <CONDITION> --amount <AMOUNT>
bullpen polymarket merge --help
bullpen polymarket merge --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.

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 merge¶