> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/compute/flexvm/creating-a-cloud-and-nodes.md).

# Creating a Cloud and Nodes

## Create a Cloud via the API

Use the `POST /v3/flexVM/clouds` endpoint with a JSON body.

**Example request:**

```http
POST /v3/flexVM/clouds
Host: api.i3d.net
PRIVATE-TOKEN: YOUR_API_KEY
Content-Type: application/json

{
  "name": "My private cloud",
  "description": "A cloud I would like to use to create VMs in.",
  "site": "frmtl1",
  "instance_type": "bm9.hmm.gpu.4rtx4000.64"
}
```

{% hint style="info" %}
The `instance_type` property indicates the type of Bare Metal servers to use for your Private Cloud.

Currently, the available `instance_type` values are:

* `bm7.hmm.8`
* `bm9.hmm.gpu.4rtx4000.64`

More Bare Metal instance types will be available in the future, once they are validated for VM usage.

[Detailed information on the Bare Metal instance types](https://docs.i3d.net/compute/flexvm/pages/Fln1gVNvtLe9RL65jFMq#id-3.-fm-instance-type).
{% endhint %}

{% hint style="info" %}
Response (201 Created) returns the created Cloud object.
{% endhint %}

{% hint style="warning" %}
A 409 Conflict is returned when a Cloud with the same name already exists.
{% endhint %}

## Deleting a Cloud

Use the `DELETE /v3/flexVM/clouds/{cloudUuid}` endpoint.

**Example request:**

```http
DELETE /v3/flexVM/clouds/{cloudUuid}
Host: api.i3d.net
PRIVATE-TOKEN: YOUR_API_KEY
```

{% hint style="info" %}
Response (204 No Content) is returned on success.
{% endhint %}

{% hint style="danger" %}
A Cloud cannot be deleted while it still has active VMs.
{% endhint %}

## Scaling Nodes

Nodes are the bare-metal servers that provide the capacity for your Cloud's VMs. You scale a Cloud by adding or removing Nodes. New Nodes use the Cloud's instance type and location, so no request body is required.

### Add a Node

Use the `POST /v3/flexVM/clouds/{cloudUuid}/nodes` endpoint.

**Example request:**

```http
POST /v3/flexVM/clouds/{cloudUuid}/nodes
Host: api.i3d.net
PRIVATE-TOKEN: YOUR_API_KEY
```

{% hint style="info" %}
Response (201 Created) returns the new Node object. The Node is provisioned asynchronously and becomes available to host VMs once provisioning completes; retrieve it with `GET /v3/flexVM/clouds/{cloudUuid}/nodes/{nodeUuid}`.
{% endhint %}

### Remove a Node

Use the `DELETE /v3/flexVM/clouds/{cloudUuid}/nodes/{nodeUuid}` endpoint.

**Example request:**

```http
DELETE /v3/flexVM/clouds/{cloudUuid}/nodes/{nodeUuid}
Host: api.i3d.net
PRIVATE-TOKEN: YOUR_API_KEY
```

{% hint style="info" %}
Response (202 Accepted) is returned — the Node is released asynchronously.
{% endhint %}

{% hint style="warning" %}
A 409 Conflict is returned when the Node still hosts active VMs (`node_has_vms`) — move or delete those VMs first — or when the Node is not in a deletable state (`node_not_running`), e.g. it is still provisioning or already being removed.
{% 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.i3d.net/compute/flexvm/creating-a-cloud-and-nodes.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.