Nansen Polymarket Insider Scan
- 347 installs
- 127 repo stars
- Updated August 4, 2026
- nansen-ai/nansen-cli
nansen-polymarket-insider-scan is an AI agent skill for the Nansen CLI that scores top Polymarket winners for insider-like wallet patterns after a market resolves.
About
nansen-polymarket-insider-scan is an agent skill in nansen-ai/nansen-cli that scans resolved Polymarket prediction markets for wallets exhibiting insider-like trading behavior. The workflow calls Nansen CLI commands—market-screener for closed markets, pnl-by-market for top winners, then per-wallet trades-by-address, 365-day historical-balances on Polygon, and profiler labels—to compute a 0–13 suspicion score across eight flags including new or young wallets, single-market focus, extreme ROI (500%+), high ROI (200–499%), late entries at prices ≥0.80, large $10k+ positions, and known entities (−2). Wallets flag at score ≥3, mark high risk at ≥7, and signal high-confidence patterns at ≥9. Developers reach for this skill after controversial market resolutions when they need repeatable on-chain evidence instead of manually cross-referencing dozens of wallets. Requires NANSEN_API_KEY and the nansen npm package with Bash(nansen:*) access.
- Polymarket surveillance
- Insider pattern flags
- Wallet anomaly alerts
- Nansen CLI queries
- Prediction market intel
Nansen Polymarket Insider Scan by the numbers
- 347 all-time installs (skills.sh)
- +3 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #57 of 479 Web3 & Blockchain skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nansen-ai/nansen-cli --skill nansen-polymarket-insider-scanAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 347 |
|---|---|
| repo stars | ★ 127 |
| Last updated | August 4, 2026 |
| Repository | nansen-ai/nansen-cli ↗ |
How do you detect insider trading on Polymarket?
Monitor Polymarket for suspicious insider-like wallet activity, large pre-news positioning, and unusual flow patterns that may signal informed trading.
Who is it for?
Developers and quant engineers investigating resolved Polymarket markets who already use Nansen CLI and need automated insider-pattern scoring across top winners.
Skip if: Developers seeking live pre-resolution trade alerts or execution bots, since the skill only scans closed markets with resolved outcomes.
When should I use this skill?
A resolved Polymarket market shows controversial outcomes or extreme winner PnL and the developer needs wallet-level suspicion scoring via Nansen CLI.
What you get
Risk-scored wallet list with eight suspicion flags, PnL metrics, Polygon funding dates, Nansen profiler labels, and flagged or high-risk tiers per market.
- tiered risk-scored wallet report
- per-wallet suspicion flag breakdown
- PnL and profiler label context per winner
By the numbers
- Scores wallets 0–13 using 8 suspicion flags
- Profiles wallet funding history over a 365-day Polygon window
- Flags suspicious wallets at score ≥3 and high risk at ≥7
Files
PM Suspicious Wallet Scanner
Answers: "Are there wallets with suspicious trading patterns in this Polymarket market?"
# 1. Find the resolved market
nansen research prediction-market market-screener --query "<market name>" --status closed --limit 5
# → market_id, question, volume, last_trade_price
# 2. Get top winners (positive PnL) — paginate if needed, keep per_page <= 10
MID=<market_id>
nansen research prediction-market pnl-by-market --market-id $MID --limit 10
# → address (proxy), owner_address (wallet), side_held, net_buy_cost_usd, total_pnl_usd
# 3. For each top winner, run these three calls (use proxy address for PM, owner for profiler):
PROXY=<address_from_pnl>
nansen research prediction-market trades-by-address --address $PROXY --limit 100
# → market_id, market_question, side, price, size, usdc_value, taker_action, timestamp
OWNER=<owner_address_from_pnl>
nansen research profiler historical-balances --address $OWNER --chain polygon --days 365 --sort block_timestamp:asc --limit 100
# → block_timestamp, value_usd, token_symbol — first non-zero value_usd = wallet funding date
nansen research profiler labels --address $OWNER --chain polygon
# → label, categoryFor each winner, compute ROI = total_pnl_usd / net_buy_cost_usd * 100 (skip ROI flags if net_buy_cost_usd <= 0), then score (0–13). Within each tier group, apply only the highest matching flag:
| Flag | Pts | Trigger |
|---|---|---|
| NEW_WALLET | 3 | First funded within 7 days of now |
| YOUNG_WALLET | 1 | First funded 8–28 days ago (skip if NEW_WALLET fires) |
| SINGLE_MARKET | 3 | trades-by-address shows only 1 distinct market_id |
| FEW_MARKETS | 1 | 2–3 distinct market_ids (skip if SINGLE_MARKET fires) |
| EXTREME_ROI | 3 | ROI >= 500% |
| HIGH_ROI | 2 | ROI 200–499% (skip if EXTREME_ROI fires) |
| LATE_ENTRY | 2 | Any trade on this market at price >= 0.80 |
| LARGE_POSITION | 2 | net_buy_cost_usd >= $10k |
| KNOWN_ENTITY | -2 | Has Nansen labels |
Flagged at score >= 3. High risk at >= 7. High-confidence suspicious pattern: NEW_WALLET + SINGLE_MARKET + EXTREME_ROI (score 9+).
If owner_address is invalid (e.g. "0x"), use the proxy address for profiler calls too. If historical-balances returns no records with value_usd > 0, the wallet may predate the 365-day window — treat wallet age as unknown and skip NEW_WALLET / YOUNG_WALLET flags. Pause ~1.5s between wallets to avoid rate limits. Skip wallets that error and continue scanning.
Related skills
Solidity SecurityCatch and fix critical Solidity vulnerabilities like reentrancy before deploying smart contracts.13k38.4k
Extension Http OutcallsEnable their Internet Computer backend canister to make secure HTTP GET and POST requests to external APIs.10.3k
Okx Dapp DiscoveryCorrectly route Chinese-language DeFi and on-chain queries to the right protocol plugins inside an agent workflow.9.5k315Okx Growth CompetitionGuide users through OKX OnchainOS competition reward status checks, atomic claims, and post-win contact collection via the onchainos CLI.9.1k315Okx Agent Payments ProtocolLet their AI agent create and fulfill on-chain payment links without leaving the coding session.8.7k315
Query Token InfoGive your coding agent a Node CLI to search Binance tokens and pull metadata while you build crypto or DeFi features.6.1k946How it compares
Pick this for post-resolution insider-pattern scoring across many winners; use wallet-profile skills for deep single-address research before or after a scan.
FAQ
What does nansen-polymarket-insider-scan detect?
nansen-polymarket-insider-scan scans resolved Polymarket markets for wallets with suspicious patterns: newly funded accounts, single-market focus, extreme ROI (500%+), late entries at prices ≥0.80, and large $10k+ positions. Each winner receives a 0–13 score and flags at ≥3.
What do you need to run nansen-polymarket-insider-scan?
nansen-polymarket-insider-scan requires the nansen CLI npm package, a NANSEN_API_KEY environment variable, and Bash access to nansen commands. The skill uses prediction-market and profiler endpoints on Polygon chain.
When should you run nansen-polymarket-insider-scan?
Run nansen-polymarket-insider-scan after a Polymarket market closes and resolves, especially when top winners show unusually high PnL. The workflow queries closed markets only and profiles each positive-PnL winner against eight suspicion flags.