> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/profile/ratings.md).

# Ratings

The Ratings tab combines scores read back from your connected providers after synchronization. It helps you see both your ratings and differences between providers.

### Summary

The cards at the top show:

* **Ratings**, total ratings and your average score
* **Everywhere**, ratings present on every relevant provider
* **Missing**, ratings missing from one or more providers
* **Conflicts**, items where provider scores differ

### Find and filter ratings

You can filter by:

* Search
* Media type, Movies, Shows, Seasons or Episodes
* Provider
* Rating score
* Coverage, **Any coverage**, **Missing somewhere**, **On every provider**, or **Scores differ**

The score filter can be used to focus on a specific rating value.

### Views

Ratings supports:

* **Timeline**
* **Grid**
* **List**

You can choose 24, 48 or 96 items per page.

Provider badges show where a rating was found. When an item is marked as a conflict, the scores stored by its providers are not identical.

### Remove ratings

If your account has write permission, you can select ratings and remove them from selected providers.

You can select individual items, the visible page, or all matching results before choosing the provider action.

### Related pages

* Overview
* History
* Watchlist
* Collections


---

# 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://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/profile/ratings.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.
