Use Predexon API with AI assistants via Model Context Protocol
Drop one config block into Claude Desktop, Cursor, or Codex and your assistant can reason about prediction markets directly — no boilerplate HTTP calls, no SDK plumbing. Try this in Claude after install:
“What’s the smart-money flow on the top 5 Polymarket markets right now, and where are there cross-venue spreads vs Kalshi?”
Claude composes the 42 tools below — list_polymarket_markets, get_polymarket_smart_money, find_matching_markets — to answer in one round-trip. Same key gates the same data you’d get from REST; same plan limits apply.
Building an agent on top of this?Agent Cookbook walks five concrete patterns — research assistant, position monitor, smart-money alerter, copy-trader, arbitrage scout — with system prompts you can paste straight in.
Model Context Protocol (MCP) is the open standard for letting AI assistants call external tools. Predexon ships an MCP server that exposes every relevant Data API endpoint as a typed tool — so models that support MCP (Claude, Cursor, Codex, Cline, VS Code Copilot) can pull live market data, wallet analytics, and smart-money signals without you writing a single fetch call. Example questions that work out of the box:
“What are the top prediction markets by volume?”
“Show me the price history for this market”
“Find matching markets across Polymarket and Kalshi”
Edit your Claude Desktop configuration file:macOS: ~/Library/Application Support/Claude/claude_desktop_config.jsonWindows: %APPDATA%\Claude\claude_desktop_config.json
Cursor supports both global and project-specific MCP configuration.Global (all projects): ~/.cursor/mcp.jsonProject-specific: .cursor/mcp.json in your project root
Verify the connection in Settings > Cursor Settings > MCP. A green dot indicates the server is connected.Cursor MCP Docs
VS Code supports MCP servers through GitHub Copilot.Global: Open your user mcp.json via Command PaletteProject-specific: .vscode/mcp.json in your workspace
Set your API key via the PREDEXON_API_KEY environment variable in your MCP configuration (see the config examples above). The server reads this automatically on startup.As a fallback, you can also pass api_key as a parameter on individual tool calls, but the env var approach is recommended - it keeps your key out of conversation text and works across all tools automatically.