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

# DEFEND

- [DEFEND Overview](https://docs.lsports.eu/u/defend/defend.md): Risk management & exposure control
- [Capabilities](https://docs.lsports.eu/u/defend/capabilities.md)
- [Bet Monitor](https://docs.lsports.eu/u/defend/bet-monitor.md): Real-time bet monitoring and surveillance
- [Bets](https://docs.lsports.eu/u/defend/bet-monitor/bets.md): Real-time view of all betting activity
- [Risk Controls](https://docs.lsports.eu/u/defend/risk-controls.md): Configure platform-wide and entity-specific risk limits
- [Platform Limits](https://docs.lsports.eu/u/defend/risk-controls/platform-limits.md): Configure global platform-wide betting limits
- [Entity Limits](https://docs.lsports.eu/u/defend/risk-controls/entity-limits.md): Configure limits at sport, competition, or fixture level
- [Player Intelligence](https://docs.lsports.eu/u/defend/step-4-player-management.md): Manage individual player limits and restrictions
- [Player Intelligence Dashboard](https://docs.lsports.eu/u/defend/step-4-player-management/player-intelligence-dashboard.md): A unified hub for reviewing player history, risk profiles, and taking action.
- [Player List](https://docs.lsports.eu/u/defend/step-4-player-management/player-list.md)
- [Player Platform Limits](https://docs.lsports.eu/u/defend/step-4-player-management/player-platform-limits.md)
- [Player Entity Limits](https://docs.lsports.eu/u/defend/step-4-player-management/player-entity-limits.md)
- [Operational Setup](https://docs.lsports.eu/u/defend/step-3-operational.md)
- [Outright League Markets Support](https://docs.lsports.eu/u/defend/step-3-operational/outright-leagues-support.md)
- [Integration Guide](https://docs.lsports.eu/u/defend/integration-guide.md)
- [Authentication](https://docs.lsports.eu/u/defend/integration-guide/authentication.md)
- [API Reference](https://docs.lsports.eu/u/defend/api.md): This documentation describes the available API endpoints for customer integration process and bet-slips interactions
- [WebSocket Connection](https://docs.lsports.eu/u/defend/websocket-connection.md): Connect to the RMS-Socket service to receive real-time bet approval updates via secure WebSocket.
- [Quick Start & Best Practices](https://docs.lsports.eu/u/defend/websocket-connection/quick-start-and-best-practices.md): Get connected to the RMS-Socket service quickly and learn recommended practices for production environments.
- [Code Examples](https://docs.lsports.eu/u/defend/websocket-connection/code-examples.md): Complete code examples for connecting to the RMS-Socket WebSocket service.
- [Error Handling](https://docs.lsports.eu/u/defend/websocket-connection/error-handling.md): Error codes and troubleshooting guide for RMS-Socket connections.
- [FAQ](https://docs.lsports.eu/u/defend/faq.md): Frequently asked questions about DEFEND


---

# 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/defend.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.