List Memory Conflicts - MemoryLake AI

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.

Permission required: project:mem_list · instance

Path Parameters

string

required

Project ID

Query Parameters

integer

default:"1"

Page number (1-based)

integer

default:"50"

Page size, 1–100

string

Filter by conflict category:

m2m — memory vs memory.
m2d — memory vs document.

string

Filter by kind of inconsistency:

logical — contradiction or tension between statements.
knowledge — disagreement about facts or what was cited.

boolean

Filter to only resolved (true) or only unresolved (false) conflicts. Omit to return both.

boolean

Filter by whether the underlying content has changed since the conflict was detected. Stale conflicts may no longer be accurate.

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'

curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v2/projects/proj-a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6/memories/conflicts?memory_ids=mem-001,mem-002' \
  -H 'Authorization: Bearer sk_xxxxxx'

Response

object

Show Paginated conflict list

array

Array of conflict objects

Show Conflict

string

Conflict ID

string

Short title

string

Longer explanation of the contradiction

string

m2m (memory vs memory) or m2d (memory vs document)

string

logical (contradicting statements) or knowledge (disagreement about facts or citations)

boolean

Whether the conflict has been resolved

object

Resolution details — present only when resolved is true. See Get Memory Conflict for the full shape.

boolean

Whether underlying content has changed since detection

array

IDs of memories involved in the conflict

array

Memory snapshots captured at detection time

array

Document excerpts involved. Non-empty when category is m2d.

string

ID of the event that triggered detection

string

First detected at

string

Last updated at

integer

Total matching conflicts

integer

Current page (1-based)

integer

Page size

{
  "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.

​Path Parameters

​Query Parameters

​Response

Path Parameters

Query Parameters

Response