> 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/products.md).

# Capabilities of NFH fabric

This section documents the services in production that makes up NFH fabric — each component's capabilities, operator how-tos, commands, and repositories.

NFH fabric is **open for anyone to build on**. The products split into two groups: a small set of **core components** that every network needs, and a growing set of **accelerators** you adopt as you need them.

## Core NFH fabric components

The foundation of any NFH fabric network — verifiable identity.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>REGISTR</strong></td><td>The NFH fabric Registry Service — verifiable network identity &#x26; trust for every participant. Built on DeDi.</td><td><a href="/product-documentation/products/registr.md">REGISTR — build trusted networks</a></td></tr></tbody></table>

Catalog publishing isn't a separate product — a provider self-hosts and self-signs its own catalog on infrastructure it already controls. See [Catalog Publishing and Discovery](/build/creating-a-network/catalog-publishing-and-discovery.md) for the full guide.

## Accelerators

Adopt these as your network grows — discovery, credentials, connectivity, schemas, tokenised value, and audit.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>DISCOVR</strong></td><td>Real-time, multi-modal discovery engine that crawls and indexes every self-published catalogue.</td><td><a href="/product-documentation/products/discovr.md">DISCOVR — find catalogs</a></td></tr><tr><td><strong>VC on Edge</strong></td><td>Issue &#x26; verify Verifiable Credentials at the edge — powered by OpenCred. Keys never leave the issuer.</td><td><a href="/product-documentation/products/vc-on-edge.md">VC on Edge — prove anything</a></td></tr><tr><td><strong>ONIX</strong></td><td>Protocol adapter middleware between consumer and provider nodes — signing, validation, compliance.</td><td><a href="/product-documentation/products/onix.md">ONIX — connect to everything</a></td></tr><tr><td><strong>Schema browser</strong></td><td>Browse and reference the NFH fabric schema registry — the shared object models every node speaks.</td><td><a href="https://schema.beckn.io">https://schema.beckn.io</a></td></tr><tr><td><strong>Tokenisation</strong></td><td>Any form of value as a programmable, transferable token, federated across instances — from the Finternet Lab.</td><td><a href="https://docs.finternetlab.io/">https://docs.finternetlab.io/</a></td></tr><tr><td><strong>Observability &#x26; Audit</strong></td><td>End-to-end transaction tracing, network telemetry, and verifiable audit trails.</td><td><a href="/product-documentation/products/observability-audit.md">Observability &amp; Audit</a></td></tr></tbody></table>

{% hint style="info" icon="handshake" %}

#### Need help? Reach out to us <https://support.nfh.global/>

{% endhint %}


---

# 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/products.md?ask=<question>&goal=<user_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.