> 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/provider-benchmark.md).

# Provider Benchmark

Analyze providers coverage metrics

Compare providers on fixture and market coverage to optimize your provider configuration.

***

## Overview

The Provider Benchmark tool helps you analyze and compare provider coverage across two dimensions:

* **Fixture coverage** — See which providers cover more fixtures
* **Market coverage** — Compare the breadth of markets offered per fixture

***

## Available Views

| View                                                              | Description                         |
| ----------------------------------------------------------------- | ----------------------------------- |
| [Trend Analysis](/u/boost/provider-benchmark/trend-analysis.md)   | Visual comparison charts and trends |
| [Coverage Matrix](/u/boost/provider-benchmark/coverage-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 the best provider mix

***

## Key Metrics

| Metric               | Description                                 |
| -------------------- | ------------------------------------------- |
| **Fixture Coverage** | Number of fixtures covered per sport/league |
| **Market Coverage**  | Number of markets offered per fixture       |

***

## 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/provider-benchmark.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.