> 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/simulated-reality-sir/simulated-reality.md). # Simulated Reality **Introduction:** Our ‘Simulated Reality’ (or in short ‘SR-League’), is a unique, artificial intelligence-driven solution to serve you further content within multiple Betradar products, in order to guarantee a seamless user experience for your customers. Simulated Reality matches will be provided in a regular match format and the tournament names will indicate that these matches are simulated, not real life. However, our comprehensive pre-match and live odds as well as simulated live data events will make the customers experience as close to the real thing as possible. \ **Products to support Simulated Reality:** • Pre-Match Odds Service (legacy & UOF)\ • Live Odds Service (legacy & UOF)\ • Live Data Service\ • [Live Match Tracker](https://sportcenter.sir.sportradar.com/simulated-reality) () **Available Sports for Simulated Reality:** * [Tennis](/simulated-reality-sir/tennis/intro.md) * [Soccer](/simulated-reality-sir/soccer/intro.md) * Cricket *** --- # 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, and the optional `goal` query parameter: ``` GET https://docs.sportradar.com/simulated-reality-sir/simulated-reality.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.