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

# Build with agents

Patterns and primitives for building agent-native applications on NFH fabric.

Agents are first-class participants on NFH fabric. They hold identities, sign transactions, hold tokens, earn reputation, and are accountable for what they do.

[**Read the agents concept page →**](/nfh-fabric/agents.md)

## Common patterns

### Agent-owned account

Provision a DID for the agent. Issue it a capability credential. Fund a Tokenisation account in its name. The agent transacts under its own identity, with audit trails attached.

### Delegated authority

Issue a time-bounded, scope-bounded credential from a human or organisation to an agent. The agent acts under that delegation; revocation is a one-call action.

### Human-in-the-loop gating

Use Network Adapters Edge policy plug-ins to require human approval for actions above a threshold (value, risk, counterparty).

### Multi-agent commerce

Discovery via MCP. Contracts via Network Adapters Edge. Settlement via Tokenisation. Audit via Observability & Audit. Agents brokering with agents, end to end.

## Standards

MCP for discovery and service consumption. W3C Verifiable Credentials for capability and delegation. OpenTelemetry for action tracing.

## What to read next

* [Credentialling Edge](/product-documentation/products/vc-on-edge.md)
* [Tokenisation](https://docs.finternetlab.io/)
* [Discovery Edge](/product-documentation/products/discovr.md)
* [The agent data marketplace use case](/use-cases/agent-data-marketplace.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/agents.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.