# Providers

Providers are the integrations CrossWatch (CW) talks to.

Connect providers in **Settings → Authentication**.

Then pick two providers in a **pair**.

{% hint style="info" %}
Recommended first setup: **1 media server + 1 tracker**. Validate one clean run. Then add more.
{% endhint %}

### How providers fit together

* **Providers**: credentials + URLs needed to call APIs.
* **Pairs**: the rules (source, target, features, safety settings).
* **Runs**: manual or scheduled executions of your pairs.

Providers do nothing on their own.

Pairs are what sync and scrobble.

### Browse provider docs

* [Authentication](/crosswatch/providers/authentication.md)
* [Auth: Media servers](/crosswatch/providers/authentication/auth-media-servers.md)
* [Auth: Trackers](/crosswatch/providers/authentication/auth-trackers.md)
* [Auth: Others](/crosswatch/providers/authentication/auth-others.md)
* [Metadata](/crosswatch/providers/metadata.md)
* [Synchronization](/crosswatch/providers/synchronization.md)

### Tips

* Add [Metadata](/crosswatch/providers/metadata.md) early. Better IDs mean better matching.
* Connect only what you use. Each provider adds API calls and state.
* Prefer URLs reachable from the CW host/container (LAN IP > hostname).
* If something feels risky, start with **one-way** + **dry run** in your first pair.

### Next steps

* Connect credentials: [Authentication](/crosswatch/providers/authentication.md)
* Set up your first pair: [Configure Pairs](/crosswatch/configure-pairs.md)
* Decide between periodic syncing and real-time plays: [What do you need?](/getting-started/first-time-setup/what-do-you-need.md)


---

# Agent Instructions: 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/crosswatch/providers.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.