> 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.2-vision-the-universal-football-identity-layer.md). # 5.2 Vision: The universal football identity layer The vision for FanPass is a universal identity layer for football: a global standard that can move with the fan across clubs, apps, sponsors, and communities. This kind of identity layer cannot be built as a closed system. The value of identity comes from connectivity. And like any network, its value compounds through openness, interoperability, and repeated use. That is why FanPass is built from the bottom up. The fan is the only participant that naturally crosses every silo in football. A single supporter may interact with a club, ticketing provider, game, merchandise store, sponsor, and community within the same matchday. FanPass is grounded in that reality: one fan, one identity, strengthened by every connected experience. Over time, this creates a network effect no single institution could build alone. Each new fan adds more context. Each new partner adds more utility. Each new interaction makes the identity layer more valuable for the fan and for the ecosystem around them. --- # 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.2-vision-the-universal-football-identity-layer.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.