Prediction Market Exchanges
Access supported prediction market exchanges. Get exchange identifiers, venue descriptions, and official website details.
Access standardized prediction market data from leading centralized and decentralized prediction market exchanges through one unified API. Retrieve markets, trades, quotes, order books, OHLCV candles, and historical datasets using consistent schemas designed for trading systems, analytics platforms, AI applications, and quantitative research.
The FinFeedAPI Prediction Markets API normalizes data across multiple prediction market venues, eliminating the need to integrate different APIs, naming conventions, market identifiers, and data formats.
Access supported prediction market exchanges. Get exchange identifiers, venue descriptions, and official website details.
Retrieve full market records by exchange, including market IDs, titles, descriptions, outcome names, prices, status, exchange IDs, and outcome types.
Get compact lists of currently active market IDs for each exchange. This is useful when you need fast discovery before requesting full market details.
Access the latest trade and latest quote for a specific market outcome. Use this data to monitor current price movement, bid/ask levels, and recent activity.
Retrieve recent batches of trades and quotes for a market. This helps analyze short-term activity, liquidity changes, and market movement.
Pull historical trade and quote data from flat files using a full-day date query or a bounded time range. Data is filtered by processing time and includes exchange event timing.
Retrieve open, high, low, close, volume, and trade count data for prediction markets. Historical OHLCV data is returned in ascending time order for backtesting and analysis.
Access the most recent OHLCV candles for a specific market and period. Supported periods range from seconds and minutes to hours, days, months, and years.
Get current order book snapshots with bids and asks for a specific market outcome to analyze live liquidity, spreads, market depth, and top-of-book imbalance.
Retrieve raw historical limit order events (adds, updates, deletes) from flat files for custom order book reconstruction and market-replay analysis.
The Prediction Markets API brings together leading regulated, decentralized, and social prediction market exchanges through one standardized interface. Instead of integrating each venue separately, developers can discover markets, monitor liquidity, and retrieve historical data across multiple ecosystems using consistent identifiers, timestamps, and schemas.
| Exchange Type | Examples |
|---|---|
| Regulated Exchanges | Kalshi, ForecastEx, Crypto.com, Gemini |
| Decentralized Prediction Markets | Polymarket, Myriad, Pascal |
| Social Prediction Markets | Manifold |
| On-Chain Outcome Markets | Hyperliquid Outcome Markets |
Most prediction market APIs expose prices. FinFeedAPI exposes the entire market. Each market can be explored from discovery to execution-quality analysis through a single API.
Instead of stitching together multiple endpoints from different exchanges, every stage of the market lifecycle is available through one standardized data model.
The Prediction Markets API is available through a hosted Model Context Protocol (MCP) server, allowing AI assistants and autonomous applications to discover exchanges, inspect markets, retrieve activity, analyze order books, and request historical data using self-describing tools. Rather than manually navigating API documentation, AI applications can identify available exchanges, enumerate active markets, retrieve market metadata, and query market activity through standardized MCP tools.
{
"mcpServers": {
"FinFeedAPI-Prediction-Markets": {
"url": "https://api.prediction-markets.finfeedapi.com/mcp",
"headers": {
"X-APIKey": "YOUR_API_KEY_HERE"
}
}
}
}Compatible with Cursor, Claude Desktop, and other MCP-enabled AI applications.
Choose the interface that best fits your application architecture. Every interface exposes the same standardized prediction market datasets, allowing teams to adopt the protocol that best matches their infrastructure.
| Interface | Authentication Header | Best For |
|---|---|---|
| REST API | Authorization: YOUR_API_KEY | Trading systems, dashboards, analytics, and production applications |
| JSON-RPC API | Authorization: YOUR_API_KEY | Applications that prefer RPC-style integrations while accessing the same datasets |
| Hosted MCP Server | X-APIKey: YOUR_API_KEY | AI assistants, coding agents, research tools, and autonomous workflows |
Built for production-grade prediction market applications:
Consistent schemas across supported exchanges.
Stable market IDs and outcome identifiers.
Consistent time handling across all endpoints.
Access live market state (snapshots, current quotes) and historical flat files.
REST, JSON-RPC, and MCP interfaces.
Encrypted TLS/SSL endpoints with API key authentication.
Standardized decimal handling across market data (up to 19 digits with 9 decimal places).
Prediction market exchanges continue to grow, but every venue exposes different APIs, market identifiers, response formats, and capabilities. Building direct integrations means maintaining separate implementations as exchanges evolve. FinFeedAPI provides one normalized interface across supported prediction market exchanges.
| Feature | Direct Exchange APIs | FinFeedAPI Prediction Markets API |
|---|---|---|
| Exchange Integrations | One exchange at a time | Multiple exchanges through one API |
| Market Discovery | Different endpoints | Standardized discovery workflow (/active & /history) |
| Trades & Quotes | Exchange-specific formats | Unified schemas |
| Order Books | Different implementations | Live snapshots & standardized historical event logs |
| OHLCV Data | Varies by venue | Standardized time series (seconds to years) |
| Historical Data | Different retrieval methods | Bounded S3 flat-file historical access |
| AI Integration | Typically unavailable | Hosted MCP server (/mcp) |
| Engineering Maintenance | Multiple integrations | One integration |
Start retrieving prediction market data in minutes.
The documentation includes implementation examples for REST, JSON-RPC, official SDKs (Python, Node.js, Go, C#, etc.), and MCP clients.
Retrieve the latest market activity:
curl -X GET \
"https://api.prediction-markets.finfeedapi.com/v1/activity/POLYMARKET/WILL-TRUMP-SELL-10K-25K-GOLD-CARDS-IN-2025_YES/current" \
-H "Authorization: YOUR_API_KEY"The response includes the latest trade together with the latest bid and ask for the selected prediction market.
Prediction markets have expanded rapidly across regulated exchanges, decentralized protocols, and specialized event markets.
Each platform defines its own market identifiers, naming conventions, metadata, endpoints, and market structures. Even simple tasks like discovering active markets or retrieving historical trading activity require different implementations for every exchange.
The Prediction Markets API removes this complexity by normalizing exchanges into one consistent platform.
Instead of maintaining multiple integrations, developers can access standardized market metadata, trades, quotes, order books, OHLCV data, and historical market activity through a single API designed specifically for prediction markets.
Build applications on top of prediction markets instead of building infrastructure around them.
Access standardized prediction market data from multiple exchanges through one API designed for trading systems, analytics platforms, AI applications, and quantitative research. Retrieve live market activity, historical datasets, order books, OHLCV time series, and market metadata through a single, consistent integration.