Quickstart

From zero to a working memory API in about five minutes. In the dashboard, open Settings → Developer and choose Get Atlaso Build — $25/mo. Checkout is handled by Stripe; Build activates the moment payment completes.

2. Create a project

Still under Settings → Developer, click New project and give it a slug — lowercase letters, digits, and hyphens, up to 40 characters (e.g. acme-travel). A project is a namespace; you’ll usually have one per app or environment.

3. Mint an API key

On the project, click New key. The full key is shown once — copy it now and store it as a server-side secret. It looks like:

atlk_1a2b3c4d5e6f_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

The key is shown only at creation and never again — Atlaso stores only a hash. Keep it on your server, never in a browser, mobile app, or on a device. See Authentication.

You can hold up to 10 live keys per project; revoke one anytime from the dashboard.

4. Remember something

Pick a subject — your own id for one end-user (any stable string). Then store a memory in that subject’s private bag:

curl -X POST https://mcp.atlaso.ai/developer/v1/memories \
  -H "X-Atlaso-Project-Key: atlk_1a2b3c4d5e6f_XXXXXXXX" \
  -H "X-Atlaso-Subject: user_8213" \
  -H "Content-Type: application/json" \
  -d '{"text": "Prefers window seats and vegetarian meals.", "tags": ["travel-prefs"]}'

{ "id": "mem_9f2c…", "subject": "user_8213", "redacted": [] }

redacted lists the category names of any recognized secrets, credentials, or high-entropy tokens scrubbed before storing, such as aws_access_key or high_entropy. It never contains the removed values.

5. Recall it

Later — a different session, a different server, doesn’t matter — ask for what you know about that subject:

curl "https://mcp.atlaso.ai/developer/v1/recall?q=seating%20preference&limit=5" \
  -H "X-Atlaso-Project-Key: atlk_1a2b3c4d5e6f_XXXXXXXX" \
  -H "X-Atlaso-Subject: user_8213"

{
  "subject": "user_8213",
  "is_confident": true,
  "has_disagreement": false,
  "results": [
    {
      "id": "mem_9f2c…",
      "content": "Prefers window seats and vegetarian meals.",
      "tags": ["travel-prefs"],
      "is_confident": true,
      "has_disagreement": false,
      "conflict_peers": []
    }
  ]
}

That’s the whole loop. Swap in a new subject for each of your end-users and their memories stay completely separate.

Next steps

Understand subjects

How isolation works, and why the key stays server-side.

Full API reference

Delete, GDPR purge, Python & Node examples, response fields.

Put it on a device

Per-device credentials for hardware and fleets.

Limits & quotas

What to know before you scale.

Get started

Tools

Build — developer API

Account

Help

2. Create a project

3. Mint an API key

4. Remember something

5. Recall it

Next steps

Understand subjects

Full API reference

Put it on a device

Limits & quotas

​1. Subscribe to Build

​2. Create a project

​3. Mint an API key

​4. Remember something

​5. Recall it

​Next steps

Understand subjects

Full API reference

Put it on a device

Limits & quotas

1. Subscribe to Build

2. Create a project

3. Mint an API key

4. Remember something

5. Recall it

Next steps