> 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/endpoints-and-entities/endpoints/team-rankings-beta.md).

# Team Rankings - beta

{% hint style="danger" %}
This is currently a beta feature. Please contact our support team if you're interested in joining the beta
{% endhint %}

### 🧠 Team Rankings (Beta)

**Team Rankings** is a premium data feature that delivers historical and daily-updated **club rankings**, using an Elo-based model. It helps you evaluate club strength over time, whether for pre-match previews, performance modelling, or form-based content.

Unlike static league tables, Team Rankings offer a dynamic strength score that evolves daily, based on match results and opponent strength.

It’s ideal for betting platforms, match preview tools, and advanced stat-driven applications.

<figure><img src="https://3469464275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9zsNGu3HAzSnl5DWBD3Y%2Fuploads%2FYPDaCjMDnJjafBiqgysH%2F11-05-26-team%20Rankings%20-%20beta-v1.webp?alt=media&amp;token=3094996f-f4a1-4029-9467-df0962737e7c" alt=""><figcaption></figcaption></figure>

#### 📊 What’s Included?

Sportmonks’ team ranking model uses **Elo ratings** and data going back to **2005**. Rankings are updated daily at **00:00:00 UTC** and include:

* 🔢 **Current rank** – Daily team placement based on Elo
* 📆 **Date** – Rankings are available per day, from 2005 to today
* 📈 **Scaled score** – A normalized score between 0–100
* 🏷️ **Team ID** – Linked to the team object
* 🪪 **Ranking ID** – Unique identifier for the entry

{% hint style="danger" %}
Rankings are historical only. There are **no future or projected rankings** available.
{% endhint %}


---

# 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/endpoints-and-entities/endpoints/team-rankings-beta.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.