> For the complete documentation index, see [llms.txt](https://gitbook.mor.lumerin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.mor.lumerin.io/conceptual-architecture/node-architecture.md).
# Node Architecture
## Overview:
* The goal of this architecture is to create a network of hosted models and agents that can be accessed by any node in the network.
* Nodes will be compensated for services provided and agents can be monetized like apps.
## Notes:
* Morpheus will come packaged with a default chat agent and a lightweight web3 model
* Each agent has its own contract and is recorded in the agent registry contract
* Agents will have a reputation score or rating and can receive reviews
* Each model will have its own contract and is recorded in the model registry
* Model contracts have IPFS pointers, versioning and seed node stores
* Models will have a reputation score or rating and can receive reviews
* Peers are needed for Pretty Good Verification (PGV) and for routing interfaces to the requesters
---
# 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://gitbook.mor.lumerin.io/conceptual-architecture/node-architecture.md?ask=&goal=
```
`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.