> 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/control-ctrl.md).

# Control (Ctrl)

Betradar Ctrl is a new bookmaker system designed to meet the increasing challenges of bookmakers to be faster and more effective in their operations. The system that has been developed in close coordination with our customers provides a full suite of the most wanted features, and zero that are non-essential.

In fact, two critical factors shaped its entire development: **speed** and **control**. Combined with our equally new Unified Odds Feed, Betradar Ctrl is the fastest system in the market in regards to odds delivery, comparison, change and processing

The future proven modular design and slick user interface allows for fast and seamless integration of new services and features.

**Stay always up-to-date** with the latest improvements of Ctrl by signing up for our [blog](https://insidectrl.com/).

<br>


---

# 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/control-ctrl.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.