Spaces

Create a space

POST /v1/spaces/
Authorization: Bearer anona_live_YOUR_KEY
Content-Type: application/json

{
  "name": "customer-support-bot",
  "description": "Memories for the customer support chatbot"
}

Parameter	Type	Required	Description
`name`	string	Yes	The name of the space. It also becomes the `space_id`.
`description`	string	No	What this space is for.

space_id is not a settable field. Sending one is rejected with 422. Response 201 Created

{
  "space_id": "customer-support-bot",
  "name": "customer-support-bot",
  "description": "Memories for the customer support chatbot",
  "created_at": "2026-07-14T12:34:56Z"
}

The space_id is the name you chose. There is no separate generated id. The name you pass on create is the identifier every other endpoint takes, so pick it deliberately. Every memory operation requires it.

A name containing characters that are not URL-safe produces a space_id containing them too. That is legal, but the id then has to be percent-encoded everywhere it appears in a path: my space becomes /v1/spaces/my%20space. Sticking to letters, digits, - and _ avoids the problem entirely.

List spaces

GET /v1/spaces/
Authorization: Bearer anona_live_YOUR_KEY

Response 200 OK

{
  "spaces": [
    {
      "space_id": "customer-support-bot",
      "name": "customer-support-bot",
      "created_at": "2026-07-14T12:34:56Z"
    }
  ],
  "total": 1
}

Get space details

GET /v1/spaces/{space_id}
Authorization: Bearer anona_live_YOUR_KEY

Response 200 OK

{
  "space_id": "customer-support-bot",
  "name": "customer-support-bot",
  "description": "Memories for the customer support chatbot",
  "created_at": "2026-07-14T12:34:56Z"
}

Delete a space

DELETE /v1/spaces/{space_id}
Authorization: Bearer anona_live_YOUR_KEY

Response 204 No Content.

Deleting a space permanently destroys the space and every memory in it. This cannot be undone.

Space members

Spaces can optionally have named members within your organization.

The membership endpoints are control-plane calls: they need a dashboard session with the owner or admin role, not an API key. An API key gets 401 session_required; a developer or viewer session gets 403 insufficient_role.

Method and path	What it does
`GET /v1/spaces/{space_id}/members`	Lists the members of a space.
`POST /v1/spaces/{space_id}/members/invite`	Invites a member to the space.
`DELETE /v1/spaces/{space_id}/members/{member_id}`	Removes a member from the space.

State	Who can reach the space
No member rows	Anyone in the organization. The space is treated as org-wide.
One or more member rows	Only the listed members. Access is enforced.

The org-wide state exists for spaces that pre-date membership: creating a space through the API or dashboard automatically writes a member row for the creator, so a new space is member-only from the moment it exists.

Python SDK

spaces = client.list_spaces()
for s in spaces:
    print(s["space_id"], s["name"])

client.create_space("support-bot", description="Customer support memory")
client.delete_space("support-bot")

list_spaces, create_space, and delete_space are all wrapped (with async_ variants). Membership management is dashboard/session-only, so it is deliberately not in the API-key SDK.

Error responses

Status	Code	Cause
401	`missing_auth` / `invalid_api_key`	Missing or invalid API key.
403	`space_access_denied`	You are not a member of this space.
403	`space_limit_reached`	Your plan’s space limit is used up.
403	`space_read_only`	A read-only member attempted a write.
403	`space_unavailable`	The owning org of a shared space has no active API key.
404	`space_not_found`	The space does not exist.
409	`space_ambiguous`	A bare name matches both your own space and one shared with you — use the `qualified_id`.
409	`space_exists`	Create was called with a name you already hold. A space’s id is its name, so re-creating is never a fresh space — fetch or delete the existing one instead.
422	`validation_error`	Missing or invalid `name`.
429	`rate_limited` / `credits_exhausted`	Rate limit hit, or the organization is out of credits.

See the full error reference.

Next steps

Memories API

Store and manage memories.

Errors

The complete error code reference.

Getting Started

API Essentials

Memory (data plane)

LLM Proxy (drop-in)

Account (control plane)

SDKs & MCP

Integrations

Guides

Changelog

Create a space

List spaces

Get space details

Delete a space

Space members

Python SDK

Error responses

Next steps

Memories API

Errors

​Create a space

​List spaces

​Get space details

​Delete a space

​Space members

​Python SDK

​Error responses

​Next steps

Memories API

Errors

Create a space

List spaces

Get space details

Delete a space

Space members

Python SDK

Error responses

Next steps