Skip to content

bullpen hyperliquid fees

Last updated: July 13, 2026

Show current fee rates and fee schedule

Usage

bullpen hyperliquid fees [OPTIONS]

Live Help

Show current fee rates and fee schedule

Usage: bullpen hyperliquid fees [OPTIONS]

Options:
      --address <ADDRESS>
          Ethereum address to query. Defaults to the authenticated account

      --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:
  # Show Hyperliquid fee rates for an address
  bullpen hyperliquid fees --address 0x1111111111111111111111111111111111111111

  # Export Hyperliquid fee rates as JSON
  bullpen hyperliquid fees --address 0x1111111111111111111111111111111111111111 --output json

Example Commands

bullpen hyperliquid fees --address 0x1111111111111111111111111111111111111111
bullpen hyperliquid fees --address 0x1111111111111111111111111111111111111111 --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
address string no Hyperliquid account address queried
dailyUserVlm array no Recent daily volume rows returned by Hyperliquid
feeSchedule object no Current fee schedule and VIP/MM tier tables
userCrossRate string/decimal no User taker rate for perp orders
userAddRate string/decimal no User maker rate for perp orders
userSpotCrossRate string/decimal no User taker rate for spot orders
userSpotAddRate string/decimal no User maker rate for spot orders
activeReferralDiscount string/decimal no Active referral discount reported by Hyperliquid
trial object yes Trial metadata from Hyperliquid when available
feeTrialReward string/decimal yes Trial fee reward when available
nextTrialAvailableTimestamp integer yes Next trial availability timestamp when returned
stakingLink object yes Staking link metadata from Hyperliquid when available
activeStakingDiscount object yes Active staking discount metadata when available

Example

Example JSON output
bullpen hyperliquid fees --address 0x1111111111111111111111111111111111111111 --output json
{
  "address": "0x1111111111111111111111111111111111111111",
  "dailyUserVlm": [
    {
      "date": "2026-05-30",
      "userCross": "10000.0",
      "userAdd": "2500.0",
      "exchange": "0.0"
    }
  ],
  "feeSchedule": {
    "cross": "0.0004",
    "add": "0.0001",
    "spotCross": "0.0007",
    "spotAdd": "0.0002",
    "tiers": {
      "vip": [],
      "mm": []
    },
    "referralDiscount": "0.04",
    "stakingDiscountTiers": []
  },
  "userCrossRate": "0.0004",
  "userAddRate": "0.0001",
  "userSpotCrossRate": "0.0007",
  "userSpotAddRate": "0.0002",
  "activeReferralDiscount": "0.04",
  "trial": null,
  "feeTrialReward": null,
  "nextTrialAvailableTimestamp": null,
  "stakingLink": null,
  "activeStakingDiscount": null
}

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.