> For the complete documentation index, see [llms.txt](https://docs.escs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.escs.io/master.md). # Introduction Welcome to the escs. Here you will find some general words about the escs and how you can use it. ### Fun with ESCS ✨ **escs** is short for **Embedded Social and Competition Services**. \ What started as an esports platform has evolved into a **decentralized distribution network** and **publishing platform** for games. A simple escs integration does three things: 1. **Adds a Competition Hub to your game**\ Players and you can run tournaments and events, with built-in social features. 2. **Gets your game discovered** \ Your game becomes connected to the escs distribution network of digital platforms and creators - reaching **billions of players**. 3. **Unlocks a new revenue stream**\ escs gives you half of everything escs makes through partnerships, entry fees, sponsoring. escs is designed with developers in mind - integration aims to be extremely easy. \ Basic integration can be done in 15 minutes. *** **Integration steps.** 1. **Register and create your game** in escs developer dashboard. 1. Use our sandbox demo environment for the first steps: [https://client.demo.escs.io](https://client.demo.escs.io/) 2. When everything works smoothly move to the prod at [https://client.escs.io](https://client.escs.io/) 2. **Choose the plugin** for your game engine (select it from the left-hand menu) and follow the integration instructions. That’s it — you’re ready to go. We’re trying to keep the system convenient, flexible, and powered by that rare artifact known as **“common sense.”** \ Still, we know perfection is a myth (like a bug-free release). \ If anything is unclear or you spot an opportunity to improve the docs, please tell us here: [https://support.escs.io](https://support.escs.io/). --- # 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.escs.io/master.md?ask=&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.