> 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/product-documentation.md). # Product documentation - [Capabilities of NFH fabric](https://docs.nfh.global/product-documentation/products.md) - [REGISTR — build trusted networks](https://docs.nfh.global/product-documentation/products/registr.md): Digital ecosystems across sectors—commerce, mobility, energy, sustainability, public services, and more—need a reliable way for participants to identify,… - [Registry service benchmark](https://docs.nfh.global/product-documentation/products/registr/benchmark.md): This page summarizes a set of performance tests conducted on the Registry Service in December 2025 to understand how it behaves under different data sizes and… - [DISCOVR — find catalogs](https://docs.nfh.global/product-documentation/products/discovr.md): Welcome to the documentation for NFH fabric DISCOVR — the Discovery Service (DS) of the NFH fabric ecosystem. - [Getting started](https://docs.nfh.global/product-documentation/products/discovr/getting-started.md): This guide shows a consumer application (consumer node) how to connect to an NFH fabric DISCOVR instance and run its first discover request. - [Deploying your own Discover](https://docs.nfh.global/product-documentation/products/discovr/deploying-your-own-discover.md): How to deploy your own instance of the Beckn Discovr service, and what you need to have ready before you start. - [Usage](https://docs.nfh.global/product-documentation/products/discovr/usage.md): How to discover resources across published catalogues using the Beckn Protocol v2.0. - [Examples](https://docs.nfh.global/product-documentation/products/discovr/examples.md): Worked discover requests for each search mode. - [Test reports](https://docs.nfh.global/product-documentation/products/discovr/reports.md): Performance, reliability, and functional reports for the NFH fabric Discovery Service. - [VC on Edge — prove anything](https://docs.nfh.global/product-documentation/products/vc-on-edge.md): Issue & verify Verifiable Credentials at the edge — powered by OpenCred. All transactions run on trust. - [Concepts: VCs, DIDs, trust chains, revocation](https://docs.nfh.global/product-documentation/products/vc-on-edge/concepts.md): Background for working with OpenCred — Verifiable Credentials, DIDs, trust chains, and revocation. - [Desktop app](https://docs.nfh.global/product-documentation/products/vc-on-edge/desktop.md): Install OpenCred Desktop, import or generate a signing key, and issue your first credential. - [Docker image & API](https://docs.nfh.global/product-documentation/products/vc-on-edge/docker.md): Run the OpenCred Docker image for headless issuance and verification — cloud, on-prem, and CI/CD. Your infrastructure, your keys. - [Verifying credentials](https://docs.nfh.global/product-documentation/products/vc-on-edge/verifying.md): Four ways to verify an OpenCred credential — all running the same engine — and the common result shape. - [Security model](https://docs.nfh.global/product-documentation/products/vc-on-edge/security.md): The security guarantees OpenCred makes — and their boundaries. Start here before adopting it in production. - [ONIX — connect to everything](https://docs.nfh.global/product-documentation/products/onix.md): ONIX is an enterprise-grade middleware adapter system designed to facilitate seamless communication in any NFH fabric-enabled network. - [Observability & Audit](https://docs.nfh.global/product-documentation/products/observability-audit.md): End-to-end transaction tracing and verifiable audit trails. --- # 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/product-documentation.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.