> 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/blueprint-architecture/sync/_mod_anilist/overview.md).

# overview

This is the **AniList sync module** used by the orchestrator. It is not the setup/auth guide.

{% tabs %}
{% tab title="End users" %}

### What it supports

This module can sync:

* [Watchlist](/blueprint-architecture/sync/_mod_anilist/watchlist.md)
* [Ratings](/blueprint-architecture/sync/_mod_anilist/ratings.md)

It does not support:

* History

AniList watchlist maps to the **Planning** list.

AniList ratings use media-level scores.

Both features are anime-only.

Feature semantics live here:

* [Watchlist (engine-level)](/blueprint-architecture/sync/engine-level-features/watchlist.md)
* [Ratings (engine-level)](/blueprint-architecture/sync/engine-level-features/ratings.md)

### Setup links

* [Auth: AniList](/crosswatch/providers/authentication/auth-trackers/auth-anilist.md)
* [Adapter: AniList](/crosswatch/providers/synchronization/adapter-anilist.md)
* [AniList pair options](/crosswatch/configure-pairs/anilist-pair-options.md)
* [Anime ID Mapping](/crosswatch/providers/metadata-id-mapping/anime-id-mapping.md)

### Matching notes

AniList is anime-first.

Cross-provider matching can be messy.

Use **Anime ID Mapping** for the most reliable matches.

When AniList can receive writes, **Anime-only sync** is the safest option for mixed libraries.

Read: [Provider specifics](/blueprint-architecture/orchestrator/provider-specifics.md).
{% endtab %}

{% tab title="Power users" %}

### Entry point

* `sync/_mod_ANILIST.py`

### Feature modules

* watchlist → `providers/anilist/_watchlist.py`
* ratings → `providers/anilist/_ratings.py`

### Capability highlights

* `bidirectional: true`
* `index_semantics: "present"`
* `provides_ids: true`
* `observed_deletes: false`
* `watchlist_add: true`
* `watchlist_remove: true`
* `ratings_update: true`
* `ratings_remove: true`

<details>

<summary>Capabilities (raw)</summary>

```json
{
  "bidirectional": true,
  "index_semantics": "present",
  "observed_deletes": false,
  "provides_ids": true,
  "watchlist_add": true,
  "watchlist_remove": true,
  "ratings_update": true,
  "ratings_remove": true
}
```

</details>

### State files

* `anilist_watchlist_shadow.json`

Watchlist keeps a local shadow file.

Ratings do not keep a separate AniList-specific shadow file.

### External endpoints

* `https://graphql.anilist.co`
  {% endtab %}
  {% endtabs %}


---

# 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:

```
GET https://wiki.crosswatch.app/blueprint-architecture/sync/_mod_anilist/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.