> 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/nfh-fabric/capabilities.md).

# Capabilities

What NFH fabric makes possible, and how it does it.

The marketing site frames capabilities as outcomes. This page maps each outcome to the protocols and services that make it real — so you can decide which subset you actually need.

## Unified discovery and publishing

An offering published once is findable across every aligned network. The producer doesn't re-list; the consumer doesn't aggregate.

**Underpinned by:** [Catalog Publishing and Discovery](/build/creating-a-network/catalog-publishing-and-discovery.md) for publishing · [Discovery Edge](/product-documentation/products/discovr.md) for querying · [Registry](/product-documentation/products/registr.md) for tying offerings to verifiable identities.

## Self-executing contracts

The contract between buyer and seller is the wire format. Terms execute and settle without an operator clearing the trade.

**Underpinned by:** [Network Adapters Edge](/product-documentation/products/onix.md) for signed, schema-validated, policy-enforced message exchange · [Tokenisation](https://docs.finternetlab.io/) for the value-side commitment chain.

## Built-in guarantees

Refunds, escrow, arbitration are protocol concerns. The network resolves them; no intermediary owns the trust surface.

**Underpinned by:** Network Adapters Edge with policy plug-ins · [Observability & Audit](/product-documentation/products/observability-audit.md) for replayable evidence. Combined with [Pincer](/about-nfh-offerings/readme.md#pincer) for underwriter-backed gradient guarantees.

## Portable reputation

Reputation is signed by counterparties, held by the subject, and verifiable by anyone. It travels because it isn't stored in someone else's platform.

**Underpinned by:** [Credentialling Edge](/product-documentation/products/vc-on-edge.md) for the verifiable-credentials substrate · Registry for the issuer / status surface.

## Instant settlement

Value moves the moment conditions are met. Atomic, deterministic, observable.

**Underpinned by:** Tokenisation — including atomic primitives (`Lock`, `Commit`, `Unlock`) and the federation protocol for cross-instance transfers.

## Selective-disclosure identity

One identity, many proofs. Prove what's needed; reveal nothing more.

**Underpinned by:** Registry (identifiers and keys) · Credentialling Edge (issuance, verification, selective disclosure).

## Agent-first interaction

Every primitive is consumable by autonomous software directly, not as a retrofit.

**Underpinned by:** [MCP-native Discovery](/product-documentation/products/discovr.md) · agent-owned identities and accounts · capability and delegation credentials.

## Network-wide observability

You can see how the network is performing without seeing what anyone is doing.

**Underpinned by:** [Observability & Audit](/product-documentation/products/observability-audit.md) for live telemetry and cryptographic anchoring.

***

## How to use this page

When designing a deployment, work backwards from the capability you need. Each capability points at the minimum service set required — adopt that subset, add others as the use case grows. NFH fabric is composable.


---

# 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/nfh-fabric/capabilities.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.