> 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/bettor-sense/introduction.md).

# Introduction

Welcome to Sportradar's Bettor Sense documentation

This portal provides technical resources, integration guides, and product updates for Sportradar’s AI-powered player protection tool Bettor Sense — helping you build safer, fairer, and more compliant betting environments.

Bettor Sense is a part of the Responsible Gaming Product. The aim of this service is **early detection of problematic gambling powered by artificial intelligence (AI).**

**There are several benefits of using Bettor Sense as an operator, to name only a few:**

* **Earlier and more accurate detection:** respond faster to early warning signs with the flexibility offered by AI.
* **Personalise your interventions:** let data-driven insights guide your interactions with at-risk customers.
* **Easy onboarding:** get up and running in as little as a few weeks.
* **Protect your business:** meet increasing regulatory compliance requirements that demand more sophisticated RG solutions and avoid severe penalties.

Our advanced algorithm is looking at player's betting behavior, financial data and other available behavioural patterns to help you better assess and manage players who are at risk of problematic gambling.

By integrating with Bettor Sense you will be able to receive **up-to-date risk scores for active players** within your database along with their **risk categories and different areas that contributed to the scores**.

This will allow you to **trigger actions within your existing system** based on regularly updated risk scores and adapt the communication to the severity of the player's risk score.

With an **AI-powered predictive approach you can prevent harmful actions** from happening rather than react to them when it's already too late.

#### Developed by experts <a href="#bettorsenseintroduction-developedbyexperts" id="bettorsenseintroduction-developedbyexperts"></a>

* Bettor Sense is an innovation project supported by Innosuisse.
* Sportradar: AI unit with extensive experience in developing models for the gambling industry.
* Zurich University of Applied Sciences: established track record of academic and applied research in computation, data-oriented projects

***

#### Contact us

For any **sales related queries**, please contact your sales representative or email:\
:envelope:  <sales@sportradar.com>

For technical support, please reach out via your integration contact or account manager.


---

# 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/bettor-sense/introduction.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.
