List drives

Lists a space's drives.

GET /v1/space/{space}/drives

Addresshttps://api.hanzo.ai/v1/space/{space}/drives
MethodGET
Operationget_space_by_space_drives
AuthAuthorization: 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.

FieldInTypeRequiredDescription
spacepathstringyesSpace is the space's name, from the path.

Response

StatusBodyMeaning
200space.driveListok
defaultproblem-detailsrefused

200 body — 4 fields.

FieldInTypeAlwaysDescription
drivesbodyspace.driveItem[]—Drives are the drives at the space's root.
drives[].namebodystring—Name is the drive's name — the first segment of every key it holds.
spacebodystring—Space is the space that was listed.
totalbodyinteger (int64)—Total is how many drives came back.

Failure carries the platform error shape — see Errors.

Examples

hanzo space drives list <space>
import { Configuration, SpaceApi } from 'hanzoai';

const api = new SpaceApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getSpaceBySpaceDrives({ space: 'space' });
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')
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
}
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?;
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();
curl https://api.hanzo.ai/v1/space/<space>/drives \
  -H "Authorization: Bearer $HANZO_API_KEY"

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:

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 · All Hanzo APIs · Interactive reference

Was this page useful?