> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/odds-and-predictions.md).

# Odds and predictions

{% hint style="info" %}
These tutorials cover football-specific odds usage, including the bookmaker directory and market availability reference. For the dedicated Odds API endpoint reference covering all sports, see the [Odds API space](https://docs.sportmonks.com/v3/odds-api/getting-started/welcome).
{% endhint %}

In this tutorial, we’re going to discuss odds & predictions. Odds are one of our football API's most used features. With this data feature, you can build an odds portal or a match page with odds. Next to odds, we offer a predictions API as a separate add-on. You will need a subscription with this add-on to access our prediction model. We’ll discuss what you can do with the prediction API and how it works.

Let’s start at the beginning: bookmakers and markets.

{% content-ref url="/pages/H7lt44mqZdpmDJSZLR1u" %}
[Bookmakers](/v3/tutorials-and-guides/tutorials/odds-and-predictions/bookmakers.md)
{% endcontent-ref %}

{% content-ref url="/pages/Q6xi72N5Un6xcDMD26LR" %}
[Markets](/v3/tutorials-and-guides/tutorials/odds-and-predictions/markets.md)
{% endcontent-ref %}

{% content-ref url="/pages/XHHgGMqQ7u6u5JxMcQKO" %}
[Pre-match odds](/v3/tutorials-and-guides/tutorials/odds-and-predictions/pre-match-odds.md)
{% endcontent-ref %}

{% content-ref url="/pages/hMscwhrGg2pcjfjRWxBn" %}
[Live(Inplay) odds](/v3/tutorials-and-guides/tutorials/odds-and-predictions/live-inplay-odds.md)
{% endcontent-ref %}

{% content-ref url="/pages/shE27b1FXVLFF7YSo05r" %}
[Predictions](/v3/tutorials-and-guides/tutorials/odds-and-predictions/predictions.md)
{% endcontent-ref %}


---

# 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.sportmonks.com/v3/tutorials-and-guides/tutorials/odds-and-predictions.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.