> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ariacompute.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MEMO API Overview: AriaMem Knowledge Memory Platform

> Aria Compute MEMO API exposes the AriaMem cloud knowledge memory fusion platform over REST, covering workspaces, knowledge bases, memory cubes, chat memory, skills, code graph, agent loadout, and wiki, all authenticated with JWT or API key.

The MEMO API is the REST surface of Aria Compute's **AriaMem** cloud knowledge memory fusion platform. AriaMem unifies a knowledge base and memory inside one workspace: you upload documents, extract memory cubes, let agents distill layered chat memory, and bridge knowledge memory both ways into rollback-able wiki pages.

Every endpoint is prefixed with `/v1`, authenticated uniformly with a JWT or API key, and guarded by per-workspace RBAC. Call REST directly — the examples below use `curl`.

> [card] [Authentication](https://docs.ariacompute.com/api-reference/memo/authentication.md)
>
> Bearer JWT and X-API-Key schemes, self-serve key management

> [card] [Workspaces](https://docs.ariacompute.com/api-reference/memo/workspaces/create.md)
>
> Create an isolated tenant, invite members, assign roles

> [card] [Knowledge](https://docs.ariacompute.com/api-reference/memo/kbs/create.md)
>
> Build a KB, upload documents, search, and chat over them

> [card] [Memory Cubes](https://docs.ariacompute.com/api-reference/memo/cubes/create.md)
>
> Create a memory cube, add nodes, wire edges, semantic search

## Base URL

```text theme={null}
https://memo.ariacompute.com
```

On the China site use `https://memo.ariacompute.cn`.

For a self-hosted AriaMem (Docker, port `8010`, base path `/ariamem/`), replace the host with your deployment address — paths and parameters are identical.

## Authentication

Send a JWT in the `Authorization` header, or an API key in the `X-API-Key` header:

* `Authorization: Bearer <jwt>`
* `X-API-Key: <sk_aria_...>`

To obtain a JWT: [`POST /v1/auth/login`](https://docs.ariacompute.com/api-reference/memo/auth/login) exchanges email/password for a `token`, or [`POST /v1/auth/register`](https://docs.ariacompute.com/api-reference/memo/auth/register) creates an account. API keys are created self-serve via [`POST /v1/apikeys`](https://docs.ariacompute.com/api-reference/memo/apikeys/create-list) (shown only once). See [Authentication](https://docs.ariacompute.com/api-reference/memo/authentication.md) for details.

## Workspaces & RBAC

Every business endpoint (except auth) lives under a workspace (`/v1/workspaces/:workspace_id/...`). Create one first ([Create Workspace](https://docs.ariacompute.com/api-reference/memo/workspaces/create.md)), then access it by role:

| Role | Capability |
| - | - |
| `owner` | Full control, including audit and member management |
| `admin` | Read/write plus audit viewing |
| `contributor` | Read/write content and memory |
| `viewer` | Read-only |

Insufficient role returns `403 Forbidden`.

## Error format

Errors return the HTTP status and a uniform JSON envelope:

```json theme={null}
{
  "error": {
    "message": "Description of what went wrong",
    "type": "400 Bad Request"
  }
}
```

Common codes: `400` bad input, `401` unauthenticated, `403` insufficient role, `404` not found, `500` server error.

## Versioning

Current endpoints are prefixed with `/v1`. This reference documents every `/v1` business endpoint of the ariamem backend (auth, workspaces, knowledge, memory cubes, knowledge memory conversion, layered chat memory, skills, code graph, agent loadout, asset library, and wiki).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.