/v1, authenticated uniformly with a JWT or API key, and guarded by per-workspace RBAC. Call REST directly — the examples below use curl.
Authentication
Bearer JWT and X-API-Key schemes, self-serve key management
Workspaces
Create an isolated tenant, invite members, assign roles
Knowledge
Build a KB, upload documents, search, and chat over them
Memory Cubes
Create a memory cube, add nodes, wire edges, semantic search
Base URL
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 theAuthorization header, or an API key in the X-API-Key header:
Authorization: Bearer <jwt>X-API-Key: <sk_aria_...>
POST /v1/auth/login exchanges email/password for a token, or POST /v1/auth/register creates an account. API keys are created self-serve via POST /v1/apikeys (shown only once). See Authentication for details.
Workspaces & RBAC
Every business endpoint (except auth) lives under a workspace (/v1/workspaces/:workspace_id/...). Create one first (Create Workspace), then access it by role:
Insufficient role returns
403 Forbidden.
Error format
Errors return the HTTP status and a uniform JSON envelope: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).