> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/engage/hyper-livescore.md).

# Hyper Feed

Welcome to the LSports Hyper Feed Integration Guide!

## Overview

LSports Hyper Feed is a real-time service that delivers live sports incidents enriched with a confidence grade, enabling customers to power live visualizations, in-play analytics, and betting tools with unmatched speed and transparency and to analyze and act on data in real time, monitor and investigate live events with full transparency, boost in-play turnover, and gain a competitive edge by reacting faster and with clear visibility into the confidence level of each event.

To ensure context and event correlation, the LiveScore Feed is accompanied by a complementary Fixtures Feed that provides pre-event metadata (teams, league, location, sport, start time). Customers subscribe to two RabbitMQ queues and join incoming incidents with fixtures by `fixtureId`.

***

## Understanding Confidence

Hyper Feed employs advanced decision models combining multi-provider validation with proprietary weighting algorithms. The confidence score reflects both provider consensus and historical accuracy patterns, continuously optimized by sport, league, and incident type. In the latest service version, only incidents meeting our quality thresholds are published.

Each incident carries a confidence score from 0.0 to 1.0. Use the thresholds below to decide how to act on an incident based on its score.

| Confidence level | Threshold         | Notes                                                                                                                                                           |
| ---------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Low              | ≤ 0.25            | Suspensions and general-purpose use cases: widgets, match trackers, and notifications                                                                           |
| Medium           | ≥ 0.25 and < 0.51 | Risk, trading, and decisioning: automated trading workflows, operational alerts, risk exposure management, and odds creation based on higher-confidence signals |
| High             | ≥ 0.51            | Settlement: confirming final outcomes                                                                                                                           |

***

## Supported Sports

Football, Basketball, Baseball, Ice Hockey, American Football, Badminton, Bandy, Beach Volleyball, Bowls, Boxing, Curling, Darts, E-Games, Floorball, Futsal, Hockey (Field Hockey), Kabaddi, Netball, Padel, Snooker, Squash, Tennis, Water Polo, Handball, Volleyball, Chess, Lacrosse, Softball, Sumo, Table Tennis, Gaelic Sports, Australian Rules, Rugby Union, Rugby League

***

## Incidents

Hyper Feed reports live incidents per sport type. Each incident has a stable Incident ID delivered in the `id` field of every LiveScore message. For the full catalog of incidents available per supported sport, see [Incidents by Sport Type](/u/engage/hyper-livescore/enumerations/incidents-by-sport-type.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lsports.eu/u/engage/hyper-livescore.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.