# List drives

URL: https://docs.hanzo.ai/docs/openapi/space/get-space-by-space-drives

> Lists a space's drives.

`GET /v1/space/{space}/drives`

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

|               |                                                |
| ------------- | ---------------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/space/{space}/drives` |
| **Method**    | `GET`                                          |
| **Operation** | `get_space_by_space_drives`                    |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`         |

Lists a space's drives.

Listing the drives IS listing the space's root folder, because a drive is the
first segment of a key and nothing else — so the two can never disagree the way
a drives table and the keys under it would. A space the caller's org does not
own is the same 404 an unknown name gives.

Billed per call: the balance is checked BEFORE anything is touched, so an
unfunded org is refused with nothing read, and the debit lands only once the
listing has succeeded.

## Request

1 field.

| Field   | In   | Type   | Required | Description                               |
| ------- | ---- | ------ | -------- | ----------------------------------------- |
| `space` | path | string | yes      | Space is the space's name, from the path. |

## Response

| Status    | Body            | Meaning |
| --------- | --------------- | ------- |
| `200`     | space.driveList | ok      |
| `default` | problem-details | refused |

`200` body — 4 fields.

| Field           | In   | Type               | Always | Description                                                         |
| --------------- | ---- | ------------------ | ------ | ------------------------------------------------------------------- |
| `drives`        | body | space.driveItem\[] | —      | Drives are the drives at the space's root.                          |
| `drives[].name` | body | string             | —      | Name is the drive's name — the first segment of every key it holds. |
| `space`         | body | string             | —      | Space is the space that was listed.                                 |
| `total`         | body | integer (int64)    | —      | Total is how many drives came back.                                 |

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

## Examples

**CLI**

```bash
hanzo space drives list <space>
```

**SDK**

**.ts**

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

const api = new SpaceApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getSpaceBySpaceDrives({ space: 'space' });
```

**.py**

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = SpaceApi(client).get_space_by_space_drives(space='space')
```

**.go**

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

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

**.rs**

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

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

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

**.java**

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

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

var result = new SpaceApi(client).getSpaceBySpaceDrives();
```

**HTTP**

```bash
curl https://api.hanzo.ai/v1/space/<space>/drives \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

MCP reaches **space** through the `space` 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_space_drives"
         }
       }
     }'
```

---

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