---
title: "Attach the node to a private network (a grant; body names the network)"
method: POST
path: "/preview/nodes/{name}/network"
tags: ["nodes"]
---

# Attach the node to a private network (a grant; body names the network)

`POST /preview/nodes/{name}/network`

## Request

- Base URL: `https://autoresearch.sfcompute.com`
- URL: `https://autoresearch.sfcompute.com/preview/nodes/{name}/network`
- Auth: HTTP bearer

Attach a node to a private network in your workspace - a grant, like expose_port: mutable, audited, and live (a running member converges in place within seconds; no restart). The node gets stable private addresses (the response's v4/v6), keeps them for its whole life across stop/wake/recreate/repair, and can then reach - and be reached by - every other member ON ALL PORTS: one trust zone, so joining a network is trusting its members. One network per node (v1); detach_network first to move. Attachment is placement-independent: queued and stopped nodes attach fine - a stopped member keeps its addresses and simply drops traffic (nothing wakes on mesh traffic; a wake is always an explicit command). East-west only: the mesh never carries internet transit, and public reachability stays expose_port's job. The response's data_plane says whether the mesh interface exists on the node right now. `up` means gmn0 is in the container. `converging` means the interface installs on the host's next heartbeat, normally within a few seconds; if it still reads converging after about a minute, file a ticket with the node name. `not_placed` means the node is stopped or queued and joins at its next wake. `unavailable` means the host that runs the node has no mesh support; the membership and the addresses hold, and the interface appears when the host gains mesh support or the node runs on a host that has it. Nothing on your side changes that. get_node, list_nodes, list_networks, and /v1/network from inside a member carry the same field.

## Path parameters

- `name` string, required: Node name (from `list_nodes`).

## Query parameters

- `workspace` string

## Request body

- object
  - `network` string, required: Network name (from `list_networks`; create_network mints one).

## Response `200`

The capability's JSON result.

- Result: The capability's result: the same object the MCP tool returns as structuredContent. Resources carry an `object` type discriminator and an immutable id; money is integer micro-dollars in `*_usd_micros` fields.
  - `object` string: The resource type, when the result is one resource.

## Other responses

- `400`: Malformed request: bad JSON, a parameter that does not parse, or a value outside its range. Code `invalid`.
- `401`: No bearer token, or one this API cannot verify. Code `unauthenticated`.
- `403`: Authenticated, but the token's scopes or the account's role do not reach this operation. The message names the scope word to request. Code `forbidden`.
- `404`: No such route. Code `not_found`; the body names the OpenAPI document.
- `422`: A well-formed request the platform declined: no such node, a cap reached, a state that forbids the move. The message says which, and what to do instead. Code `refused`.
- `429`: Over this door's per-customer budget. Wait `Retry-After` seconds. Code `rate_limited`.
- `500`: Our fault. Retry; if it persists, quote the request-id. Code `internal`.

---

[API](https://skmtc.dev/givemeanode/apis/autoresearch-customer-api.md) · [All operations](https://skmtc.dev/givemeanode/apis/autoresearch-customer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/givemeanode/apis/autoresearch-customer-api/revisions/f88dcb70ac6c?raw)