> 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/monitoring/match-up-view/match-up-comparison-with-other-bookmakers.md). # Match Up comparison with other bookmakers Along each row in Match Up view, the user can quickly compare their market position for that particular selection of that market, firstly against the market average and then against nominated bookmakers. The market average odds being displayed have already been converted to reflect the user's own key. Moreover, either side of the market average Ctrl displays the lowest and highest odds values used to calculate that average. The bookmakers displayed along the row are those nominated in the active bookmaker list, sorted from largest to smallest assigned weight. The user can also quickly see the key being used by competitors. Finally, by hovering over a bookmaker’s name in this row the weighting of that bookmaker in the active bookmaker list will be displayed. --- # 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/monitoring/match-up-view/match-up-comparison-with-other-bookmakers.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.