> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/developer/player-control/player-info.md).

# Player Info

The Embedded, Package HTML and Web Page Widgets, as well as custom Widgets allow HTML, CSS and JavaScript to be embedded into the Player.

## Xibo v2

Starting in Xibo for Android v2 R207 and Xibo for Windows v2 R255 it is possible to call `/info` on localhost to get information about the running player. You can do this from any Widget which uses a browser.

```javascript
$.get("http://localhost:9696/info");
```

This returns:

```json
{
  "hardwareKey": "",
  "displayName": "",
  "timeZone": "",
  "latitude": null,
  "longitude": null
}
```

## Xibo v3

Starting in version 3 of Xibo we have a library available to make consuming the above information easier. You can find this here: <https://github.com/xibosignage/xibo-interactive-control>


---

# 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.xibosignage.com/developer/player-control/player-info.md?ask=<question>&goal=<endgoal>
```

`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.