Get Memory Conflict - MemoryLake AI

GET /openapi/memorylake/api/v2/projects/{id}/memories/conflicts/{conflictId}

Returns the full record for one conflict. You always get the memory snapshots captured at detection time. For memory-vs-document (m2d) conflicts, you also get the document excerpts that contradict the memory — excerpts whose source document has since been removed from the project are dropped.

Path Parameters

string

required

Project ID

conflictId

string

required

Conflict ID

curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v2/projects/proj-a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6/memories/conflicts/conf-abc123' \
  -H 'Authorization: Bearer sk_xxxxxx'

Response

data

object

Show Conflict

string

Conflict ID

name

string

Short title

description

string

Longer explanation of the contradiction

category

string

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

conflict_type

string

What kind of inconsistency:

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

resolved

boolean

Whether the conflict has been resolved

resolve

object

Resolution record — present only when resolved is true.

Show Resolution

string

Resolution record ID

strategy

string

Strategy applied: keep_memory, trust_memory, trust_document, or dismiss

keep_memory_id

string

Memory kept when the strategy required a choice

forgotten_memory_ids

array

Memories forgotten as part of resolution

resolved_by

string

Actor that resolved the conflict

created_at

string

When the conflict was resolved

stale

boolean

Whether underlying content has changed since detection

memory_ids

array

Memories involved in the conflict

memory_snapshots

array

Snapshots of each memory’s text at the moment the conflict was detected

Show Memory snapshot

memory_id

string

Memory identifier

memory_history_id

string

History revision ID, if any

memory_text

string

Memory text at detection time

file_chunks

array

Document excerpts — non-empty when category is m2d

Show File chunk

document_id

string

ID of the project document

document_name

string

Display name of the document

chunk

object

Matched text span from the document

Show Chunk

type

string

text

text

string

Plain text content

range

string

Optional location hint (e.g. page or cell range)

event_id

string

ID of the event that triggered detection

created_at

string

First detected at

updated_at

string

Last updated at

{
  "success": true,
  "data": {
    "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"
  }
}

Once you have the conflict detail, apply a decision with Resolve Memory Conflict. The returned forgotten_memory_ids tells you which memories were removed so your UI can stay in sync.

MemoryLake API

​Path Parameters

​Response

Path Parameters

Response