> 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.md). # Build - [Get started](https://docs.nfh.global/build/build.md): Build on NFH fabric — from your first transaction to standing up a whole network. Getting started, agents, and the operator playbook. - [Getting started with NFH fabric](https://docs.nfh.global/build/getting-started-with-fabric.md): A hands-on starter kit for running a live beckn network in your own environment within 10 minutes — complete with a consumer node, a provider node, and the… - [Join the network](https://docs.nfh.global/build/join-the-network.md): Get an identity on NFH fabric, publish a catalogue, and transact. - [Onboarding on the NFH fabric](https://docs.nfh.global/build/onboarding.md): Join the NFH fabric as a Network Facilitator Organisation (NFO) or a Network Participant (NP) — on the hosted dedi.global solution or by publishing files on your own domain. - [Hosted onboarding via dedi.global](https://docs.nfh.global/build/onboarding/hosted.md): Set up your network as an NFO, or register your subscriber details as an NP, on the hosted dedi.global solution. - [File-based onboarding](https://docs.nfh.global/build/onboarding/file-based.md): Publish DeDi files on your own domain — publishing your index file and registry is your onboarding, for NFOs and NPs alike. - [Worked example](https://docs.nfh.global/build/onboarding/worked-example.md): A complete file-based mobility network example - the NFO's index and reference registry, a file-based NP, and a hosted NP referenced via dedi.global lookup. - [Switching onboarding paths](https://docs.nfh.global/build/onboarding/switching-paths.md): Move an NFO or NP between the hosted (dedi.global) path and the file-based path without leaving the NFH fabric. - [Unpublishing your registries](https://docs.nfh.global/build/onboarding/unpublishing.md): Remove your registries from the NFH fabric, on either onboarding path. - [Build with agents](https://docs.nfh.global/build/agents.md): Patterns and primitives for building agent-native applications on NFH fabric. - [Creating a network](https://docs.nfh.global/build/creating-a-network.md): The operator track for standing up an open network on NFH fabric — environment, participant onboarding, policies, and building consumer and provider nodes. - [Setting up the network environment](https://docs.nfh.global/build/creating-a-network/environment.md): This section covers how a Network Facilitator Organization (NFO) sets up a new NFH fabric network using the NFH fabric Registry infrastructure on DeDi Global, and how… - [Onboarding network participants](https://docs.nfh.global/build/creating-a-network/onboarding-participants.md): Once the network registry has been created, approved NPs can be added to the network. - [Catalog Publishing and Discovery](https://docs.nfh.global/build/creating-a-network/catalog-publishing-and-discovery.md): How a Provider Node self-hosts and self-signs its catalog, and how a Discovery Service finds, verifies, and indexes it — with no centrally-run relay in between. - [Configuring network policies](https://docs.nfh.global/build/creating-a-network/network-policies.md): Once the network environment exists, the network facilitator can define rules that apply across that network. - [Creating and publishing the network manifest](https://docs.nfh.global/build/creating-a-network/network-policies/network-manifest.md): This guide explains how a Network Facilitator Organization (NFO) can create, publish, and maintain a network manifest for an NFH fabric network. - [Creating and publishing Rego policy artifacts](https://docs.nfh.global/build/creating-a-network/network-policies/rego-policies.md): This guide explains how Network Facilitating Organizations (NFOs) can author policies in Rego, package them as OPA bundles, or a single rego file, publish… - [Signing a single file](https://docs.nfh.global/build/creating-a-network/network-policies/signing-files.md): OpenSSL can create digital signatures using a private key and verify them using the corresponding public key. - [Migration Guides](https://docs.nfh.global/build/migration-guides.md): Guides for moving a Beckn Network deployment between various topologies without breaking network interoperability. - [Migrating from Beckn protocol version 1 to version 2](https://docs.nfh.global/build/migration-guides/beckn-v1-to-v2.md): A readiness checklist for moving a Beckn network participant from protocol v1 to v2 — covering DEDI registry setup, protocol and schema readiness, ONIX configuration, and business application migratio - [Migrating from the centralized Catalog Service to the decentralized catalog](https://docs.nfh.global/build/migration-guides/catalog-service-to-decentralized-catalog.md): A migration guide for networks currently publishing through CATALG's centralized publish/subscribe API, moving to the decentralized, self-hosted catalog model. - [Resources and changelog](https://docs.nfh.global/build/resources.md): Working group, changelog, repositories, and the broader resource map. --- # 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.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.