> For the complete documentation index, see [llms.txt](https://emibergo.gitbook.io/redischat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emibergo.gitbook.io/redischat/advanced-use-case.md).

# Advanced use-case

Since RedisChat doesn't rely on the proxy (but behaves like it is), the plugin has a lot of applications:

Multi-proxy - use RedisChat to **sync chats through different proxy servers**. Ex. proxy 1 has a spigot1 server and proxy2 has a spigot2 server. You can sync those 2 spigot servers simply by setting the same Redis server address/URI

Multiple multi-spigot servers - You have a skyblock with 200 spigot instances and a survival with 4 instances. You can synchronize skyblock server's chats by setting the same **cluster-id** and the same with survival instances

Single spigot - using it on a single instance is the simpler setup. It is recommended to use Redis anyway but it is possible to set a Mysql storage or file storage for RedisChat data


---

# 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://emibergo.gitbook.io/redischat/advanced-use-case.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.