> 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.1-what-is-fanpass.md). # 5.1 What is FanPass? While OneFootball has built one of the largest and most engaged fanbases in sports media, the company’s next chapter is focused on transforming passive fandom into active digital ownership. This transition began with OneFootball Club, a community layer for fans who want more than football content, including recognition for how they participate, rewards for the value they create, and a profile that reflects their continuous relationship with the game. FanPass is the next evolution of that foundation: a portable football identity that turns scattered fan activity into a persistent record fans can carry and grow across the global football ecosystem. A fan creates a FanPass and can progressively connect it with the platforms where their fandom happens: football clubs, games, commerce, communities, and the OneFootball app. As those connections grow, isolated actions become verified fan signals. A prediction, completed challenge, or purchase can contribute to the same unified identity rather than disappearing as a one-off interaction. Over time, those signals build the fan’s profile, including traits, badges, and credentials. Together, they create a consented record of fandom that the fan can see, control, and share on their own terms. That record can then be used to unlock access and personalized experiences wherever FanPass is integrated. For partners, FanPass provides the infrastructure they would otherwise have to build alone – identity, reputation, eligibility, consent, and wallets all in one integration. A club, brand, or app can recognize a verified fan on the first contact instead of starting every relationship at zero. As such, FanPass provides the football ecosystem a common layer to build on. --- # 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.1-what-is-fanpass.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.