Configuration¶
The API is HTTPS on 127.0.0.1:8443. Clients do not choose their own user.
Root administrators control users and data.
Where things live¶
| Item | What it is |
|---|---|
https://127.0.0.1:8443 |
Authenticated API. No browser dashboard. |
~/.config/sushi/mem0/access.json |
The default client credential. |
~/.config/sushi/mem0/server.crt |
The instance certificate the client trusts. |
~/.config/sushi/mem0/isolation.json |
Credential for the demo's second user. |
/etc/mem0/provider.json |
The provider configuration the service reads. |
/etc/mem0/identity/users.json |
Root-managed user map. |
/var/lib/mem0/users |
Per-user Qdrant store and SQLite history. |
sushi-mem0-api |
Client. It reads the credential file and does not print it. |
sushi-mem0-admin |
Applies provider configuration and adds users. |
Routes¶
| Call | Body |
|---|---|
GET /health |
Readiness, including whether a provider is configured |
POST /memories |
text (1–8000 characters) and optional infer (default false) |
GET /memories |
Up to 100 memories for the authenticated user |
GET /memories/<id> |
The exact stored text |
DELETE /memories/<id> |
Delete that memory |
POST /search |
query and optional limit (1–100) |
Pass JSON with --input so the body is not a command argument full of
secrets. The helper already keeps the credential off the command line.
Another API user¶
Stop the service, add the user, and start it again. Use a new user name and a new output file:
sudo systemctl stop sushi-mem0-api.service
sudo sushi-mem0-admin add-user --user application-a --output /root/mem0-application-a.json
sudo systemctl start sushi-mem0-api.service
The output is mode 0600. Deliver that file and the instance certificate
through your own channel. The client accepts --profile for an owned
credential file. There is no self-service signup. The service allows up to
100 configured users.
Certificate¶
First boot generates a TLS identity. The public guide says the certificate
lasts 365 days. Renew it before expiry, keep SANs for localhost and
127.0.0.1, update ~/.config/sushi/mem0/server.crt, and restart the API.
server.key stays root:mem0 mode 0640. A partial
/etc/mem0/identity.partial is kept for diagnosis and is not overwritten.
Last updated November 11, 2026 · Suggest an improvement