List Memory Conflicts - MemoryLake AI

GET /openapi/memorylake/api/v3/workspaces/{workspaceId}/projects/{projectId}/memories/conflicts

When MemoryLake extracts facts from conversations, it compares new facts against existing knowledge. If a contradiction is detected, it is recorded as a memory conflict. Use this endpoint to list a project’s conflicts, newest first, so you can surface them to users for review. You can filter by resolution status to show only unresolved conflicts that need attention, or only resolved ones for audit purposes. For conflicts among an actor’s personal facts, use List Actor Memory Conflicts instead.

Permission required: project:mem_list

Path Parameters

string

required

Workspace ID

string

required

Project ID

Query Parameters

boolean

Filter by resolution status. Pass true for resolved conflicts only, false for unresolved only. Omit to return both.

integer

default:"20"

Number of conflicts to return per page. Range: 1–100.

string

Token from a previous response to fetch the next page of results

curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v3/workspaces/ws_abc123/projects/proj_def456/memories/conflicts?resolved=false&page_size=20' \
  -H 'Authorization: Bearer sk_xxxxxx'

curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v3/workspaces/ws_abc123/projects/proj_def456/memories/conflicts?page_size=50' \
  -H 'Authorization: Bearer sk_xxxxxx'

Response

object

Show Paginated conflict list

array

Array of conflict objects

Show Conflict object

string

Conflict identifier

string

Short title describing the conflict

string

Detailed explanation of the contradiction

string

Conflict category: m2m (fact vs. fact) or m2d (fact vs. document)

boolean

Whether the conflict has been resolved

object

Resolution record. Present only when the conflict has been resolved; null otherwise. See Get Memory Conflict for the full structure.

boolean

Whether an involved fact changed after the conflict was detected. Stale conflicts may no longer be accurate.

string

Conflict type: logical or knowledge

array

IDs of the facts involved in the conflict

array

Snapshots of the involved facts at detection time

Show Fact snapshot

string

Fact identifier

string

Fact text at detection time

array

Document excerpts cited by a fact-vs-document conflict

Show File chunk

string

The conflicting excerpt text

string

ID of the document this excerpt belongs to

string

Display name of the document

string

When the conflict was first detected

string

When the conflict was last updated

string

Token to retrieve the next page of results. Absent when there are no more pages.

{
  "success": true,
  "data": {
    "items": [
      {
        "id": "conf-abc123",
        "name": "Contradicting project deadline",
        "description": "One fact states the project deadline is March 2025; another says it was moved to June 2025.",
        "category": "m2m",
        "resolved": false,
        "resolve": null,
        "stale": false,
        "conflict_type": "logical",
        "fact_ids": ["fact-001", "fact-002"],
        "fact_snapshots": [
          {
            "fact_id": "fact-001",
            "fact_text": "Project deadline is March 2025"
          },
          {
            "fact_id": "fact-002",
            "fact_text": "Project deadline was moved to June 2025"
          }
        ],
        "file_chunks": [],
        "created_at": "2025-01-20T14:30:00Z",
        "updated_at": "2025-01-20T14:30:00Z"
      }
    ],
    "continuation_token": null
  }
}

​Path Parameters

​Query Parameters

​Response

Path Parameters

Query Parameters

Response