> For the complete documentation index, see [llms.txt](https://docs.onefootballclub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onefootballclub.com/5-introducing-fanpass/5.4-fanscore.md). # 5.4 FanScore FanScore is the reputation layer inside FanPass: a dynamic measure of fan participation curated from verified signals across different verticals within football. Unlike traditional loyalty programs, FanScore is behavioral and dynamic, capturing data across ecosystems rather than within a closed platform. A fan’s standing grows through meaningful participation, but can fade if it is not maintained. Fandom is not one-size-fits-all, therefore FanScore measures fandom across multiple dimensions. A fan may be a Consumer, Amplifier, Creator, Collector, Gamer, Analyst, or a combination of several roles. The fan who buys every shirt shouldn’t be recognized the same as the fan who attends every match or who publishes a tactical analysis of every game. Each fan contributes value in their own way, and FanScore is designed to recognize those differences. It translates visible fandom into a score that can be understood and carried by the fan, while preserving the diversity of football fandom that makes the sport unique. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.onefootballclub.com/5-introducing-fanpass/5.4-fanscore.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.