> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/trade/concepts/market-types.md).

# Market Types

TRADE supports various market types, each with distinct behaviors for odds calculation and provider configuration. Understanding them is key to effective risk and margin management.

### **Single Provider Markets**

#### **Definition**:

Markets where providers offer different bets that cannot be aggregated.

#### **Behavior**:

* In **Calculated Odds mode**, only provider lists with one provider can be selected. Calculated odds are available from that single provider only.
* For Provider Odds<sup>+</sup>, provider lists with multiple providers can be selected, but **calculated odds will not be available**; only provider odds are sent.
* A warning appears in the UI when multiple providers are chosen for these markets.

### **Average Provider Only Markets (Special Markets)**

#### **Definition**:

Markets with non-overlapping or independent bets (e.g., range or outright markets).

**Behavior**:

* Odds are averaged across all providers.
* Only competitive margin = 0 is allowed.
* Calculated odds are based solely on raw averages.
* Margin customization is not supported.


---

# 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.lsports.eu/u/trade/concepts/market-types.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.