> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/nfh-fabric/participants.md). # Participants Who's on NFH fabric and what they do. NFH fabric is permissionless. If you can speak the protocol, you can join. Participants take different shapes depending on what they do on the network. ## Buyers / consumer-side apps Apps that help users discover, choose, and transact across the network. A ride-hailing app, a savings app, a procurement portal, an agent-driven trading client. ## Providers / seller-side apps Apps that publish offerings and fulfil them. A restaurant, a logistics provider, an energy supplier, a data marketplace, a credentialing authority. ## Tokenisation instances Operators that run a token runtime — central banks, regulated financial institutions, sector operators, hosted services (such as those Lium runs). Each instance speaks the federation protocol and federates value with other instances. ## Credential issuers Authorities that issue verifiable credentials — universities, regulators, professional bodies, certification authorities, employer organisations. ## Agents Autonomous software, with the same rights and accountability as humans and businesses. [Read more →](/nfh-fabric/agents.md) ## Network facilitators Organisations that stand up sector-specific or jurisdiction-specific networks on top of NFH fabric — defining policies, onboarding participants, governing local rules. Facilitators consume NFH fabric's central services and reference software to launch quickly with predictable compliance. ## The NFH Foundation Operates NFH fabric's central services (Registry, Cataloguing, Discovery, Observability & Audit anchors), publishes the protocols, and stewards the reference software. --- # 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://docs.nfh.global/nfh-fabric/participants.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.