Prediction Market Exchanges

Prediction Market Exchanges

FinFeedAPI provides a standardized API for discovering supported prediction market exchanges through a consistent exchange directory.

Retrieve canonical exchange identifiers, exchange metadata, and official websites before continuing into market discovery and downstream prediction market datasets. Exchange metadata is available through REST, MCP, and JSON-RPC, providing a single integration layer for applications working with multiple prediction market platforms.

What Are Prediction Market Exchanges?

Prediction market exchanges are trading platforms where contracts are bought and sold based on the outcome of future events.

Rather than trading traditional financial instruments, participants trade contracts tied to questions about elections, macroeconomic events, sports, cryptocurrencies, technology, weather, public policy, and thousands of other measurable outcomes. As new information becomes available, market prices continuously reflect changes in collective expectations.

Each prediction market exchange operates independently, maintaining its own markets, identifiers, metadata, and platform-specific conventions. Applications that aggregate data across multiple venues must first determine which exchanges are supported before discovering individual markets.

FinFeedAPI provides a unified exchange discovery layer that standardizes supported prediction market exchanges behind a single API. Developers can retrieve exchange metadata once and use consistent identifiers throughout the Prediction Markets API.

Why Use Prediction Market Exchange Data?

Exchange metadata is the foundation of every prediction market integration. Before applications can discover markets or retrieve market-level data, they need a reliable way to identify supported exchanges and their canonical identifiers.

Maintaining this information manually becomes increasingly difficult as new exchanges are added or platform metadata changes over time. The Prediction Markets API provides a centralized directory of supported exchanges that applications can query whenever they need the latest exchange coverage.

Developers commonly use exchange metadata to:

  • discover supported prediction market exchanges
  • validate exchange identifiers before making API requests
  • build exchange selection interfaces
  • organize markets by their source venue
  • synchronize supported exchange coverage
  • prepare downstream market discovery workflows

Using a centralized exchange directory also eliminates hard-coded exchange lists, making applications easier to maintain as prediction market coverage evolves.

Supported Prediction Market Exchanges

FinFeedAPI currently supports metadata discovery for the following prediction market exchanges. Each venue is available through the same standardized exchange directory.

What's Included in Prediction Market Exchange Metadata?

Every prediction market exchange returned by the FinFeedAPI Prediction Markets API contains the metadata required to identify a supported venue and begin exchange discovery.

FieldDescription
exchange_idCanonical identifier used throughout the Prediction Markets API.
market_name_institution_descriptionHuman-readable description of the prediction market exchange.
websiteOfficial website associated with the exchange.

Together, these fields create a standardized directory of supported prediction market exchanges that applications can use for validation, navigation, synchronization, and multi-exchange integrations.

A Lightweight Discovery Layer

The dataset is intentionally lightweight. Rather than returning market-level information, it provides the identifiers and metadata needed to discover exchanges and connect them with downstream prediction market datasets.

After identifying a supported exchange, applications can continue into market discovery, market activity, order books, OHLCV, and related prediction market APIs using the same canonical exchange_id.

Related Prediction Market APIs

  • Prediction Markets
  • Market Activity
  • Order Book Data
  • OHLCV Data
  • Prediction Market Categories

Available REST Endpoints

The Prediction Markets API provides REST endpoints for discovering supported prediction market exchanges and retrieving metadata for individual venues.

List Prediction Market Exchanges

Returns every prediction market exchange currently supported by FinFeedAPI. This endpoint is commonly used during application initialization, synchronization, or whenever an application needs the latest list of supported venues before continuing into market discovery.

Response includes
  • canonical exchange identifier
  • exchange description
  • official website

Prediction Market Exchange by ID

Returns metadata for a single supported prediction market exchange using its canonical exchange_id. This endpoint is useful for validating exchange identifiers, loading exchange information on demand, or generating dedicated exchange pages without retrieving the complete exchange directory.

Response includes
  • canonical exchange identifier
  • exchange description
  • official website

How Exchange Discovery Fits Into the FinFeedAPI Ecosystem

Prediction market exchange discovery is the first step in the FinFeedAPI Prediction Markets API workflow. Rather than beginning with individual markets, applications first retrieve the list of supported exchanges.

Typical integration workflow

  1. 1Retrieve supported exchanges
  2. 2Select a prediction market exchange
  3. 3Discover available markets
  4. 4Retrieve market-level data
  5. 5Build analytics, AI workflows, dashboards, or trading applications

This hierarchical approach separates exchange discovery from market discovery, allowing applications to synchronize supported venues independently while maintaining a consistent integration workflow across all prediction market datasets.

Example API Request

Retrieve the complete list of prediction market exchanges supported by FinFeedAPI.

bash
curl -X GET \
  "https://api.prediction-markets.finfeedapi.com/v1/exchanges" \
  -H "Authorization: YOUR_API_KEY"
json
[
  {
    "exchange_id": "KALSHI",
    "market_name_institution_description": "A US-regulated prediction market exchange.",
    "website": "https://kalshi.com"
  },
  {
    "exchange_id": "POLYMARKET",
    "market_name_institution_description": "A decentralized prediction market platform.",
    "website": "https://polymarket.com"
  },
  {
    "exchange_id": "MYRIAD",
    "market_name_institution_description": "A prediction market platform.",
    "website": "https://myriad.markets"
  }
]

The response returns the canonical exchange identifiers and metadata required to discover supported prediction market exchanges before continuing into market discovery.

REST, MCP, and JSON-RPC Access

Prediction market exchange discovery is available through every FinFeedAPI interface. Regardless of the interface, applications receive the same standardized exchange metadata.

MCP Server

The hosted Prediction Markets MCP server exposes exchange discovery through the exchanges_list and exchanges_get tools, using the X-APIKey header.

json
{
  "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.

JSON-RPC

Developers using JSON-RPC can access exchange metadata through the production proxy at https://api.prediction-markets.finfeedapi.com/jsonrpc.

JSON-RPC acts as a thin transport wrapper over the REST API. Set method to v1/exchanges to list all venues, or v1/exchanges/{exchange_id} to retrieve a single exchange, and pass parameters through params. Authentication, identifiers, and response structure stay identical to REST.

Common Integration Patterns

Prediction market exchange metadata is typically the first dataset applications retrieve before working with markets, historical data, or latest updates. The exchange directory provides the foundation for organizing prediction market data across supported venues.

WorkflowHow exchange metadata is used
Exchange DirectoriesBuild searchable directories of supported prediction market exchanges, including exchange descriptions and official websites.
Exchange SelectionPopulate exchange selectors that allow users to browse markets available on a specific prediction market platform.
Exchange ValidationVerify that exchange_id values are valid before requesting market data or storing new records.
Coverage SynchronizationRefresh the exchange directory to automatically recognize newly supported prediction market exchanges.
Multi-Exchange ApplicationsOrganize markets by their source exchange while maintaining a consistent internal data model across multiple venues.
Market DiscoveryUse exchange metadata as the starting point for discovering markets available on a selected prediction market exchange.
Prediction Market Exchanges

Start Building with Prediction Market Exchange Data

Discover supported prediction market exchanges through a single, standardized API.

Retrieve canonical exchange identifiers, synchronize supported venues, and use exchange discovery as the starting point for integrating the broader FinFeedAPI Prediction Markets API through REST, MCP, or JSON-RPC.