> 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 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/ctrl/control-ctrl.md?ask=<question>&goal=<user_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.