# Create spaces

URL: https://docs.hanzo.ai/docs/openapi/space/post-space-spaces

> Makes a new space for the caller's org and answers 201 with it.

`POST /v1/space/spaces`

> [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/spaces` |
| **Method**    | `POST`                                 |
| **Operation** | `post_space_spaces`                    |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY` |

Makes a new space for the caller's org and answers 201 with it.

The one bucket a space's files live in is derived from the caller's VALIDATED
org, so an org can only ever create inside its own namespace and no request
field can redirect that. A name already taken in the org is 409.

Billed per call: the balance is checked BEFORE anything is touched, so an
unfunded org is refused with nothing created, and the debit lands only once the
space exists.

## Request

1 field, body `application/json` (required).

| Field  | In   | Type   | Required | Description                                                                                                                                         |
| ------ | ---- | ------ | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| `name` | body | string | —        | Name is the space's name, matching ^[a-z0-9](https://docs.hanzo.ai/docs/openapi)?$ — the shape a drive name takes too, so a caller learns one rule. |

## Response

| Status    | Body            | Meaning |
| --------- | --------------- | ------- |
| `201`     | space.spaceItem | created |
| `default` | problem-details | refused |

`201` body — 2 fields.

| Field       | In   | Type            | Always | Description                                            |
| ----------- | ---- | --------------- | ------ | ------------------------------------------------------ |
| `createdAt` | body | integer (int64) | —      | CreatedAt is when the space was made, in unix seconds. |
| `name`      | body | string          | —      | Name is the space's name, as the org created it.       |

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

## Examples

**CLI**

```bash
hanzo space spaces create
```

**SDK**

**.ts**

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

const api = new SpaceApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postSpaceSpaces({ name: "<name>" });
```

**.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).post_space_spaces(name="<name>")
```

**.go**

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

resp, _, err := client.SpaceAPI.PostSpaceSpaces(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::post_space_spaces(&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).postSpaceSpaces();
```

**HTTP**

```bash
curl -X POST https://api.hanzo.ai/v1/space/spaces \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "name": "<name>"
     }'
```

**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)