The July 30 release adds unauthenticated volume data access after Gemini introduced a sports market taxonomy and batch-order APIs for its CFTC-regulated prediction markets platform.
Gemini has expanded developer access for Gemini Predictions with a public REST API endpoint for trading data and a standardized sports market taxonomy in its Predictions API. The new public endpoint, launched on July 30, provides volume data by category and by day or hour in UTC without authentication, API keys or account creation, while the taxonomy introduces a sportsMarket object that lets developers filter CFTC-regulated sports prediction events by sport, market family, subject, scope and optional metric. Gemini said the taxonomy is designed to reduce the need to parse titles or provider-specific tickers when building trading tools, analytics dashboards and automated strategies. Supported market families include moneyline, spread, total, prop and futures, with coverage including baseball, soccer, American football and cricket. Example filters include sport=american_football, sports_market_type=prop and sports_market_metric=passing_yards. The public data release follows July 17 product updates that added batch-order APIs and new event categories, including FIFA World Cup contracts. Batch orders allow market makers and algorithmic traders to place or cancel multiple orders at once. Gemini Predictions launched on December 16, 2025, through Gemini Titan, a CFTC-designated Designated Contract Market, and Gemini says that structure allowed the platform to launch across all 50 U.S. states. By July 2026, the platform had surpassed $24 million in cumulative trading volume and more than 10,000 active users. Gemini also reported that April 2026 volume rose 78% month over month, that prediction markets contributed about $400,000 to Q1 2026 revenue of $50.3 million, and that more than 20,000 users engaged with the service during the quarter. Since launch, the platform has traded more than 100 million contracts. Gemini noted that the sports taxonomy applies at the event level rather than the individual contract level, so users still need the List Events endpoint to confirm live contract availability. Regulatory uncertainty remains, as the CFTC’s stance on event contracts could change and state gaming commissions have not uniformly accepted federally regulated event contracts that resemble sports wagering without a state gaming license.