POST request to /nodes provisions a fresh compute node on your account. The endpoint returns immediately with a node ID and an initial status of provisioning — the node is being prepared in the background and will transition to running once it is ready to accept connections. You can poll GET /nodes/ to track that transition.
Endpoint
Request Headers
string
required
Your nodepick.ai API key, passed as a Bearer token. Example:
Bearer YOUR_API_KEYstring
required
Must be
application/json for all requests to this endpoint.Request Body
string
Human-readable display name for the compute node.
number
default:"1"
Number of vCPUs to allocate. Minimum:
1.number
default:"1"
System RAM in gigabytes (GB). Minimum:
1 GB.number
default:"10"
Disk storage in gigabytes (GB). Minimum:
10 GB.string
VPC network ID (e.g.
vpc-1009-xh9rdu or UUID) to deploy node into. Defaults to account’s default VPC.string
Specific compute host UUID to pin placement. If omitted, the scheduler selects the cheapest active host meeting requirements.
string
Target region or datacenter (e.g.
us-west-1, fmt1).Request Example
Response
A successful request returns HTTP201 Created with a JSON body describing the new node.
string
The unique identifier for your new node. Use this ID to inspect or delete the node in subsequent requests.
string
The initial lifecycle status of the node. This will be
provisioning immediately after creation. The node moves to running once it is fully ready.string
An ISO 8601 timestamp recording exactly when the node was created. Billing is calculated from this moment.
Response Example
Python SDK
Thenode_create() method on NodePickClient wraps this endpoint:
Billing starts the moment this endpoint returns
201. Per-second charges accumulate until you call DELETE /nodes/ to terminate the node. Do not leave nodes running if you no longer need them.