Skip to main content
Gemini Predictions is a centralized prediction market run by Gemini. Like Kalshi, it uses traditional limit-order semantics with server-side authentication — no client-side signing needed.

At a glance

Prerequisites

  • A Gemini account with Predictions enabled
  • A Gemini API key with order placement permissions — generate at exchange.gemini.com (or exchange.sandbox.gemini.com for testing)
  • Save the API key and HMAC secret immediately — Gemini only shows the secret once

One-time setup: register credentials

The Delphi server stores the HMAC secret encrypted at rest and uses it to sign every Gemini request.

Place an order

buildGeminiOrder is a thin convenience helper — it just shapes your input into the JSON the API expects. There’s no cryptography happening client-side; you can construct the payload by hand if you prefer:

Order parameters

Query and cancel

Common pitfalls

Confirm your API key has the Trader role (or Auditor + Trader) on Gemini. Read-only Auditor-tier keys can fetch market data but can’t place orders.
Gemini lets you rotate the HMAC secret while keeping the same API key ID. If you rotate, re-register on Delphi with the new secret:
The Delphi server points at production Gemini by default. Sandbox API keys (from exchange.sandbox.gemini.com) won’t work without server-side configuration. Contact Delphi support if you need sandbox routing.
Gemini contract symbols include the expiry encoded in the suffix (e.g. FEDJAN26 = Fed meeting January 2026). Always pull the latest active symbols from Gemini’s market data endpoint before placing orders — old symbols will return “market not found” once they settle.

API reference