> 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/features/delta-offer.md). # Delta Offer Delta offer is a replica of client's events, markets and odds stored in MTS system and used in validation of bets coming from the bookmaker's channels. Instead of relying on MTS global feed and global fair odds validation, with delta offer client can benefit from more accurate odds validation through [alternative odds](/mts/features/alternative-odds.md) feature, and gain access to liability driven odds, CTRL's early odds feature, customer specific settlements, manual odds adjustment, and more. Pre-requisites for delta offer activation are: * The client has an active subscription to at least one Unified Odds Feed package, * The client is using a node ID in their recovery requests and the node ID is always a positive integer value, * Feed probabilities have to be enabled for all active producers. {% hint style="info" %} **Note** Please note that even with the delta offer, MTS maintains a maximum allowable deviation from the global fair odds. Any ticket exceeding this limit will be rejected. Currently, the deviation tolerance is set to 50% above the global fair net odds. {% 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/features/delta-offer.md?ask=&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.