# List services

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

> Returns the Zero Trust edge services the caller's org owns.

`GET /v1/network/services`

> [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/services` |
| **Method**    | `GET`                                      |
| **Operation** | `get_network_services`                     |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`     |

Returns the Zero Trust edge services the caller's org owns.

One row per real ZT edge service tagged with the org's "org-\<org>" role
attribute: mtls is "required" when the service mandates end-to-end encryption and
"enabled" otherwise (the fabric always mutually authenticates every link), and
status is "active" because a listed service is a configured, dialable entry. A
service tagged for another org, or tagged for none, is invisible here.

Unlike the network and router reads this does NOT degrade: an unconfigured
deployment answers 503 and an unreachable controller surfaces the upstream's
status, so a mesh page never renders "no services" for a fabric it simply could
not read.

## Request

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

## Response

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

`200` body — 5 fields.

| Field                | In   | Type                | Always | Description                                                                                                                                                  |
| -------------------- | ---- | ------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `services`           | body | network.meshView\[] | —      | Services is one row per ZT edge service tagged with the caller's org role.                                                                                   |
| `services[].id`      | body | string              | —      | ID is the ZT edge service's id.                                                                                                                              |
| `services[].mtls`    | body | string              | —      | Mtls is "required" when the service mandates end-to-end encryption, else "enabled" — the fabric mutually authenticates every link, so it is never truly off. |
| `services[].service` | body | string              | —      | Service is the edge service's name.                                                                                                                          |
| `services[].status`  | body | string              | —      | Status is "active": a listed service is a configured, dialable mesh entry.                                                                                   |

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

## Examples

**CLI**

```bash
hanzo network services get
```

**SDK**

**.ts**

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

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

**.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_services()
```

**.go**

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

resp, _, err := client.NetworkAPI.GetNetworkServices(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_services(&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).getNetworkServices();
```

**HTTP**

```bash
curl https://api.hanzo.ai/v1/network/services \
  -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)