Skip to content

bullpen polymarket status

Last updated: May 29, 2026

Show Polymarket platform status and per-component health (read-only)

Usage

bullpen polymarket status [OPTIONS]

Live Help

Show Polymarket platform status and per-component health (read-only)

Usage: bullpen polymarket status [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:
  bullpen polymarket status --help
      Show options for this command without signing, submitting, or changing state.

Example Commands

bullpen polymarket status [OPTIONS]
bullpen polymarket status --help
bullpen polymarket status --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
status string no ok when the status-page fetch succeeds
fetched_at string no UTC timestamp for the status-page fetch used in this response
cached_seconds integer no Age of the in-process cached status snapshot
polymarket_status object no Page status, status URL, and component health array

Example

bullpen polymarket status --output json
{
  "status": "ok",
  "fetched_at": "2026-05-29T13:42:11Z",
  "cached_seconds": 0,
  "polymarket_status": {
    "page_status": "HASISSUES",
    "status_url": "https://status.polymarket.com",
    "components": [
      {"name": "Website", "status": "OPERATIONAL"},
      {"name": "CLOB API", "status": "PARTIALOUTAGE"},
      {"name": "Markets API", "status": "OPERATIONAL"},
      {"name": "Polygon (RPC)", "status": "DEGRADEDPERFORMANCE"},
      {"name": "User auth", "status": "OPERATIONAL"},
      {"name": "Sports API", "status": "OPERATIONAL"}
    ]
  }
}

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.