Memory Atoms

Atoms are the durable memory units stored in MaaS.

What an atom contains

• anchor_id — the memory scope
• content — the natural-language memory payload
• source_type — storage lane such as prd or chat-log
• metadata — product-specific fields such as atom_type, user_external_id, session_id
• confidence — optional relevance or certainty signal if your product uses it

Write an atom

curl -X POST https://maas.nunchiai.com/v1/atoms \
  -H "Authorization: Bearer mk_maas_example" \
  -H "X-Workspace-Id: acme-prod" \
  -H 'Content-Type: application/json' \
  -d '{
    "anchor_id": "be2d5afd-8ec2-44d1-bfb3-e1eb4cb2c9b1",
    "content": "Learner still confuses TCP and UDP.",
    "source_type": "prd",
    "metadata": {
      "atom_type": "misconception",
      "user_external_id": "learner-17",
      "confidence": 0.82
    },
    "chunking": { "enabled": false }
  }'

{
  "atom_ids": ["88f1b2ff-61d1-4675-ae74-634c78e8aa61"],
  "stored_count": 1,
  "service_source": "enterprise-tutor"
}

Storage rules

• Store meaningful observations, not greetings or filler.
• Keep content human-readable. Do not store compressed codewords.
• Put product taxonomy in metadata.atom_type.
• Use source_type=prd for durable facts and preferences.
• Use source_type=chat-log for recent conversational observations.

Character chat examples

• preference
• emotional_state
• relationship_event
• backstory_reveal
• promise
• boundary

Errors

• 400 malformed request body or invalid key
• 403 access policy denied
• 404 anchor missing
• 429 write rate limited