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

# Quickstart

> Subscribe to Build, create a project, mint an API key, and make your first remember and recall call.

From zero to a working memory API in about five minutes.

## 1. Subscribe to Build

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
```

<Warning>
  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](/build/authentication#keeping-keys-safe).
</Warning>

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:

```bash theme={null}
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"]}'
```

```json theme={null}
{ "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:

```bash theme={null}
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"
```

```json theme={null}
{
  "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

<CardGroup cols={2}>
  <Card title="Understand subjects" icon="users" href="/build/subjects">
    How isolation works, and why the key stays server-side.
  </Card>

  <Card title="Full API reference" icon="terminal" href="/build/api-reference">
    Delete, GDPR purge, Python & Node examples, response fields.
  </Card>

  <Card title="Put it on a device" icon="cpu" href="/build/devices">
    Per-device credentials for hardware and fleets.
  </Card>

  <Card title="Limits & quotas" icon="gauge" href="/build/limits">
    What to know before you scale.
  </Card>
</CardGroup>