> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/itservices/user-interface/insight-tech-user-interface/events.md).
# Events
The **Events** section in the Insight Tech Console provides real-time visibility into ongoing and upcoming sports events, enriched with ratings, alerts, and performance insights that help operators evaluate risk and prioritise monitoring.
This page is designed for users who need to oversee match-level integrity and operational efficiency, such as traders, risk managers, and sportsbook operations teams.
### What it shows
Each row in the table represents a sports event, showing the start time, sport, event name, country, tournament, and ratings across different stages (pre-match, live, suggested, and current).
Events can be filtered by sport, searched by name or ID, and sorted by start time or rating. **Event ratings** range from 1 (low profile) to 10 (high profile) and are model-derived based on turnover potential, fraud signals, sharp behaviour, and player concentration.
The **Live Time Delay** (LTD) section provides information about the recommended bet placement and cashout processing delays for matches in Sportradar offering. Suggested LTD settings are shown next to the current MTS system settings as an ML-model output to support risk-informed decisions.
Alerts column highlights unresolved signals related to specific events (e.g. suspicious volume or sharp customer behaviour).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sportradar.com/itservices/user-interface/insight-tech-user-interface/events.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
