Unified API for Fragmented Prediction Markets

Prediction markets are becoming a retention feature before they become a standalone category. Brokerages, sportsbooks, and crypto exchanges already have users opening their apps to check prices, watch games, or place trades, so adding a yes or no contract around the same events gives them one more reason to keep people in app, generate more transactions, and reuse existing wallets, compliance, and trading infrastructure instead of sending that activity to Kalshi or Polymarket.

• The products are fragmenting by venue and by use case. Kalshi is the regulated U.S. exchange layer, Polymarket is the crypto native global venue, Robinhood launched an in app hub through Kalshi in March 2025, and later moved deeper into exchange infrastructure through a joint venture tied to a CFTC licensed venue.
  1 sacra 2 robinhood 5 sacra 6 robinhood
• Sportsbooks are entering because event contracts look like a natural extension of the sportsbook screen. DraftKings bought Railbird in October 2025 and launched DraftKings Predictions in January 2026, while Fanatics built Fanatics Markets alongside its sportsbook and casino products to turn existing sports traffic into more frequent trading activity.
  3 draftkings 4 draftkings 7 sacra
• This creates the exact integration mess that gave crypto infrastructure companies room to grow. Different venues use different rails, rules, and liquidity pools. Dome sits in that gap, normalizing market data and routing orders across Kalshi style regulated books and Polymarket style crypto books so traders and app builders do not have to wire each venue one by one.
  1 sacra 5 sacra 6 robinhood

The next phase is a market structure fight over who owns the user and who owns the liquidity. Consumer apps will keep embedding prediction trading inside broader investing, betting, and crypto workflows, while infrastructure layers that can aggregate fragmented venues will become more valuable as more regional, vertical, and regulated exchanges come online.