The price. And the context.

Consensus

A reference, not another raw feed.

A de-vigged probability for each outcome, derived from current order-book observations. Consensus includes fixtures, live scores, venue mappings and settlement grades over REST. Snapshots are at most one second behind the stream; that is a delivery difference, not a measure of the age of market information.

Realtime delivery

Keep pace with published changes.

Everything in Consensus, with consensus changes delivered over server-sent events. Receive the current state first, then price updates and removals. Live-score streaming is planned separately and is not yet a documented live endpoint.

Signals

Change the quote when conditions change.

Everything in Realtime, plus streamed bet-stop and widened-state flags. A bet-stop tells your system to widen or pull quotes. It does not stop the venue’s market, and the consensus price keeps updating. A numeric uncertainty measure is planned; the current widened-state flag is not a calibrated confidence interval.

Fixtures

Every game stays accounted for.

A fixture never disappears silently. Postponements, suspensions and cancellations retain a traceable history. Stable identifiers join schedules to live scores, venue mappings and settlement grades. A replacement after a locked-date postponement receives its own linked identifier.

Live scores

Follow every live game.

Scores, period and clock tied to the same fixture identity. Baseball includes inning, count and occupied bases. Use REST for current game state; live-score streaming is planned.

Results

Settle on a shared result.

Consensus results for moneyline markets, with win, lose or push for each outcome. Grades require agreeing evidence; conflicting results remain unpublished for review.