AlternativesSourced from Prediction market API rate limits, tested with a daily ramp
Kalshi alternatives
CFTC-regulated event contracts exchange with a token bucket API
Kalshi runs a CFTC-regulated event contracts exchange with the only documented token bucket in its cohort (around 20 requests per second on the basic read tier at the time of writing). Its order book and single-market endpoints go to origin on every request, but the market list is served from CloudFront with `max-age=15`, so list latency measures the edge rather than the API origin. The WebSocket requires authentication, which excludes Kalshi from the public WS panel. Builders sizing against this kind of API need two numbers: the real latency of the hot endpoints at a polite request rate, and what happens as the rate climbs. This benchmark probes book (`/markets/{ticker}/orderbook`), price (`/markets/{ticker}`) and list (`/markets`) endpoints continuously from three Railway regions (us-east, eu-west, sgp), every 5 to 7 seconds over warm keep-alive connections, with a separate cold-connect probe once per minute. Once per day per venue it runs a 60-second-per-tier ramp at rising request rates, recording added latency against the same-hour warm baseline and any 429 onset. Kalshi's ramp uses tiers 25/50/100 requests per 10 seconds and stops at the first 429 out of respect for the documented contract. The harness flags CDN cache hits via `cf-cache-status`, `x-cache` and `age` headers and excludes them from latency aggregates so no venue ranks on its CDN. Every request carries an identifying User-Agent with a contact address. The cohort competing with Kalshi includes Polymarket (Cloudflare-queued CLOB), Limitless (undocumented limits, errors CDN cached for 4 hours), Manifold (500 req/min per IP, whole API behind a 5-second cache) and Myriad (single-region Heroku origin, no order book).
Positioning
Kalshi is a US event-contracts exchange with two API surfaces (Predictions and Perps) exposed over REST, WebSocket and FIX, authenticated by API key and governed by a documented token-budget rate-limit model with 7 named tiers (Basic, Advanced, Expert, Premier, Paragon, Prime, Prestige) that scale from a few hundred to several thousand tokens per second, with a burst allowance after idle time. Its architectural moat is regulatory: the venue operates under CFTC-recognised status for event contracts, which shapes the API surface (identified market participants, published limits, FIX access for institutional flow) and the data redistribution terms that any downstream consumer inherits. For a pm-rate-limits benchmark, that means Kalshi is the cohort's baseline for what a documented contract looks like: token budgets are formally tiered, order and book endpoints go to origin on every call, and the market-list endpoint is served from a CDN with a short max-age, so list latency measures the edge. WebSocket access requires authentication, which is standard for a regulated venue and keeps the public unauthenticated WebSocket surface small. Trading systems that require CFTC-supervised counterparty, FIX connectivity or auditable API terms integrate on Kalshi natively. Teams migrate to a Polygon-based CLOB when the product requires permissionless market creation, non-US retail flow, or on-chain settlement receipts that the regulated venue's off-chain matching does not surface.
About Kalshi: kalshi.com
Top 4 Kalshi alternatives
- Best
- 200 ms
- Median
- 322 ms
- Worst
- 2.00 s
- Spread
- 13.7×250 ms → 3.42 s
- Samples · 24h
- 261,6227 providers
Warm book latency · last 24 hours
Warm book latency · last 24 hours
Product ledger · sorted by p50
| Product | Warm book p50 | Trend | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Color | № | 24h | ||||||||
| 01 | 200 ms | |||||||||
| 02 | 282 ms | |||||||||
| 03 | 322 ms | |||||||||
| 04 | 1.27 s | |||||||||
| 05 | 2.00 s | |||||||||
| — | — | — | ||||||||
Same data as /benchmarks/pm-rate-limits, refreshed every minute. OpenChainBench is community-run; methodology is open.