> 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/vm-service.md).

# VM Service API

The VM Service API creates and manages **virtual machines** on NeevAI infrastructure. Unlike GPU Instances — which are container-based — a VM gives you a full virtual machine with its own root disk, configurable compute, optional GPU attachment, and network configuration. Use it for workloads that need a persistent operating system, custom kernels, or a traditional server lifecycle.

VMs are scoped to a project and are built from a base **image**. Each VM has a **root disk** volume that persists independently and can be listed and inspected on its own. Once created, a VM can be started, stopped, and restarted on demand.

## What you can do

* **Virtual machines** — list a project's VMs (paginated), create a VM with a chosen compute size, root disk, optional GPU, and network settings, fetch a single VM's details, and permanently delete a VM.
* **Power lifecycle** — start, stop, and restart a VM.
* **Root disks** — list the project's root disk volumes (paginated) and fetch a single root disk by ID.
* **Images** — browse available base images and fetch a single image by ID for use when creating a VM.

Use the interactive reference below to inspect the create payload, status fields, and response schemas, and to try each endpoint directly.


---

# 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/vm-service.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.