> 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.3-mission-make-every-fan-visible.md). # 5.3 Mission: Make every fan visible Most fandom is invisible. Years of support, thousands of matches watched, hundreds of debates joined, and stacks of jerseys purchased, yet little of that history becomes a record the fans can use. The fan struggles to prove it. The club can’t fully verify it. The sponsor can’t meaningfully reward it. In the existing economy, the value is created but remains fragmented. FanPass exists to make that fandom visible. Visible to the fan, as a profile that reflects how they show up. Visible to clubs and partners, as consented context rather than demographic guesswork. And visible as value, because behavior that strengthens the football ecosystem should create recognition, access, and rewards for the person behind it. This is the shared fan and commercial mission of FanPass. Fans already create value through loyalty, attention, and participation. FanPass makes that value legible, portable, and understood. --- # 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.3-mission-make-every-fan-visible.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.