> 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/introduction/glossary/introduction.md). # Introduction ## E *** ### **Environment:** UOF is accessed through separate Integration and Production environments. The Integration environment is for testing and validation without affecting live data; access is upgraded to Production once onboarding is complete. ## I *** ### **Integration Program:** Betradar's structured, sprint-based onboarding process for new UOF integrations. Timelines vary depending on team size, experience, and whether you use the SDK or the raw API/protocol. ## P *** ### **Producer** The internal Betradar system that generates a given piece of odds or event data, for example, LiveOdds, the pre-match odds service, MTS, BetradarCtrl, BetPal, or PremiumCricket. Every message in the feed can be traced back to the producer that created it, which matters during handover periods when producers can send conflicting updates for the same market. ## S *** ### **Security Access Token** The credential used as the AMQP username to authenticate and connect to the feed. Issued after the introduction call, initially scoped to the Integration environment before being upgraded for Production. ## U *** ### **Unified Odds Feed (UOF)** Betradar's single delivery mechanism for all odds feed data. Combines real-time XML messages pushed over AMQP with an API for supporting metadata, covering Live Odds, pre-match betting, and Virtual Sports through one feed. --- # 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/introduction/glossary/introduction.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.