> 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-memory-shell.md).
# Network Quantum Storage
A Quantum Storage interface
The Network Quantum Storage is Network's attempt at deep storage.
They work similarly to Infinity Barrels.
The desired item is to be hovered over the designated spot to register it.
Items can be added manually via the input slot (green background).
Items can be withdrawn from (and a stack will be buffered in) the output slot (orange background).
Network Quantum Storages must have a [Network Monitor](/networks/network-nodes/network-monitor.md) attached and pointing towards it for the items in it to be exposed.
### Storage Sizes
Quantum Storages
| Card (left to right above) | Max Items Stored |
| -------------------------- | ---------------- |
| Storage (4k) | 4,096 |
| Storage (32k) | 32,768 |
| Storage (262k) | 262,144 |
| Storage (2m) | 2,097,152 |
| Storage (16m) | 16,777,216 |
| Storage (134m) | 134,217,728 |
| Storage (1b) | 1,073,741,824 |
| Storage (∞) | Max Value |
{% hint style="info" %}
Option to automatically void excess incoming items has been added, to avoid clogging up your Network.
{% 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-memory-shell.md?ask=&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.
