Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.anduril.atlas.arenaphysica.com/llms.txt

Use this file to discover all available pages before exploring further.

Memories are knowledge Atlas carries across interactions. User memories capture personal preferences, domain background, and workflow conventions. Entity memories capture hardware-specific context attached to nodes in the metagraph. Entity memory endpoints are documented under Metagraph. See Adding a Personal Skill & System Memory for a workflow guide.

Endpoints

MethodPathDescription
GET/memoriesGet current user memories
PUT/memoriesSet user memories
GET/memories/historyGet memory version history
POST/memories/restoreRestore a previous memory version

Get memories

GET /memories Returns the current memory content for the authenticated user. Example request:
curl "$ATLAS_URL/api/v1/memories" \
  -H "Authorization: Bearer $ATLAS_TOKEN"
Response fields:
FieldTypeNullableDescription
contentstringNoMarkdown-formatted memory content
updated_atstringYesISO 8601 timestamp of the last update
Example response:
{
  "content": "I work on power systems. Always flag voltage anomalies as high priority. Team uses dB scale for RF measurements.",
  "updated_at": "2026-04-13T09:00:00.000000"
}

Set memories

PUT /memories Replaces the current memory content entirely. Memory writes are versioned automatically. Request body:
FieldRequiredTypeDescription
contentYesstringFull memory content (max 10,000 characters, markdown supported)
Example request:
curl -X PUT "$ATLAS_URL/api/v1/memories" \
  -H "Authorization: Bearer $ATLAS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "I work on power systems. Always flag voltage anomalies as high priority. Team uses dB scale for RF measurements."
  }'
Returns the updated memory object with the same fields as Get memories.

Get version history

GET /memories/history Returns all previous versions of the user’s memory document. Example request:
curl "$ATLAS_URL/api/v1/memories/history" \
  -H "Authorization: Bearer $ATLAS_TOKEN"
Response fields (array):
FieldTypeNullableDescription
versionintegerNoVersion number (1-indexed)
contentstringNoMemory content at this version
updated_atstringNoISO 8601 timestamp
restored_from_versionintegerYesVersion this was restored from, if applicable
Example response:
[
  {
    "version": 2,
    "content": "I work on power systems. Always flag voltage anomalies as high priority. Team uses dB scale for RF measurements.",
    "updated_at": "2026-04-13T09:00:00.000000",
    "restored_from_version": null
  },
  {
    "version": 1,
    "content": "I work on power systems.",
    "updated_at": "2026-04-12T08:00:00.000000",
    "restored_from_version": null
  }
]

Restore a version

POST /memories/restore Rolls back the user’s memory to a previous version. The restore creates a new version entry rather than overwriting history. Request body:
FieldRequiredTypeDescription
versionYesintegerVersion number to restore (must be ≥ 1)
Example request:
curl -X POST "$ATLAS_URL/api/v1/memories/restore" \
  -H "Authorization: Bearer $ATLAS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"version": 1}'
Returns the restored memory object with the same fields as Get memories.