> 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/widgets-and-trackers.md).

# Widgets & Trackers

- [Overview](https://docs.lsports.eu/u/widgets-and-trackers/widgets.md): Embeddable sports data widgets and live tracking tools, powered by STATSCORE
- [PreMatch Pro](https://docs.lsports.eu/u/widgets-and-trackers/prematch-pro.md): Pre-match statistics and data visualization widgets, powered by STATSCORE
- [LiveMatch Pro](https://docs.lsports.eu/u/widgets-and-trackers/livematch-pro.md): Live match tracking and real-time statistics widgets, powered by STATSCORE
- [Score Frame](https://docs.lsports.eu/u/widgets-and-trackers/score-frame.md): Compact livescore display widget for any platform, powered by STATSCORE
- [Points InPlay](https://docs.lsports.eu/u/widgets-and-trackers/points-inplay.md): Point-by-point live tracking for tennis and other sports, powered by STATSCORE
- [Scout](https://docs.lsports.eu/u/widgets-and-trackers/scout.md): Live sports data collection and scouting coverage, powered by STATSCORE
- [STATSCORE API](https://docs.lsports.eu/u/widgets-and-trackers/statscore-api.md): Direct API access to STATSCORE sports data


---

# 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.lsports.eu/u/widgets-and-trackers.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.