`bullpen polymarket wrap`¶

Last updated: May 29, 2026

Wrap USDC into pUSD (Polymarket collateral token)

Usage¶

bullpen polymarket wrap [OPTIONS] <AMOUNT>

Live Help¶

Wrap USDC into pUSD (Polymarket collateral token)

Usage: bullpen polymarket wrap [OPTIONS] <AMOUNT>

Arguments:
  <AMOUNT>
          Amount in USDC to wrap (e.g. "100" for $100)

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

          [possible values: table, json]

      --yes
          Skip confirmation prompt

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

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

      --preview
          Preview the approve + wrap relayer batch without signing or submitting

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

      --wallet <WALLET>
          Pin the signer to a specific owner EOA (0x…). Bypasses the active-wallet cache and resolves the Polymarket wallet context directly for this address. Use in bot automation to avoid wallet-select races

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

Example Commands¶

bullpen polymarket wrap [OPTIONS] <AMOUNT>
bullpen polymarket wrap --help
bullpen polymarket wrap --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 wrap¶