> ## 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.

# Atlaso Build

> The memory API for the software and hardware you build — a private, isolated memory for each of your end-users.

**Atlaso Build** is the developer tier. It turns Atlaso's memory into an API you
can put inside your own product — a web app, a mobile backend, an agent, or a
physical device — so every one of *your* end-users gets their own private,
persistent memory. No memory infrastructure to run; you call one endpoint.

It's **\$25/month**, flat, and includes everything in [Pro](/account/plans).

## 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](/build/devices).

## How it fits together

<Steps>
  <Step title="You hold one project API key">
    Server-side. It looks like `atlk_…` and can address any subject in the
    project.
  </Step>

  <Step title="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.
  </Step>

  <Step title="You call remember / recall">
    Atlaso stores and retrieves memories in that subject's isolated bag and
    returns them, semantically ranked.
  </Step>
</Steps>

## Start here

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/build/quickstart">
    Subscribe, create a project, mint a key, and make your first `remember`
    and `recall` call — in a few minutes.
  </Card>

  <Card title="Authentication" icon="key" href="/build/authentication">
    The two auth modes, the exact headers and key formats, and every error
    code.
  </Card>

  <Card title="Subjects & isolation" icon="users" href="/build/subjects">
    What a subject is, and how each end-user's memory stays private.
  </Card>

  <Card title="API reference" icon="terminal" href="/build/api-reference">
    Every endpoint with curl, Python, and Node examples.
  </Card>

  <Card title="Devices & hardware" icon="cpu" href="/build/devices">
    Put memory on an ESP32, a robot, or a fleet — safely.
  </Card>

  <Card title="Limits & quotas" icon="gauge" href="/build/limits">
    Payload sizes, rate limits, storage, idempotency, and deletion.
  </Card>
</CardGroup>

<Note>
  Building something and not sure how to model it? Email
  [support@atlaso.ai](mailto:support@atlaso.ai) — a real person reads every
  message.
</Note>