bullpen polymarket search

Last updated: July 13, 2026

Search prediction markets and trader profiles

Usage

bullpen polymarket search [OPTIONS] <QUERY>

Live Help

Search prediction markets and trader profiles

Usage: bullpen polymarket search [OPTIONS] <QUERY>

Arguments:
  <QUERY>
          Search query

Options:
      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --type <TYPE>
          Filter by result type: all, market/event, user/profile

          [default: all]

      --env <ENV>
          Target environment to connect to (overrides config.toml)

          [env: BULLPEN_ENV=]
          [possible values: staging, production]

      --limit <LIMIT>
          Number of visible table rows per type; JSON keeps top-level event/profile results

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

      --status <STATUS>
          Filter by market status: active, closed

      --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:
  # Search markets by keyword
  bullpen polymarket search bitcoin --type market

  # Export active market search results
  bullpen polymarket search bitcoin --type market --limit 5 --output json

Example Commands

bullpen polymarket search bitcoin --type market
bullpen polymarket search bitcoin --type market --limit 5 --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.

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.