# List network

URL: https://docs.hanzo.ai/docs/openapi/network/get-network

> Returns the caller's org overlay network on the Zero Trust fabric.

`GET /v1/network`

> [Network →](https://docs.hanzo.ai/docs/openapi/network) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides)

|               |                                        |
| ------------- | -------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/network`      |
| **Method**    | `GET`                                  |
| **Operation** | `get_network`                          |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY` |

Returns the caller's org overlay network on the Zero Trust fabric.

The org has at most ONE overlay, projected from the edge-routers tagged with its
"org-\<org>" role attribute: nodes is the real router count and status is
"connected" once at least one router has dialed home, "provisioning" while none
has. An org with no routers gets an empty list, never a fabricated network.

The read degrades rather than erroring: a deployment with no ZT credential, and a
controller that cannot be reached, both answer 200 with an empty list so the
console's Networks page renders a clean empty state instead of an error.

## Request

`GET /v1/network` takes no parameters and no body — the credential is the whole request.

## Response

| Status    | Body                | Meaning |
| --------- | ------------------- | ------- |
| `200`     | network.networkList | ok      |
| `default` | problem-details     | refused |

`200` body — 5 fields.

| Field               | In   | Type                   | Always | Description                                                                                                                                           |
| ------------------- | ---- | ---------------------- | ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| `networks`          | body | network.networkView\[] | —      | Networks holds the org's overlay network, or is empty when the org has no edge-routers on the fabric (no nodes → no network, never a fabricated one). |
| `networks[].id`     | body | string                 | —      | ID is the org-derived id of the overlay network — the key GET /v1/network/{id} addresses.                                                             |
| `networks[].name`   | body | string                 | —      | Name is the org the overlay belongs to.                                                                                                               |
| `networks[].nodes`  | body | integer (int64)        | —      | Nodes is how many edge-routers the org has on the fabric.                                                                                             |
| `networks[].status` | body | string                 | —      | Status is "connected" once at least one of the org's edge-routers is online, else "provisioning" (routers exist but none has dialed home).            |

Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors).

## Examples

**CLI**

```bash
hanzo network list
```

**SDK**

**.ts**

```ts
import { Configuration, NetworkApi } from 'hanzoai';

const api = new NetworkApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getNetwork();
```

**.py**

```python
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import NetworkApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = NetworkApi(client).get_network()
```

**.go**

```go
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.NetworkAPI.GetNetwork(context.Background()).Execute()
if err != nil {
	return err
}
```

**.rs**

```rust
use hanzo_client::apis::{configuration::Configuration, network_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = network_api::get_network(&cfg, Default::default()).await?;
```

**.java**

```java
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.NetworkApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new NetworkApi(client).getNetwork();
```

**HTTP**

```bash
curl https://api.hanzo.ai/v1/network \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

MCP reaches **network** through the `network` tool, which names its 7 operations with its own verbs — this one among them, under a name only MCP declares. `describe` explains any of them:

```bash
curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_networks"
         }
       }
     }'
```

---

[Network API](https://docs.hanzo.ai/docs/openapi/network) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)