> For the complete documentation index, see [llms.txt](https://developer.aiodds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.aiodds.com/explore/core-concepts.md).

# Core concepts

AiOdds provides sports data, bookmaker odds, real-time updates, trading workflows, and operational tools for sportsbook integrations. 

This page explains how the main concepts fit together before you start building.

## Platform model

AiOdds is built around five core layers:

1. Basic data
2. Bookmaker Odds data
3. Real-time delivery
4. AI Trading
5. Customer operations

Each layer supports a different part of a sportsbook integration.

### Basic data

Basic data is the foundation of an odds integration. It includes sports, tournaments, locations, teams, and match metadata.

Use it to understand available events, organize your event hierarchy, and align AiOdds entities with your internal systems.

Common objects include:

* Sports
* Locations
* Tournaments
* Teams
* Matches

### Bookmaker Odds data

Odds data includes bookmaker markets and odds for pre-match and in-play matches. Each odds record is tied to a bookmaker, a market, and one or more selections.

Depending on your product access, you can consume odds through HTTPS APIs, MQTT over WebSocket, or both.

Common objects include:

* Bookmakers
* Markets
* Pre-match odds
* In-play odds
* Settlement

Our Bookmaker Odds data has been upgraded with a new protection mechanism: [**Backup Safe Mode.**](/explore/core-concepts/backup-safe-mode.md)

This upgrade is designed to prevent odds updates from stopping during exceptional source issues, such as a bookmaker platform outage, source connection interruption, or source data becoming temporarily unavailable.

When AiOdds detects that a supported bookmaker's data has stopped updating, it can switch that bookmaker to a backup odds solution so that odds can continue to update instead of remaining stale or unavailable.

### Real-time delivery

AiOdds uses MQTT over WebSocket for live delivery. This is the right model when your product needs continuous updates instead of periodic polling.

Common real-time payloads include match updates and odds updates.

### AI Trading

AI Trading supports trading workflows that let operators generate and control their proprietary odds. Use this model when your workflow includes pricing rules, trading controls, or proprietary odds output.

This is separate from bookmaker odds.

### Customer operations

The AiOdds customer console is the operational layer for your account. It includes the main tools used to monitor services, review access, and work with support.

| Module            | Use it for                                                               |
| ----------------- | ------------------------------------------------------------------------ |
| Monitoring        | Follow live and pre-match odds, review movement, and check market state. |
| Trading           | Work with proprietary odds and trading workflows.                        |
| Subscription      | Review assigned product and data access.                                 |
| Tickets           | Contact support for issues and requests.                                 |
| API Documentation | Open product-specific technical reference material.                      |
| Live Tracker      | Review live match and event data.                                        |
| Help Center       | Find support articles and operational guidance.                          |


---

# 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://developer.aiodds.com/explore/core-concepts.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.