Skip to content
Developer APIMCP available

Build on prediction market intelligence.

7 API endpoints for the questions agents actually ask: trader quality, whale flow, market discovery, smart-money direction, and suspicious activity signals.

  • Trader grades and strategy context
  • Whale trades and market discovery
  • Smart-money direction and insider-risk signals
Quick start

Start with one request, then branch into deeper tools.

Example requestbash
curl -H "Authorization: Bearer oxi_sk_live_..." \
  https://api.0xinsider.com/api/v1/whale-trades?min_grade=S&limit=5
What the developer layer is for

A cleaner interface for trading systems, research tools, and AI agents.

  • Ask whether a trader deserves attention before you react to their flow.
  • Discover which markets actually have quality capital behind them.
  • Pull structured outputs into bots, reports, or your own internal tooling without scraping the product UI.
7
public REST endpoints on the page today
OpenAPI
machine-readable contract for generated clients
MCP
agent-friendly entry point for tool-based workflows
Why use it

Your system is only as good as the context attached to the trade.

Most bots can see the print. The useful edge is understanding who placed it, how credible that trader is, and whether the broader pattern deserves attention.

Raw trade feed

A large trade happened on some market.

Noise
Sized trade feed

A $47K trade happened on the Bitcoin $100K market.

Data
0xinsider API

An S-grade trader with a strong historical profile just built size on the same market, aligned with other quality accounts, and no suspicious-pattern flags are attached to the move.

Intelligence
7 endpoints

Questions agents ask, answered.

Each endpoint is designed around an analytical question, not a raw table dump. Full reference in the docs.

get_trader
Should I trust this trader?

Grade (S-F), ML-detected strategy, P&L breakdown, win rate, and per-category strengths. Expand heavy fields on demand.

GET /api/v1/trader/{address}
get_whale_trades
What big moves are happening?

Large trades with 0-1 signal scoring. Filter by size, category, trader grade, or side. Category falls back to stored market metadata if inferred_category is not backfilled yet. Cursor pagination for polling.

GET /api/v1/whale-trades
explore_markets
What markets deserve attention?

Browse whale-active titled markets by category, platform, status, or sort order. Returns grouped event rows for discovery surfaces.

GET /api/v1/markets/explore
get_market_intel
Where's the smart money?

Net money flow direction, top trader positions, whale trade count, and buy/sell volumes for any market.

GET /api/v1/market/{condition_id}/intel
get_leaderboard
Who are the best traders?

Top traders ranked by grade, P&L, volume, or win rate. Filter by category or ML-detected strategy type.

GET /api/v1/leaderboard
search_markets
Find markets about X

Keyword search across all prediction markets. Returns representative matches with status, category, platform, and cursor pagination.

GET /api/v1/markets/search
get_insider_radar
What looks suspicious?

Coordinated wallets, pre-resolution accumulation, and suspicious timing patterns. Unique to 0xinsider.

GET /api/v1/insider-radar
MCP Server

Works with Claude Code, Cursor, Codex, Gemini CLI, and other MCP clients.

Ask your assistant about prediction markets and let it query 0xinsider directly. The setup command detects local Claude Code or Cursor configs, plus installed Codex or Gemini CLI clients. Other clients can use the manual config from the docs.

Install
npx -y @0xinsider/mcp init

Detects local Claude Code or Cursor configs, plus installed Codex or Gemini CLI clients.

Example prompts

"What are the S-grade traders buying in crypto right now?"

get_leaderboard -> get_whale_trades

"Analyze this trader's strategy and recent performance"

get_trader -> get_whale_trades

"Is there insider activity on the Bitcoin $100K market?"

get_market_intel -> get_insider_radar
What you get

Intelligence on every trade.

Structured context for agents, dashboards, and research flows. The response stays compact, but each trade carries enough metadata to rank, filter, and act on quickly.

Built for technical buyers who need signal density, not a generic event feed.

Signal layer

Signal scoring

Every whale trade gets a 0-1 significance score based on trader grade, size, timing, and market context.

  • grade-aware
  • size-aware
  • timing-aware
  • market context
Quality layer

Trader grades

S through F grades from win rate, volume, edge consistency, and 40+ quant metrics. Updated daily.

  • S-F scale
  • 40+ metrics
  • edge consistency
  • daily refresh
Strategy layer

Strategy detection

ML classifies each trader as arbitrageur, momentum, market maker, or directional, with confidence scores attached.

  • ML classification
  • confidence scores
  • arbitrageur
  • directional
Risk layer

Insider radar

Coordinated wallets, pre-resolution accumulation, suspicious timing, and other patterns that deserve a second look.

  • wallet clusters
  • timing flags
  • pre-resolution buildup
  • pattern alerts
Delivery layer

Cursor pagination

Composite timestamp plus ID cursors keep polling clients from skipping records during high activity.

  • timestamp + ID
  • no skipped rows
  • batch-safe
  • agent polling
Control layer

Expandable fields

Use `expand[]=strategy` and similar parameters when you want heavier context without paying the latency cost by default.

  • expand[]=strategy
  • depth on demand
  • low-latency default
  • heavy fields optional
Coming next

More delivery surfaces are planned beyond the current REST and MCP layer.

CLI

Query 0xinsider from your terminal, pipe results into scripts, and automate exports or alerts without opening the app.

Soon

WebSocket streaming

Real-time whale-trade streaming for trading bots, monitoring systems, and live dashboards that need lower-latency delivery.

Soon

Webhooks

Push notifications for tracked traders, conditions, or suspicious patterns instead of polling every workflow manually.

Soon
Developer Docs

Use the docs when you want the full contract, examples, and setup path.

The reference covers request parameters, response shapes, MCP installation, and the integration patterns behind the public developer surface.