Filter Polymarket Wallets by Market | BlockRun

Provide the full condition IDs of 1–10 Polymarket markets to find wallets that traded those markets. Review matching wallet addresses and the supplier’s combined statistics for the selected markets.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use `filter-polymarket-wallets-blockrun` for my selected Polymarket markets. Ask for 1–10 full market condition IDs if they are missing. Put their comma-separated values in queryParams.markets, with filtering parameters directly in queryParams. Use market_logic=and and window=all_time unless I request a supported alternative; use my requested limit or the supplier’s documented default 100. If a requested filter cannot be applied, explain it and ask how to proceed rather than silently broadening the search. Reuse my Toolmu connection, or follow https://toolmu.com/SKILL.md if setup is needed. Work within my existing budget and authorization. Show one page of wallet addresses and selected-market metrics with their units, preserving nulls and original rate values. Include pagination information and continue within my requested scope if further pages are needed. Do not treat addresses as verified people or past results as future-profit guarantees.

Task:
For the Polymarket market condition ID I provide, request up to 5 matching wallets using all-time statistics. Show their addresses, matched-market counts, total PnL in USD and trade counts. Keep null values and say whether another page is available.

Paste into your connected AI's conversation.

Connection guide

Up to 0.01122 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

BlockRun

Filter Polymarket Wallets by Market | BlockRun

You receive

You receive a page of matching wallet records with addresses, matched-market counts and trading statistics. These include trade counts, volume and profit/loss metrics for the selected markets and time window. The response also identifies the market selection, matching logic and pagination, so your Agent can organize the records for comparison within that scope.

Start with your task

For the Polymarket market condition ID I provide, request up to 5 matching wallets using all-time statistics. Show their addresses, matched-market counts, total PnL in USD and trade counts. Keep null values and say whether another page is available.

What to know

A wallet address does not establish a person’s identity. The statistics describe the selected markets and window, rather than the wallet’s whole portfolio, and past performance does not guarantee future profit. A page may contain fewer records than requested and does not establish complete or fully current coverage.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Wallet-filter parameters`queryParams`	`object`	Optional	Query object for the filter request. Supply 1–10 full market condition IDs as the comma-separated markets value directly in this object, along with supported optional parameters. The task needs market IDs even though this container is marked optional.
Nested query object`queryParams.query`	`object`	Optional	Optional nested object with no individual filters defined inside it. Supply the operation’s filtering parameters directly in queryParams, as explained in the additional documentation.

View raw JSON

{
  "type": "object",
  "required": [],
  "properties": {
    "queryParams": {
      "type": "object",
      "properties": {
        "query": {
          "type": "object",
          "required": [],
          "properties": {}
        }
      }
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

Market selection and filters

The Predexon wallet-filter reference describes filtering wallets that traded selected markets. Supply 1–10 full condition IDs as the comma-separated markets value directly in queryParams. An empty market selection is not a usable filter request.

The supplier documents market_logic=and for trading every selected market and or for at least one; the default is and. Documented metric windows are 1d, 7d, 30d and all_time, with all_time as the default. These windows describe the statistics, not when the source last refreshed its data.

Predexon also documents sorting and metric thresholds, subject to supplier support for the requested configuration. The documented default is total_pnl in descending order; limit is 1–100, default 100. Ask for a supported combination and retain your intended scope if a requested filter is unavailable. The BlockRun prediction-market reference describes the gateway operation.

Reading the wallet records

Each entry identifies a wallet through user; rank is its one-based position in the returned results, and markets_matched counts the selected markets it traded. The metrics values are combined across the selected markets, not the wallet’s entire portfolio.

realized_pnl is closed-position profit or loss in USD. total_pnl is realized plus unrealized profit or loss minus net fees, in USD; volume is trading volume in USD. trades counts trades. wins and losses count winning and losing closed positions; positions_closed counts all closed positions.

roi and win_rate are decimal ratios: for example, a win rate of 0.6 represents 60%. Keep the original values when formatting rates. profit_factor is the supplier’s gross-profit/gross-loss measure; retain its returned value rather than replacing it with a recalculated value. avg_buy_price and avg_sell_price are volume-weighted prices on a 0–1 scale, while entry_edge is average sell price minus average buy price. Preserve null as unavailable, separate from numeric zero.

Page scope

The response’s pagination.count is the number of records in that page. has_more indicates whether the supplier reports another page, and pagination_key is an opaque continuation cursor to retain unchanged. A first page does not count all wallets in the source.

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

This operation requires the full Polymarket condition IDs for the selected markets. A market name alone does not provide those identifiers; supply the IDs for 1–10 markets before filtering.

Filter Polymarket Wallets by Market | BlockRun

Filter Polymarket Wallets by Market | BlockRun

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Market selection and filters

Reading the wallet records

Page scope

Connect your Agent

Provide the selected markets

Read the selected-market statistics

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Market selection and filters

Reading the wallet records

Page scope

Connect your Agent

Provide the selected markets

Read the selected-market statistics

Questions about this tool.

Can I provide market names instead of condition IDs?