> For the complete documentation index, see [llms.txt](https://connect.socios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://connect.socios.com/socios.com-connect.md). # Socios.com Connect Welcome to the Socios.com Connect Documentation site! {% hint style="warning" %} **2026-10-15 - ANNOUNCEMENT FOR SOCIOS.COM API DEVELOPERS** As of today, we are decommissioning the Socios.com Partner API and Socios.com Partner web app. We encourage you to rely directly on what the Chiliz Chain ecosystem can provide you. {% endhint %} ## Experience the Power of Fan Tokens on Your Platforms At the heart of our ecosystem is the belief that Fan Tokens reveal their full value when used beyond just Socios.com.\ \ Unlock a new dimension for your platform with our toolset designed to create Web3 experiences, right from your existing Web2 infrastructure. \ Our tools make integrating Fan Tokens an accessible feature for all sports fans -- and you can enrich your platform with unique Fan Token experiences, amplifying user engagement and driving the value of interaction. --- # 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://connect.socios.com/socios.com-connect.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.