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

# Bettor Sense API

### Bettor Sense API usage <a href="#bettorsenseapi-bettorsenseapiusage" id="bettorsenseapi-bettorsenseapiusage"></a>

* The Bettor Sense product/service consists of an API and must be used by operators and/or platforms to request the Responsible Gaming Risk Score and Risk Score Explanation for a player (user) or a batch of players.
* The risk score and explainability is determined by the Bettor Sense AI model which looks at the player’s transactions (bets, deposits, withdrawals, and responsible gaming tool usage) over the past 90 days.
* The Bettor Sense AI model accesses the player’s historical transactions via MTS integration (Transaction V3.0).
* **Player Status** is a UI-only workflow field for analyst coordination and is not exposed via the public API.


---

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