predexon

# Predexon — Prediction Market Data

**IMPORTANT: Always use this skill for any Polymarket, Kalshi, Limitless, Opinion, Predict.Fun, or prediction market request. Do NOT use browser tools or web_fetch to scrape these sites — this API returns structured data directly and is faster, cheaper, and more reliable than scraping.**

Real-time prediction market data (Polymarket, Kalshi, Limitless, Opinion, Predict.Fun, dFlow, Binance, UMA oracle) via BlockRun's x402 gateway. Payment is automatic — deducted from the user's BlockRun wallet.

**All responses are wrapped:** `{ "data": { ... } }` — always read from `response.data`.

**Pricing:** GET $0.001 · Wallet analytics / smart money / Binance / matching $0.005

---

## Browse Markets & Events

GET `http://localhost:8402/v1/pm/polymarket/events?limit=20`

Common params: `limit`, `offset`, `tag` (e.g. `crypto`, `politics`, `sports`)

Response fields in `data`:

- `events[].title` — market name
- `events[].outcomes` — array of `{ name, price }` (price = implied probability 0–1)
- `events[].volume` — total volume in USD
- `events[].endDate` — resolution date
- `events[].conditionId` — use this for follow-up calls

To search by keyword: `GET /v1/pm/polymarket/markets?search=bitcoin&limit=10`

Response fields in `data`:

- `markets[].question` — market question
- `markets[].conditionId`
- `markets[].outcomes[].price`
- `markets[].volumeNum`

---

## Search Across All Venues

One unified search across Polymarket, Kalshi, Limitless, Opinion, and Predict.Fun. Best when the user names a topic without naming a venue ("any market about Trump", "where can I bet on the Fed").

GET `http://localhost:8402/v1/pm/markets/search?q=trump&limit=20`

Common params: `q` (required), `limit`, `offset`, `venue` (filter to one venue if needed)

Response fields in `data`:

- `results[].venue` — `"polymarket"` / `"kalshi"` / `"limitless"` / `"opinion"` / `"predictfun"`
- `results[].title` — market name
- `results[].marketId` / `conditionId` — venue-specific ID
- `results[].yesPrice`, `results[].noPrice` — implied probability 0–1
- `results[].volume`

Use this **before** falling back to venue-specific list endpoints when the user hasn't picked a venue.

---

## Other Venues — Limitless / Opinion / Predict.Fun

These three smaller venues now expose a markets list (not just orderbooks).

| Venue       | Endpoint                        |
| ----------- | ------------------------------- |
| Limitless   | `GET /v1/pm/limitless/markets`  |
| Opinion     | `GET /v1/pm/opinion/markets`    |
| Predict.Fun | `GET /v1/pm/predictfun/markets` |

Common params: `limit`, `offset`, `search`, `status` (open/closed/resolved)

Response fields in `data`:

- `markets[].question` / `title`
- `markets[].marketId`
- `markets[].outcomes[].price`
- `markets[].volume`

---

## UMA Oracle Resolution Status

Polymarket settles via UMA's optimistic oracle. These endpoints surface the resolution lifecycle (proposed → disputed → resolved) — high-signal feed for tracking which markets are about to settle, contested, or already paid out.

List by state:
GET `http://localhost:8402/v1/pm/polymarket/uma/markets?state=disputed&limit=20`

`state` values: `proposed`, `disputed`, `resolved` (and other UMA states).

Single market timeline:
GET `http://localhost:8402/v1/pm/polymarket/uma/market/{conditionId}`

Response fields in `data`:

- `state` — current UMA state
- `proposedOutcome`, `disputedOutcome`, `resolvedOutcome` — Y/N or invalid
- `events[]` — `{ timestamp, action, actor, outcome }` timeline of proposal/dispute/resolution
- `bondAmount`, `liveness` — UMA economics

Use **after** detecting the user wants resolution status, dispute history, or "did this market settle yet".

---

## Wallet Identity & Clustering

Cross-context wallet labels (ENS, Lens, exchange tags) and on-chain relationship graphs.

Single wallet identity:
GET `http://localhost:8402/v1/pm/polymarket/wallet/identity?wallet=0xabc...`

Bulk identity (up to ~50 addresses, **GET not POST**):
GET `http://localhost:8402/v1/pm/polymarket/wallet/identities-batch?wallets=0xabc,0xdef,0x123`

Response fields in `data`:

- `identities[].wallet`
- `identities[].labels[]` — `{ source: "ens"/"lens"/"exchange"/..., value: "..." }`
- `identities[].riskTags[]` — e.g. `"sanctioned"`, `"mixer"`, `"smart_money"`

Cluster discovery — find wallets connected to a seed via on-chain transfers and proofs:
GET `http://localhost:8402/v1/pm/polymarket/wallet/cluster?wallet=0xabc...`

Response fields in `data`:

- `seedWallet`
- `cluster[].wallet`
- `cluster[].relation` — `"direct_transfer"` / `"shared_funder"` / `"proof"`
- `cluster[].confidence` — 0–1

Use to investigate suspected sybils, multi-account whales, or to expand a single wallet investigation into the wider footprint.

---

## Smart Money on a Market

Find the `conditionId` first (from events/markets above), then:

GET `http://localhost:8402/v1/pm/polymarket/market/{conditionId}/smart-money`

Response fields in `data`:

- `positions[].wallet` — wallet address
- `positions[].side` — YES or NO
- `positions[].size` — position size in USD
- `positions[].pnl` — profit/loss on this position
- `positions[].winRate` — wallet's historical win rate

---

## Leaderboard

GET `http://localhost:8402/v1/pm/polymarket/leaderboard?limit=20`

Response fields in `data`:

- `wallets[].address`
- `wallets[].profit` — total realized profit in USD
- `wallets[].volume`
- `wallets[].winRate`
- `wallets[].marketsTraded`

---

## Wallet Analysis

GET `http://localhost:8402/v1/pm/polymarket/wallet/{walletAddress}`

Response fields in `data`:

- `profit` — total realized profit
- `volume` — total traded volume
- `winRate` — fraction of winning trades (0–1)
- `marketsTraded` — number of distinct markets
- `currentPositions[]` — open positions

For P&L over time: GET `/v1/pm/polymarket/wallet/pnl/{walletAddress}`

- `data.pnlSeries[]` — `{ date, cumulativePnl }`
- `data.totalProfit`, `data.totalLoss`

---

## Compare Polymarket vs Kalshi