# Entity Descriptions

Entity endpoints offer additional insights into related entities outlined in fixtures and event information. The localized version of an entity is accessible by prefixing any of the entity paths with a language code.

<table data-header-hidden><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><br></td><td>HTTP</td><td>Endpoint Path</td></tr><tr><td>1</td><td>GET</td><td><pre><code>Name: UOF - Player profile endpoint 

Path: sports/{language}/players/sr:player:{id}/profile.xml
Description: Returns the player information. </code></pre></td></tr><tr><td>2</td><td>GET</td><td><pre><code>Name: UOF - Competitors profile endpoint

Path: sports/{language}/competitors/sr:{urn\_type}:{id}/profile.xml
Description: Returns the competitor (team / individual player) information </code></pre></td></tr><tr><td>3</td><td>GET</td><td><pre><code>Name: UOF - Venues summary endpoint

Path: sports/{language}/venues/sr:venue:{id}/profile.xml
Description: Returns sport structure, competitor, and venue information. </code></pre></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.sportradar.com/uof/api-and-structure/api/entity-descriptions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.