Nansen Prediction Markets
- 411 installs
- 127 repo stars
- Updated August 4, 2026
- nansen-ai/nansen-cli
nansen-prediction-markets is an agent skill that exposes Nansen CLI Polymarket screeners so developers can discover trending events, rank markets by volume and liquidity, and search contract questions from structured JSO
About
nansen-prediction-markets is a Claude Code and OpenClaw agent skill bundled in the nansen-ai/nansen-cli repository that wraps three Nansen CLI Polymarket screener commands for Polygon-based Polymarket data. Developers install the npm package nansen-cli, set NANSEN_API_KEY, and run nansen research pm with event-screener, market-screener, or categories subcommands to pull JSON rows for event titles, market questions, best bid/ask, 24-hour volume, liquidity, open interest, and unique traders. The skill documents eight sort fields—including volume_24hr, liquidity, open_interest, and unique_traders_24h—and supports --query text search plus --status closed for resolved markets. Reach for nansen-prediction-markets when you need programmatic market discovery before deeper wallet or orderbook analysis with sibling nansen-cli skills.
- Prediction market data
- Event odds research
- Participant flows
- Nansen CLI
Nansen Prediction Markets by the numbers
- 411 all-time installs (skills.sh)
- +5 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #238 of 1,106 Finance & Trading 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-prediction-marketsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 411 |
|---|---|
| repo stars | ★ 127 |
| Last updated | August 4, 2026 |
| Repository | nansen-ai/nansen-cli ↗ |
How do you screen Polymarket events by volume from CLI?
Analyze prediction-market contracts and participant behavior with Nansen CLI to research event odds, liquidity, and positioning ahead of trades or product bets.
Who is it for?
Developers building agent workflows or trading research pipelines who need fast Polymarket discovery without opening the Polymarket UI.
Skip if: Developers who need orderbook depth, wallet PnL, or holder analysis should use nansen-polymarket-deep-dive instead of these screeners alone.
When should I use this skill?
User asks to browse trending Polymarket events, rank prediction markets by 24h volume or liquidity, search market questions, or list categories before a trade or research step.
What you get
JSON screener tables listing Polymarket events, markets, category stats, bids, asks, volume, liquidity, and open interest.
- Polymarket event screener JSON
- market screener JSON
- category volume summaries
By the numbers
- Documents 3 Polymarket screener subcommands: event-screener, market-screener, and categories
- Supports 8 sort-by fields including volume_24hr, liquidity, open_interest, and unique_traders_24h
- Installs the nansen-cli npm package and requires NANSEN_API_KEY
Files
Prediction Market Screeners
All commands: nansen research prediction-market <sub> [options] (alias: nansen research pm <sub>)
No --chain flag needed — Polymarket runs on Polygon.
# Top events (groups of related markets)
nansen research pm event-screener --sort-by volume_24hr --limit 20
# → event_title, market_count, total_volume, total_volume_24hr, total_liquidity, total_open_interest, tags
# Top markets by 24h volume
nansen research pm market-screener --sort-by volume_24hr --limit 20
# → market_id, question, best_bid, best_ask, volume_24hr, liquidity, open_interest, unique_traders_24h
# Search for specific markets
nansen research pm market-screener --query "bitcoin" --limit 10
# Find resolved/closed markets
nansen research pm market-screener --status closed --limit 10
# Browse categories
nansen research pm categories --pretty
# → category, active_markets, total_volume_24hr, total_open_interestSort options: volume_24hr, volume, volume_1wk, volume_1mo, liquidity, open_interest, unique_traders_24h, age_hours
Screeners return active/open markets by default. Use --status closed for resolved markets.
Related skills
Wind Mcp SkillGive their AI coding agent instant access to comprehensive Chinese and global equity, fund, bond, and macroeconomic data from Wind.63.5k71
Upgrade StripeSafely upgrade their Stripe API version and SDKs without introducing breaking changes.53.1k1.7k
Recipe Create Expense TrackerInstantly create a ready-to-use Google Sheets expense tracker with headers, sample data, and sharing permissions.24.1k30.1k
Backtesting FrameworksCreate realistic event-driven backtesters that simulate order execution, slippage, commissions, and position tracking before committing capital to a trading strategy.13.3k38.4k
Grimoire PolymarketQuery live Polymarket odds, search events, and manage conditional order flow directly from Claude or Cursor without leaving the IDE.11.9k6
CoinglassGive their AI coding agents real-time access to crypto derivatives market data such as funding rates, open interest, long/short ratios, liquidations, and futures OHLC h11.3k21How it compares
Pick nansen-prediction-markets for high-level Polymarket discovery and volume ranking; switch to deeper nansen-cli Polymarket skills when you need orderbooks, holders, or wallet PnL.
FAQ
What commands does nansen-prediction-markets expose?
nansen-prediction-markets documents three Nansen CLI subcommands under nansen research pm: event-screener for grouped events, market-screener for individual contracts, and categories for topic-level volume and open-interest totals on Polymarket.
Does nansen-prediction-markets need a chain flag?
nansen-prediction-markets targets Polymarket on Polygon only, so nansen research pm commands omit --chain. Developers pass sort, limit, query, and status flags instead of selecting an EVM network.
What setup does nansen-prediction-markets require?
nansen-prediction-markets requires the global nansen-cli npm binary, a NANSEN_API_KEY environment variable, and agent Bash access scoped to nansen:* commands so screeners can return structured JSON from the Nansen API.