> 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/uof/introduction/integration-process.md).
# Integration Process
The Unified Odds Feed integrations are supported via our Integration Program.
We offer personal and direct assistance during the integration where a dedicated Integration Manager will stay in direct contact with your technical team during the entire process via direct chat solutions.
#### Process Overview
> For details about our integration program, see [**this**](/uof/introduction/integration-process/integration-program.md) page.
Depending on the team size / structure, team experience and SDK use, our integration team collected the below estimations for combined Unified Odds Feed integration and MTS integration.
#### Time Planning including MTS Integration
{% hint style="success" %}
**Note**
Time Estimations on the full integration journey to launch is ***+/- 21 weeks*** (Managed Trading Services integration included). However, the integration timelines and schedules can be adjusted to suit the respective client's preferences.
An estimation of the full integration cycle of the Unified Odds Feed including MTS, based on the average integration times we recorded so far:
* UOF Integration: +/-10 weeks
* UOF Sportsbook Test (backend to frontend test): +/-2 weeks
* MTS Integration: +/-8 weeks & MTS End to end (E2E) test: +/- 1week
{% endhint %}
Depending on team size/structure, team experience and SDK use, our integration team collected the below estimations for combined Unified Odds Feed & MTS integrations.
---
# 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/uof/introduction/integration-process.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.