> 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/boost/trading-performance.md).

# Trading Performance

Analyze trading quality metrics

Compare market uptime and margin efficiency to optimize your trading quality.

***

## Overview

The Trading Performance tool helps you analyze and compare trading quality across two dimensions:

* **Market uptime** — See how often your markets are open and tradeable
* **Margin comparison** — Compare configured vs delivered margins across providers

***

## Available Views

| View                                                                     | Description                         |
| ------------------------------------------------------------------------ | ----------------------------------- |
| [Overview](/u/boost/trading-performance/overview.md)                     | Visual comparison charts and trends |
| [Performance Matrix](/u/boost/trading-performance/performance-matrix.md) | Side-by-side tabular data           |

***

## How to Use

1. Select your **primary provider** as the baseline
2. Choose **competitor providers** to compare against
3. Filter by **sport**, **league**, or **time period**
4. Analyze the results to identify trading quality gaps

***

## Key Metrics

| Metric                | Description                                               |
| --------------------- | --------------------------------------------------------- |
| **Market Uptime**     | Percentage of time each market type is open and tradeable |
| **Margin Comparison** | Difference between configured margin and delivered margin |

***

## Related

* [BOOST Overview](/u/boost/boost.md) — Main BOOST documentation


---

# 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/boost/trading-performance.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.