> 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/legacy-products/legacy.md).

# Legacy Overview

Documentation for legacy products

This section contains documentation for legacy LSports products that are being phased out in favor of ARENA360.

{% hint style="warning" %}
**Legacy products are in maintenance mode.** New customers should use ARENA360 products (TRADE, DEFEND, BOOST, ENGAGE). Existing customers are encouraged to migrate.
{% endhint %}

***

## Available Documentation

### [Odds Service](/u/legacy-products/odds-service.md)

The original LSports odds feed service. Now superseded by **TRADE**.

| Feature         | Odds Service  | TRADE               |
| --------------- | ------------- | ------------------- |
| Data Delivery   | RabbitMQ      | RabbitMQ            |
| UI Platform     | Legacy Client | Modern Platform     |
| Configuration   | API-based     | UI + API            |
| Analytics       | Limited       | Full (via BOOST)    |
| Risk Management | Separate      | Integrated (DEFEND) |

***

## Migration

Ready to upgrade to ARENA360?

➡️ [Migration Guide](/u/legacy-products/migration.md)

***

## Support

Legacy products remain supported for existing customers:

* **Technical issues:** [Open a ticket](https://support.lsports.eu/support/tickets/new)
* **Migration questions:** Contact your CSM
* **Documentation:** See product-specific pages below


---

# 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/legacy-products/legacy.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.