> For the complete documentation index, see [llms.txt](https://fabco.gitbook.io/dappy-spec/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fabco.gitbook.io/dappy-spec/glossary/dappy-network-and-network-members-or-agents.md).

# Dappy Network and network members (or agents)

The Dappy network is a group of agents (agent is a generic term for “individual” or “company”), each agent should be independant one with another just like the nodes of a blockchain platform. A Dappy network is not a blockchain or smart contract platform, it is a layer or interface that sits between arbitrary clients and the blockchain platform itself. The members of a Dappy network must run a read-only or active node of the same blockchain platform, and therefore share the same state.

A Dappy network may therefore represent a portion of the nodes of a blockchain platform. The purpose of a Dappy network is not primarily to maintain or participate in a blockchain platform, but it is to be available for client requests, and so to expose many endpoints that clients will be able to query simultaneously.

In the current Dappy system, a network member must run the [Dappy node](https://github.com/fabcotech/dappy-node/) program connected to the [rnode or RChain node](https://github.com/rchain/rchain) program instance.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fabco.gitbook.io/dappy-spec/glossary/dappy-network-and-network-members-or-agents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.