> 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/imga-dl-trading-odds-distribution/odds-distribution-service/market-behavior.md).

# Market Behaviour

This page covers the different collection levels IMGA offer through the various tours and market logic in terms of whether it's deadball, in play, when the market opens, suspends, closes etc. This documentation is produced in conjunction with our pricing partner, Dime Line Trading.

Please see the DL1-5 tabs for different rulings based on coverage but note this is still a work in progress, so any feedback please share with us so we can make the product as good as it can be. [support@sportradar.com](mailto:support@imgarena.com).

{% file src="/files/XQnRW0DLTyfHAfTKlTXp" %}


---

# 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/imga-dl-trading-odds-distribution/odds-distribution-service/market-behavior.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.