> 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/mts/alpha-odds/introduction-and-integration-details.md).

# Introduction and Integration Details

<figure><img src="https://3563239839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3JvMJx2x71aK15pDIp2j%2Fuploads%2FUEqtgCR7BhWe5eX6ACiA%2Fbanner-alpha-odds.png?alt=media&amp;token=8a828d81-b640-4edc-81c2-44652313770f" alt=""><figcaption></figcaption></figure>

### What is Alpha Odds?

Alpha Odds delivers enhanced odds pricing for customers who provide liquidity information through an MTS ticket integration, with or without the MTS risk management service.​

Enhanced odds pricing capabilities include:​

* Individualized odds adjustment taking into account own liabilities and predicted further turnover to reduce liability and balance further turnover.​
* Sharper price positioning relative to the industry to increase turnover while maintaining or increasing profit margins.​
* Dynamic odds key adjustment to balance between risk exposure vs. increased turnover flow.​

Supported sports include soccer, basketball, tennis, and cricket.&#x20;

### Integration

#### Integration (UOF)

**Producer masking**

As a prerequisite, a client must be on the UOF, and MTS will need to switch the client's validation to validate against the bookmaker-specific feed, also known as a Delta Offer. No additional integration is required as long as all MTS integration and sportsbook testing have been completed. Clients will have to agree to a commercial contract to use the Alpha Odds service before a simple configuration is applied on the MTS side to enable the service.

#### Sportsbook testing (UOF)

Clients are required to carry out testing.

The purpose of the testing is to ensure all the requisites listed below are met.

Various steps in the testing process validate the integration with the Unified Odds Feed and MTS while ensuring the production system is not affected during the certification.

#### Integration (MTS)

Existing clients integrating Alpha Odds are required to pass the UOF Sportsbook Test and undergo a brief verification process with our MTS Client Integration Engineers.

#### Client requisites

{% tabs %}
{% tab title="Live" %}
{% hint style="warning" %}
The client must have LO.

The client must **not** use Betpal for manual trading of events.

The client must **not** use Sportradar’s Probabilities / CashOut   (A*vailable on request to use both solutions).*

The client must **not** use Custom Bet (the feature returns an error for LDO events).  \
(*The* *solution to use Live Custom Bet:  The client must use Transaction 3.0 and the Harmonization feature in Ctrl.)*
{% endhint %}
{% endtab %}

{% tab title="Pre-match" %}
{% hint style="warning" %}
The client must have Pre-match.
{% endhint %}
{% endtab %}
{% endtabs %}

{% hint style="warning" %}
Clients with multiple active MTS sub-accounts may require account restructuring to ensure the odds values for each sub-account do not disrupt each other.
{% endhint %}


---

# 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/mts/alpha-odds/introduction-and-integration-details.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.
