> 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/build/join-the-network.md).

# Join the network

Get an identity on NFH fabric, publish a catalogue, and transact.

Joining NFH fabric takes four steps. None of them require permission from a platform owner.

## 1. Register an identity

Use the [Registry](/product-documentation/products/registr.md) to create a DID and publish your public key. This is your verifiable identity across every NFH fabric-aligned network.

## 2. Stand up a network adapter

Run the [Network Adapters Edge](/product-documentation/products/onix.md) reference software inside your infrastructure. Configure plug-ins for signing, schema validation, policy, and audit.

## 3. Publish, discover, or both

* **Publish** — list offerings via [Catalog Publishing and Discovery](/build/creating-a-network/catalog-publishing-and-discovery.md).
* **Discover** — query the network via [Discovery Edge](/product-documentation/products/discovr.md).

## 4. Transact

Settle in any token class via the [Tokenisation](https://docs.finternetlab.io/) federation protocol. Carry credentials via [Credentialling Edge](/product-documentation/products/vc-on-edge.md). Watch your fleet and anchor audit trails via [Observability & Audit](/product-documentation/products/observability-audit.md).

***

## Next steps

* [Getting started with NFH fabric](/build/getting-started-with-fabric.md)
* [Resources and changelog](/build/resources.md)


---

# 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/build/join-the-network.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.