> 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/ctrl/guide/configuration/unified-odds-feed.md).

# Unified Odds Feed

Betradar Ctrl works in conjunction with Betradar’s Unified Odds Feed, a faster and lighter data feed that combines several odds producers (such as pre-match odds, live odds, odds for virtuals, player markets…). The Unified Odds Feed settings in the Config section allow the user to download technical documentation related to the Unified Odds Feed. The Unified Odds Feed access token settings allow the user to generate new additional access tokens and manage the existing ones. The user can also check the IPs that have been whitelisted to access the Unified Odds Feed.

<figure><img src="/files/MNHU6oWUPlgm8hWnXAQi" alt=""><figcaption></figcaption></figure>


---

# 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/ctrl/guide/configuration/unified-odds-feed.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.