Skip to main content
GET
/
api
/
v2
/
agents
/
{agent_id}
/
conflicts
curl -X GET "http://localhost:8000/api/v2/agents/my-agent/conflicts?date=2026-05-08" \
  -H "X-Session-Token: your_session_token"

{
  "agent_id": "my-agent",
  "session_id": "sess_982287b6a5f5",
  "date": "2026-05-08",
  "conflicts": [
    {
      "type": "contradiction",
      "title": "Database preference changed",
      "old_memory_id": "abc-123",
      "new_memory_id": "def-456",
      "resolved": false
    }
  ],
  "count": 1
}

​
Overview

Returns conflicts that are not yet marked resolved for the given agent and date. Memanto reads the conflict report JSON produced by the conflict-detection workflow (for example after running a daily summary that generates conflicts locally). If no report exists for that date, the list is empty (count: 0).

​
Authentication

API clients do not send an API key or Authorization header.
​
X-Session-Token
string
required
Session token from Activate Agent. Must match agent_id.

​
Path Parameters

​
agent_id
string
required
The unique identifier of the agent.

​
Query Parameters

​
date
string
Report date in YYYY-MM-DD. Defaults to today on the server when omitted.
curl -X GET "http://localhost:8000/api/v2/agents/my-agent/conflicts?date=2026-05-08" \
  -H "X-Session-Token: your_session_token"

{
  "agent_id": "my-agent",
  "session_id": "sess_982287b6a5f5",
  "date": "2026-05-08",
  "conflicts": [
    {
      "type": "contradiction",
      "title": "Database preference changed",
      "old_memory_id": "abc-123",
      "new_memory_id": "def-456",
      "resolved": false
    }
  ],
  "count": 1
}

​
Next Steps