> 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/uof/live-competition-odds/live-odds-biathlon/biathlon-uof-api-score-information.md). # Biathlon UOF API score information After the race has ended, we provide the following data in the summary endpoint in the Unified Odds API.
For each competitor the following statistics are available: * **position**\ The finishing position of each competitor\
* **wc\_points**\ How many world cup points the competitor gets for finishing in the respective position. If the competitor does not finish in a position where world cup points are awarded, wc\_points is not present next to the competitor. \
* **time**\ The finishing time of each competitor. If the time element is not present, then a competitor did not finish the race. Reasons can be overlapping or retirement. If none of the statistics are available for a certain competitor then he or she has not participated at all in the race. The mentioned data is displayed inside of the results element, as you can see below: \ **Men's 10km Sprint 2023 - Oslo, Holmenkollen** {% code lineNumbers="true" %} ```xml ``` {% endcode %} --- # 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/uof/live-competition-odds/live-odds-biathlon/biathlon-uof-api-score-information.md?ask=&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.