> 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/about-nfh-offerings/readme.md). # Networks for Humanity offerings Networks for Humanity — an international network of labs building open, interoperable infrastructure for the intelligent era. Networks for Humanity builds and stewards a family of open infrastructural products. At the base is **NFH fabric** — the open network for value exchange — and around it a set of infrastructure components and packaged, production-ready services that run *on* NFH fabric. ## The offerings at a glance


NFH fabric	The open network for value exchange — discovery, contracting, settlement, identity, and trust.	Welcome to NFH fabric
UNITS	Programmable, transferable units of value — tokenisation.	https://docs.finternetlab.io/
DeDi	Decentralised Directory for public registries.	https://dedi-global.gitbook.io/docs
Vouch	Purpose-bound digital value — value that carries its own rules of use.	https://vouch.finance/
Pincer	Gradient guarantees and arbitration — trust as a continuous, contextual contract.	https://pincer.network/

--- # 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/about-nfh-offerings/readme.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.