`bullpen hyperliquid pair orders`¶

Last updated: July 13, 2026

List Pear open pair orders

Usage¶

bullpen hyperliquid pair orders [OPTIONS]

Live Help¶

List Pear open pair orders

Usage: bullpen hyperliquid pair orders [OPTIONS]

Options:
      --no-multi-wallet-warning
          Suppress the table-mode warning shown when multiple EVM wallet accounts exist

      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

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

      --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:
  # List open Pear pair orders for the active Hyperliquid account
  bullpen hyperliquid pair orders

  # Export open Pear pair orders as JSON
  bullpen hyperliquid pair orders --output json

PEAR PREREQUISITES:
  Use `bullpen status --output json` and `bullpen doctor auth --output json`
  to confirm the active Bullpen-managed EVM wallet. Run `bullpen login` only
  when diagnostics report login is required. Enable `hyperliquid` for reads/status. Pair orders
  require a cached Pear session from `pair login --yes` or `pair setup --yes`.

OUTPUT:
  Table output is a compact summary of Pear's current response. Use
  `--output json` for the full Pear payload.

Example Commands¶

bullpen hyperliquid pair orders
bullpen hyperliquid pair orders --output json

JSON Output¶

Contract: JSON Output Contract.

Successful output is a single JSON document. The shape below is representative for this command family; commands may add fields without breaking the shared contract.

Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.

Top-level Keys¶

key	type	nullable	notes
`kind`	string	no	Stable envelope kind: `hyperliquid_pear_positions`, `hyperliquid_pear_open_orders`, or `hyperliquid_pear_twap_orders`
`schema_version`	integer	no	Pear read envelope schema version; currently `1`
`source`	string	no	Always `pear` for Pear API-backed pair-trading reads
`account`	string	no	Active Bullpen-managed EVM wallet used for the Pear session and Hyperliquid signing
`data`	array/object/null	no	Raw Pear upstream payload for the selected read endpoint; empty accounts commonly return `[]`

Example¶

bullpen hyperliquid pair orders --output json

{
  "kind": "hyperliquid_pear_open_orders",
  "schema_version": 1,
  "source": "pear",
  "account": "0x1111111111111111111111111111111111111111",
  "data": []
}

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 hyperliquid pair orders¶