> 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/games/simplay-sports/visualization-options.md).

# Visualization Options

## Sportradar Live Match Tracker

In the case you’re already integrated with the Betradar Live Match Tracker (LMT) for Tennis, Cricket, and Baseball, the Sim-Play Tennis & ATP Legends, Cricket and Baseball visualizations are already available in the LMT.

For Sim-Play sports, you can simply pass the full Sport entities URNs for match IDs (e.g. `vti:match:28701023`).

{% hint style="warning" %}
LMT for Sim-Play does only work with production match ID and can display events. Sim-Play do have an individual staging environment with individual match ID´s. Visualization can be just verified with production data.
{% endhint %}

The initialization of LMT for Sim-Play sports should follow the same steps&#x20;as for live sports:

* <https://widgets.sir.sportradar.com/docs/Widgets.match.LMT.html>
* <https://widgets.sir.sportradar.com/docs/Widgets.match.LMTPlus.html>

For more information, please refer to the [LMT general documentation](https://widgets.sir.sportradar.com/docs/Widgets.match.LMTPlus.html).


---

# 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/games/simplay-sports/visualization-options.md?ask=<question>&goal=<user_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.
