> For the complete documentation index, see [llms.txt](https://docs.sefiraat.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sefiraat.dev/networks/network-nodes/network-monitor.md).

# Network Monitor

![Network Monitor](https://2343825542-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FO0k8J7KDC5EdW6hPoarg%2Fuploads%2FUXom6AvH5P46TTqDUqFT%2Ftile_network_monitor.png?alt=media)

the Network Monitor exists to 'expose' a connected Inventory to the Network. When right-clicked, it opens up a directional interface allowing you to select which adjacent block it should expose. When selected, the contents of that inventory are then open to the Network, the exposed items will show up in [Grids](/networks/network-nodes/network-grid.md) while also allowing Nodes to request/submit items from/to the Inventory where applicable.

Currently the Monitor can access the following blocks:

* Infinity Expansion Storage Units
* Network Quantum Storage

The Monitor is a Directional Networks Node and is, therefore, compatible with the [Networks Configurator](/networks/tools/network-configurator.md)

Network Monitors are allowed to be covered using [Block Veils](/crystamae-historia/tools/block-veil.md) from Crystamae Historia

{% hint style="info" %}
*A future update will expand monitors to a far larger range of inventories*
{% endhint %}


---

# 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.sefiraat.dev/networks/network-nodes/network-monitor.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.