> For the complete documentation index, see [llms.txt](https://docs.ai.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ai.neevcloud.com/api-reference/storage.md).

# Storage API

The Storage API manages **Network Volumes** — persistent, region-local storage that you attach to GPU Instances (AI Runtimes). Network Volumes let your data, datasets, model checkpoints, and outputs survive beyond the lifetime of any single instance, so you can stop and recreate compute without losing state.

Volumes are scoped to a project. A newly created volume may report a `pending` status until its underlying persistent volume claim binds, after which it becomes available to mount.

## What you can do

* **List volumes** — page through every Network Volume in a project, with their size and current state.
* **Create a volume** — provision a new in-region Network Volume of a chosen capacity (for example, 100 GiB) for use by AI Runtimes in the project.
* **Extend a volume** — increase an existing volume's capacity. The new size must be larger than the current size; the resize is applied asynchronously.
* **Inspect a volume** — fetch a single volume by ID to read its status, capacity, and binding details.
* **Delete a volume** — remove a Network Volume when it is no longer needed.

All endpoints are nested under `/api/v1beta1/orgs/{org_id}/projects/{project_id}/volumes`. Use the interactive reference below to explore request bodies and response schemas.


---

# 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://docs.ai.neevcloud.com/api-reference/storage.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.