Skip to main content
GET /openapi/memorylake/api/v2/projects/{id}/memories/conflicts
When a new memory is added, MemoryLake checks it against two things: the project’s existing memories, and the project’s documents. If the new memory contradicts either one, the contradiction is recorded as a conflict. There are two kinds:
  • m2m — memory vs memory: the new memory contradicts an existing memory.
  • m2d — memory vs document: the new memory contradicts content in a project document.
Use this endpoint to surface conflicts to end users (“review unresolved conflicts”), or to fetch conflicts tied to specific memories you’re about to display.

​
Path Parameters

​
id
string
required
Project ID

​
Query Parameters

​
page
integer
default:"1"
Page number (1-based)
​
page_size
integer
default:"50"
Page size, 1–100
​
category
string
Filter by conflict category:
  • m2m — memory vs memory.
  • m2d — memory vs document.
​
conflict_type
string
Filter by kind of inconsistency:
  • logical — contradiction or tension between statements.
  • knowledge — disagreement about facts or what was cited.
​
resolved
boolean
Filter to only resolved (true) or only unresolved (false) conflicts. Omit to return both.
​
stale
boolean
Filter by whether the underlying content has changed since the conflict was detected. Stale conflicts may no longer be accurate.
​
memory_ids
string
Comma-separated list of memory IDs. Returns conflicts that involve any of the listed memories.
curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v2/projects/proj-a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6/memories/conflicts?resolved=false&page=1&page_size=50' \
  -H 'Authorization: Bearer sk_xxxxxx'

​
Response

​
data
object
{
  "success": true,
  "data": {
    "items": [
      {
        "id": "conf-abc123",
        "name": "Contradicting restaurant preferences",
        "description": "An earlier memory says the user prefers spicy food; a later one says they avoid it.",
        "category": "m2m",
        "conflict_type": "logical",
        "resolved": false,
        "stale": false,
        "memory_ids": ["mem-001", "mem-002"],
        "memory_snapshots": [
          { "memory_id": "mem-001", "memory_text": "User prefers spicy food" },
          { "memory_id": "mem-002", "memory_text": "User avoids spicy food" }
        ],
        "file_chunks": [],
        "event_id": "evt-xyz",
        "created_at": "2024-01-15T10:30:00Z",
        "updated_at": "2024-01-15T10:30:00Z"
      }
    ],
    "total": 1,
    "page": 1,
    "page_size": 50
  }
}
For the full breakdown of a single conflict — including the nested resolution record when it’s been resolved and document excerpts for m2d cases — call Get Memory Conflict.