Frequently asked questions

Updated 2026-09-10

Which sports odds API is the fastest?

In the September 2026 run the lowest line-change latency from US-East was Pinnacle at 243 ms p95, with PinnWire the fastest third-party feed at 286 ms p95. Per sportsbook — Pinnacle: Pinnacle 243 ms p95 (next best: PinnWire 286 ms p95); Betradar (Sportradar): Sportradar 380 ms p95 (next best: OddsRadarWire 472 ms p95); FanDuel: FanLine Wire 521 ms p95 (next best: BoltOdds 564 ms p95); ODDIN.GG: ODDIN.GG 411 ms p95 (next best: OddiWire 457 ms p95). Rankings hold from EU-Central, where the fastest feed was Pinnacle at 194 ms p95 and US-facing aggregator feeds run roughly 200–600 ms slower. Full table, per-sportsbook pages and raw data are linked from every number on this site.

What is line-change latency and why not just measure response time?

Line-change latency is the delay between a sportsbook changing a price and that price appearing in the API. Response time only measures how fast the server answers; it says nothing about whether the odds inside are fresh. A REST API can respond in 50 ms while serving a line that moved 20 seconds ago.

Is this benchmark independent?

Yes. OddsBench is not owned by, paid by or affiliated with any provider listed. We buy every API key ourselves, there are no affiliate links and no provider can pay for placement. The per-provider measurements are downloadable as CSV and JSON for every run, so each published figure can be recomputed from the data file it comes from.

How often is it updated?

Monthly. Each run is a 7-day continuous window; results are published within a week of the window closing and kept at a permanent URL under /runs/.

Why are push feeds (WebSocket, SSE, AMQP) faster than REST?

Push feeds send a message the moment a price changes. Polled REST feeds are only as fresh as the polling interval allows and are often served from a cache with its own refresh cycle, which adds seconds. We show the protocol and polling interval for every row so like is compared with like.

Which sports odds API is the best value?

Best value ranks only providers that publish an unlimited real-time price for a tier that carries every book they advertise, and whose measured line-change p95 is 1,000 ms or better — slower feeds and subset tiers are published but not ranked. Value score = line-change p95 (ms) × monthly price ($) ÷ 1,000, lower is better. In the September 2026 run from US-East the best overall value is PinnWire at $178/mo with 286 ms p95 (score 50.9). Per sportsbook: Pinnacle — PinnWire; Betradar (Sportradar) — OddsRadarWire; FanDuel — FanLine Wire; ODDIN.GG — OddiWire.

What does the price column mean?

The advertised monthly price of the cheapest self-serve plan that includes an unmetered WebSocket or SSE stream of live line changes: no daily or monthly cap, no credit or stream-hour metering, no league or market scope limit. Where push is an add-on the base plan plus add-on is shown (for example PinnWire Pro $89 + WebSocket $89 = $178). A dash means no such plan is published: REST-only (The Odds API, OddsBlaze, Sportsbook API), metered (TheRundown bills WebSocket messages against a 100M/month cap; Odds-API.net meters stream-hours; ParlayAPI meters credits on every tier), pre-match only (Odds-API.net, Odds Engine), or quote-only (Sportradar, OpticOdds, Unabated, OddsJam, LSports, OddsMatrix, FairPlay, OddsPapi). Prices were read from each provider's public pricing page on the publish date.

Why are some prices marked scope-limited?

Because that tier does not carry every book the vendor advertises. SharpAPI's widest self-serve tier (Sharp, $399 + $99 WebSocket) covers 25 of the 40+ sportsbooks it sells; Odds-API.io's (Pro + WebSocket, £458 = $618.67) covers 15 of 265+ bookmakers. We publish the vendor's own list price for the widest tier sold self-serve, state the scope, and keep the row out of the value ranking: scaling it into a 'full-coverage' figure would be our arithmetic, not the vendor's price.

What does 'Try without signup' mean?

The provider publishes a demo key or open endpoint that returns live odds with no account. In the September 2026 run 4 of the 34 providers do; the rest require signup or a sales contact before any data is returned.

Can I use this data?

Yes, under CC BY 4.0. Cite as: OddsBench, Sports Odds API Latency Benchmark, September 2026, https://oddsbench.xyz.

A provider disputes a number. What happens?

Providers can email [email protected] with the run ID, the provider and the vantage. We re-run the affected probes from both vantages and publish the outcome, including when we were wrong, in the run changelog.