> 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/api-and-structure/api-stage-structure.md).
# API - Stage Structure
With the introduction of the UOF a new concept was added which is the Stage structure.
The stage structure does no fit into the tournament category structure and the customer needs to be aware that this kind of entities should be treated differently.
A stage can be thought of as a big box containing stages which on their end contain stages as well.
Generally, a stage which contains several stages is known as a parent stage and the contained ones are child stages.
Child stages can be on their hand parent of other child stages.
Schema below provides an overview of the concept.
In order for the customer to get more detailed info related to any competition organized in a stage structure, it is necessary to dig deeper from parent stage into child stage until the lowest level of the parenting chain.
The UOF end points provide the chance of exploring the competition from the highest stages till the lowest. The one below is the general schema in order to get to the lower stages starting from the ID of the sport.
With the UOF we have several sports organized into stages and for each of them we will report an example of how it is possible to retrieve detailed info at the bottom stage starting jus from the sport id.
---
# 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.sportradar.com/uof/api-and-structure/api-stage-structure.md?ask=&goal=
```
`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.