Anchors

Anchors define the scope that memory belongs to.

When to create an anchor

Create an anchor when your product needs one stable memory lane.

Examples:

• one anchor per user + character pair
• one anchor per learner
• one anchor per editorial lane
• one anchor per product workflow

Create an anchor

curl -X POST https://maas.nunchiai.com/v1/anchors \
  -H "Authorization: Bearer mk_maas_example" \
  -H "X-Workspace-Id: acme-prod" \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "Editorial Lane",
    "type": "chat-log",
    "metadata": {
      "lane": "MAAS_ANCHOR_EDITORIAL",
      "project": "indiepulse-editorial"
    }
  }'

{
  "anchor_id": "6629df4e-6ee8-4d1d-ae8a-bb1f2a35a2ab",
  "name": "Editorial Lane",
  "type": "chat-log",
  "metadata": {
    "lane": "MAAS_ANCHOR_EDITORIAL",
    "project": "indiepulse-editorial"
  }
}

Naming rules

• Keep the anchor strategy stable after production launch.
• Encode scope in metadata even if the anchor name is human-readable.
• Reuse anchors. Do not create a new anchor every turn.

Recommended defaults

• Character chat: one anchor per user + character
• Tutor: one anchor per learner
• Editorial: one anchor per lane such as EDITORIAL, TRENDS, MAKERS

Errors

• 400 invalid body or missing workspace header
• 402 billing blocked
• 403 access policy denied
• 429 rate limited