Skip to content

bullpen polymarket clob geoblock

Last updated: August 26, 2026

Check Polymarket geo-IP status for the current direct CLOB request path

Usage

bullpen polymarket clob geoblock [OPTIONS]

Live Help

Check Polymarket geo-IP status for the current direct CLOB request path

Usage: bullpen polymarket clob geoblock [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:
  # Check what Polymarket reports for this direct request IP/network path
  bullpen polymarket clob geoblock

  # Export the current request-path signal as JSON
  bullpen polymarket clob geoblock --output json

Example Commands

bullpen polymarket clob geoblock
bullpen polymarket clob geoblock --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
provider string no Provider that reported the signal; polymarket
signal_source string no Scoped provider endpoint; polymarket_clob_geo_ip_endpoint
network_path string no Request path observed by the endpoint; direct_clob_request
direct_clob_ip_blocked boolean no Whether Polymarket reports the current direct-request IP/network path as blocked
observed_ip string yes Request IP address observed by Polymarket when returned
observed_country string yes Country code reported by Polymarket when returned
observed_region string yes Region code reported by Polymarket when returned
normal_prediction_trade_route string no Normal Bullpen prediction route; this is routing metadata, not an eligibility result
route_observation_changes_eligibility boolean no Always false; observing another route does not change eligibility
legal_eligibility_determined boolean no Always false; the CLI does not determine legal eligibility
blocked boolean no Backward-compatible alias for direct_clob_ip_blocked
ip string yes Backward-compatible alias for observed_ip
country string yes Backward-compatible alias for observed_country
region string yes Backward-compatible alias for observed_region
proxy_routes_prediction_trades boolean no Backward-compatible routing metadata; it does not imply a bypass or eligibility change
note string no Scope and eligibility boundary for this provider signal

Example

bullpen polymarket clob geoblock --output json
{
  "provider": "polymarket",
  "signal_source": "polymarket_clob_geo_ip_endpoint",
  "network_path": "direct_clob_request",
  "direct_clob_ip_blocked": false,
  "observed_ip": "203.0.113.10",
  "observed_country": "US",
  "observed_region": "NY",
  "normal_prediction_trade_route": "bullpen_account_services",
  "route_observation_changes_eligibility": false,
  "legal_eligibility_determined": false,
  "blocked": false,
  "ip": "203.0.113.10",
  "country": "US",
  "region": "NY",
  "proxy_routes_prediction_trades": true,
  "note": "Polymarket reports this result for the current request IP and network path. This check does not determine legal eligibility. Bullpen routing does not change Polymarket controls or eligibility."
}

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.