Esports consensus odds.
Fair lines, gated edges.
GET /v6/esports/{sport}/lines.Why consensus odds beat a single book
If you searched for fair esports odds, prediction-market priors, or a sportsbook + DFS Teams + Kalshi/Polymarket join — this is the product. Not another scrape. A consensus layer.
- —One venue is not a fair price — A single sportsbook or DFS board can lag, shade, or thin out. Models that anchor to one feed inherit that bias and call it edge.
- —Prediction markets and books do not share a schema — Kalshi and Polymarket speak probability. Sportsbooks and DFS Teams speak American. Without de-vig and join keys, you cannot build a real consensus.
- —Raw edge spam is noise — Huge gaps usually mean bad joins, dead liquidity, or two-source accidents — not alpha. Ungated feeds train models on garbage.
How KashRock builds consensus
Workers keep venue boards warm. The /lines request reads Redis, joins matchups, de-vigs, and ranks — no live upstream fan-out on the call path.
- —De-vig + weighted consensus — Each venue is normalized to probabilities that sum to 1.0. Consensus is a weighted mean (prediction markets default weight 1.5).
- —Hard quality gates — Liquidity floors, ≥3 sources for top_edges, disagreement ≤12 pts, raw edge ≤8%. Ranked by confidence × liquidity × edge.
- —One route, four markets — match_winner, map_winner, total_maps, and map_handicap on GET /v6/esports/{sport}/lines — CS2, Valorant, LoL, Dota 2, COD, R6, MLBB, Deadlock.
Call consensus in one request
Hobby key or higher. Response includes full events with quality flags plus a gated top_edges feed.
curl -H "X-API-Key: YOUR_KEY" \ "https://kashrock.up.railway.app/v6/esports/cs2/lines?market=match_winner"
If you need a normalized feed instead of another UI wrapper, the Esports API exposes live boards, schedules, and history on one schema — with the IDs and outcome patterns that keep backtests and grading honest. Start free on Sandbox, or see published pricing.