`bullpen funds balances`¶

Last updated: July 13, 2026

Show the existing multi-chain portfolio balances view

Usage¶

bullpen funds balances [OPTIONS]

Live Help¶

Show the existing multi-chain portfolio balances view

Usage: bullpen funds balances [OPTIONS]

Options:
      --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 the existing multi-chain portfolio balances view
  bullpen funds balances

  # Export balances as JSON
  bullpen funds balances --output json

Example Commands¶

bullpen funds balances
bullpen funds balances --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.

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

Routing-wallet probe fields¶

funds balances --output json includes routing-wallet probe metadata so agents can tell which routing-wallet balances were actually checked.

routing_wallet_probe_status: one of verified_clean, verified_nonzero, partial_unverified, or probe_failed.
routing_wallet_probe_scope: current proof scope. The CLI currently verifies Polygon routing wallets only, so successful probes are partial.
verified_chains / routing_wallet_probe_verified_chains: chains checked by this run.
unverified_chains / routing_wallet_probe_unverified_chains: chains not checked by this run. When this list is non-empty, status is partial_unverified, never verified_clean.
routing_wallet_warnings: null means no non-zero routing-wallet balances were found on the verified scope only. It is only globally clean when unverified_chains is empty.
next_diagnostic_command: follow-up command for deposit-route diagnosis.

Current successful probes verify polygon and leave arbitrum and ethereum unverified; backend/manage-wallet routing data is required for full Arbitrum/Ethereum routing-wallet proof.

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 funds balances¶