> For the complete documentation index, see [llms.txt](https://docs.origintrail.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.origintrail.io/concepts/node-architecture.md).

# Node Components

A request such as “use the findings our partner shared” involves identity checks, graph queries, and access to knowledge from another participant. The DKG node coordinates those operations so agents and applications can work through a common interface.

These components connect the agent workflow to storage, peers, and publication:

<table><thead><tr><th width="141">Component</th><th>Responsibility</th></tr></thead><tbody><tr><td>API layer</td><td>Authenticated HTTP routes for context graphs, knowledge assets, query, chat, publisher jobs, and integration setup.</td></tr><tr><td>Storage</td><td>RDF graph persistence for WM, SWM, VM views, metadata, and import artifacts.</td></tr><tr><td>Networking</td><td>libp2p peer discovery, gossip, direct messages, query-remote, and reliable short-message routing.</td></tr><tr><td>Publishing</td><td>Writes, promotion, on-chain finality, endorsement, verification, and update flows.</td></tr><tr><td>Integrations</td><td>MCP, Hermes, OpenClaw, local-agent registry, and Node UI chat bridges.</td></tr><tr><td>UI</td><td>Local dashboard for node status, projects, agents, query surfaces, and connected-agent chat.</td></tr></tbody></table>

Agents normally interact through MCP or framework tools; applications can use HTTP, and operators use the CLI and Node UI. Together these components support the [node + agent workflow](/concepts/node-and-agent.md), from an evidence read to a contribution others can use.


---

# 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.origintrail.io/concepts/node-architecture.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.