Use market clusters when you want the same tradeable question across venues. A cluster contains every matched market PMXT currently knows about for that question, plus the pairwise relations used to connect the cluster. You can anchor the lookup to a market you already have, or omit the anchor fields to browse clusters across the catalog.Documentation Index
Fetch the complete documentation index at: https://pmxt-feat-series-api.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
fetchMatchedMarketClusters
- Python
- TypeScript
- curl
Passing an existing market
If the market came fromfetchMarkets, pass it directly.
- Python
- TypeScript
Browsing clusters
OmitmarketId, slug, and url to browse the highest-volume matched
clusters.
- Python
- TypeScript
Parameters
| Parameter | Type | Default | Notes |
|---|---|---|---|
marketId | string | - | Anchor to a PMXT market ID. |
slug | string | - | Anchor to a market slug. |
url | string | - | Anchor to a venue market URL. |
relation | string | - | Filter to one relation type. |
relations | string or string[] | - | Filter to multiple relation types. |
minConfidence / min_confidence | number | 0 | Minimum cluster edge confidence, from 0 to 1. |
venues | string or string[] | - | Only include clusters touching these venues. |
excludeVenues / exclude_venues | string or string[] | - | Exclude clusters touching these venues. |
minVenues / min_venues | integer | - | Require at least this many venues in a cluster. |
withOrderbook / with_orderbook | boolean | false | Require live orderbook coverage on matched edges. |
includeRawMatches / include_raw_matches | boolean | false | Include pairwise edges used to build the cluster. |
updatedSince / updated_since | datetime | - | Only include matches updated after this time. |
sort | "volume" or "confidence" | "volume" | Cluster sort order. |
limit | integer | 50 | Maximum clusters to return. |
offset | integer | 0 | Pagination offset. |
edgeLimit / edge_limit | integer | - | Maximum pairwise edges to scan before clustering. |
Response shape
Relation Types
Every edge in a cluster is classified into one of five set-theoretic relations describing how two markets’ resolution conditions relate.| Relation | Meaning | Example |
|---|---|---|
identity | Same resolution condition. | ”BTC > $100k by Dec 31” on Polymarket and Kalshi. |
subset | A resolving YES implies the other resolves YES, not vice versa. | ”Democrats win presidency” is narrower than “Democrats win popular vote”. |
superset | The reverse of subset. | ”Democrats win popular vote” is broader than “Democrats win presidency”. |
overlap | Related, but neither condition implies the other. | ”Fed cuts in June” and “Fed cuts twice in 2026”. |
disjoint | Cannot both resolve YES. | Two mutually exclusive candidates winning the same office. |
To match an entire event and see the corresponding child markets, use
Find Similar Events.

