> 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/getting-started/arena360-ai-access.md).

# ARENA360 AI Access

Connect an AI agent to your ARENA360 account and run your trading setup in plain language

Run your trading setup in plain language. Use the Arena AI agent built into ARENA360, or connect the AI client you already use (Claude, Cursor, ChatGPT, GitHub Copilot, or any MCP-capable agent).

{% hint style="info" %}
**Beta.** This capability is in beta and available to selected operators. Your CSM confirms when it is enabled on your account.
{% endhint %}

## What it is

One secure endpoint that connects an AI agent to your ARENA360 account. Instead of clicking through screens or writing API calls, you describe what you want and the agent runs it against your live setup.

You reach that agent two ways. **Arena AI** is the agent inside ARENA360, with its own chat screen and nothing to install. **Your own MCP client** connects to the same endpoint from Claude, Cursor, ChatGPT, or Copilot. Both use your ARENA360 account. What each surface covers is in the table below.

We are rolling the products onto each surface in stages, so coverage differs today.

| Capability                                                             | MCP connection | Arena AI  |
| ---------------------------------------------------------------------- | -------------- | --------- |
| **TRADE**: orders, configuration and odds settings, provider lists     | Available      | Available |
| **BOOST**: coverage, uptime, margin, historical data                   | Available      | Available |
| **DEFEND**: bet monitoring, risk limits, player controls               | Available      | (Coming)  |
| **ENGAGE**: tips and real-time match data                              | Available      | (Coming)  |
| **Coverage Hub**: sports, markets, livescore, and settlement inventory | Available      | Available |
| **Read access**                                                        | Available      | Available |
| **Write access**                                                       | Available      | Available |

Wherever this guide describes something either surface does not cover yet, it says so. Your CSM tells you when the rest opens up on your account.

### Why and when to use it

* **Faster answers** — "What's my InPlay tennis coverage this week?" comes back in seconds.
* **One place to ask** — TRADE, DEFEND, BOOST, ENGAGE, and Coverage Hub, without switching screens.
* **You approve every change** — in a read-and-write session the agent shows the change and its target package, waits for your approval, writes it, then reads it back so you can confirm it landed.
* **Test before production** — rehearse any change on QA or UAT before you repeat it on Production.

## Option 1: Arena AI inside ARENA360

Arena AI is the built-in agent. It has its own screen in the platform, so your traders get the same answers without installing a client or configuring anything.

Open it at <https://platform.lsports.eu/arena-ai>, sign in with your ARENA360 credentials, and start asking. Package selection matches the MCP connection. What Arena AI covers is the Arena AI column in the table above.

**Scope today.** Arena AI answers on **TRADE** (orders, templates, odds settings, and provider lists), **BOOST** (coverage, uptime, margin, and historical data), and **Coverage Hub** (sports, markets, livescore, and settlement inventory). It can also change your TRADE setup: each change is shown with its target package, waits for your approval, then is read back. DEFEND and ENGAGE on Arena AI are still marked in the table above.

### Granting access

Arena AI is off by default, and only an admin on your account can turn it on. Admins grant it per user by adding the **Arena AI** role in ARENA360:

1. Open the avatar menu in ARENA360.
2. Go to **User management**.
3. Open **Users**.
4. Select the user you want to allow and edit their roles.
5. Tick **Arena AI** and save.

The user sees the Arena AI screen on their next sign-in. Remove the role to remove access. If you are not an admin, ask one on your account to add the role for you.

## Option 2: connect your own AI client

Every client uses the same MCP URL:

```
https://arena-mcp.lsports.eu/arena/mcp
```

Sign in with your ARENA360 credentials. At sign-in you choose read, or read and write (see [Permissions](#permissions)).

**Claude** (custom connector / MCP server):

```json
"MCP_Arena": {
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://arena-mcp.lsports.eu/arena/mcp"]
}
```

**Cursor** (MCP config):

```json
"MCP_Arena": {
  "url": "https://arena-mcp.lsports.eu/arena/mcp"
}
```

**ChatGPT:** enable Developer Mode and MCP apps, then add the URL. See OpenAI's [setup steps](https://help.openai.com/en/articles/12584461-developer-mode-and-mcp-apps-in-chatgpt).

**GitHub Copilot:** add Arena MCP as a remote MCP server in your Copilot MCP config:

```json
"MCP_Arena": {
  "type": "http",
  "url": "https://arena-mcp.lsports.eu/arena/mcp",
  "tools": ["*"]
}
```

Copilot CLI reads this from its MCP config file, and you can also add the server interactively with the `/mcp add` command. GitHub's [Add MCP servers to Copilot](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers) page has the current file paths and steps for each Copilot surface. Sign-in and permissions work exactly as they do in Claude or Cursor: you authenticate with your ARENA360 credentials and choose read, or read and write.

{% hint style="info" %}
In most clients, developer and MCP tools are off by default and need a short enablement step before you connect.
{% endhint %}

## What you can do

Both surfaces cover TRADE, BOOST, and Coverage Hub, and both can change your TRADE setup. On your own MCP client you choose read, or read and write, at sign-in. DEFEND and ENGAGE on Arena AI stay as shown in the table above.

**TRADE.** Review and update orders, templates, odds settings, provider lists, and the trading floor:

* "Which tennis leagues am I ordering InPlay this week?"
* "Show me the margin settings on this template."
* "Which providers sit in my list for football main markets?"
* "On UAT, add the Copa Libertadores to my InPlay ordering."
* "Apply this margin on UAT. Once it looks right, apply the same change on Production."

For a change, the agent names the target package, waits for your approval, writes it, then reads it back so you can confirm it landed.

**BOOST.** Pull coverage, uptime, margin, and historical data, including questions that span products in one request:

* "Which tennis leagues have the best InPlay coverage this week, and which of them am I already ordering?" (BOOST analysis, then TRADE ordering data)
* "Show where my margin trails competitors, and which templates those markets sit in." (BOOST, then TRADE configuration)
* "Compare provider margins last week and tell me which providers I would want in my list." (BOOST, then TRADE configuration)
* "Check last month's results for this league before I decide whether to order it." (historical data, then TRADE ordering data)

The same BOOST and Coverage Hub questions work in Arena AI.

**DEFEND.** Monitor bets, check exposure against your limits, and look up player risk:

* "Which bets are waiting for a decision right now?"
* "Show the platform limits on my InPlay football markets."

**ENGAGE.** Tips and real-time match data:

* "What tips are live for today's football?"
* "Show the latest incidents for this fixture."

**Coverage Hub.** Ask what LSports covers — sports, locations, competitions, markets, and providers — plus livescore scout coverage, settlement coverage, and spotlight. This is inventory, separate from BOOST performance numbers:

* "Which providers cover the most Football InPlay fixtures over the last month?"
* "Does this competition have settlement coverage?"

## Package-aware

Your account can hold more than one package (for example QA, UAT, and Production). One connection covers all of them, so you choose the target as part of your request: "Show me the margin settings on UAT, not production."

If you have one package, the agent uses it automatically. If you have several and do not name one, it asks which you mean. Rehearse changes on QA or UAT before you repeat them on Production.

## Permissions

Both Arena AI and the MCP connection can read your account and change your TRADE setup.

* **Read.** The agent explores and analyzes your account. It cannot place orders, change configuration, or edit settings. On your own MCP client you choose this at sign-in.
* **Read and write.** The agent can change your setup. On your own MCP client you choose this at sign-in. On Arena AI it is available with the Arena AI role. Either way, the agent shows each change and its target package, waits for your approval before anything is written, then reads the result back so you can verify it.
* **Your ARENA360 role still applies.** Neither surface gives you more than you can already do in ARENA360.

**Arena AI needs a role, and only an admin can add it.** The MCP connection works with any ARENA360 user. Arena AI does not: an admin has to add the **Arena AI** role to each user who should reach it. See [Granting access](#granting-access) for the steps. Access starts on the user's next sign-in, and removing the role removes access. Arena AI coverage stays as shown in the Arena AI column above.

## Need help?

Reach out to your LSports CSM and we will walk you through your first connection.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lsports.eu/u/getting-started/arena360-ai-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.