What you get
- A memory API at
https://mcp.atlaso.ai/developer/v1—remember,recall, and delete, over plain HTTPS. No SDK to install. - A private memory per end-user. You pass a
subject(your own id for one user or device); each(project × subject)is a cryptographically isolated memory bag. Users never see each other’s memories. - The same engine that powers Atlaso for coding tools — semantic recall, automatic scrubbing of recognized secrets, credentials, and high-entropy tokens, plus conflict-aware results — none of the infrastructure.
- A dashboard to browse every subject’s memory by project, and per-project usage counters.
- Hardware-ready. Mint a revocable, per-device credential for an ESP32, a robot, or a fleet — see Devices & hardware.
How it fits together
1
You hold one project API key
Server-side. It looks like
atlk_… and can address any subject in the
project.2
You name a subject per end-user
Any stable string —
user_8213, an email, a device id. It’s your id for
one of your users.3
You call remember / recall
Atlaso stores and retrieves memories in that subject’s isolated bag and
returns them, semantically ranked.
Start here
Quickstart
Subscribe, create a project, mint a key, and make your first
remember
and recall call — in a few minutes.Authentication
The two auth modes, the exact headers and key formats, and every error
code.
Subjects & isolation
What a subject is, and how each end-user’s memory stays private.
API reference
Every endpoint with curl, Python, and Node examples.
Devices & hardware
Put memory on an ESP32, a robot, or a fleet — safely.
Limits & quotas
Payload sizes, rate limits, storage, idempotency, and deletion.
Building something and not sure how to model it? Email
support@atlaso.ai — a real person reads every
message.