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": [
{
"index": 2,
"type": "contradiction",
"title": "Database preference changed",
"old_memory_id": "abc-123",
"new_memory_id": "def-456",
"resolved": false
}
],
"count": 1
}
{
"detail": "Missing session token. Use X-Session-Token header."
}
{
"detail": {
"error": "InternalServerError",
"message": "An unexpected error occurred",
"details": {
"original_error": "Session is for agent 'other-agent', cannot access 'my-agent'"
}
}
}
Data
List Conflicts
List unresolved conflicts for an agent from the stored conflict report.
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": [
{
"index": 2,
"type": "contradiction",
"title": "Database preference changed",
"old_memory_id": "abc-123",
"new_memory_id": "def-456",
"resolved": false
}
],
"count": 1
}
{
"detail": "Missing session token. Use X-Session-Token header."
}
{
"detail": {
"error": "InternalServerError",
"message": "An unexpected error occurred",
"details": {
"original_error": "Session is for agent 'other-agent', cannot access 'my-agent'"
}
}
}
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).
Each conflict carries an
index — its stable position in the full report, including already-resolved rows. Pass that value as conflict_index to Resolve Conflict; do not use the conflict’s position in this filtered response. Because this endpoint omits resolved conflicts, the two numbering schemes diverge after the first resolution, and resolving by filtered position can act on the wrong memory.Authentication
API clients do not send an API key orAuthorization header.
string
required
Session token from Activate Agent. Must match
agent_id.Path Parameters
string
required
The unique identifier of the agent.
Query Parameters
string
Report date in
YYYY-MM-DD. Defaults to today (UTC) 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": [
{
"index": 2,
"type": "contradiction",
"title": "Database preference changed",
"old_memory_id": "abc-123",
"new_memory_id": "def-456",
"resolved": false
}
],
"count": 1
}
{
"detail": "Missing session token. Use X-Session-Token header."
}
{
"detail": {
"error": "InternalServerError",
"message": "An unexpected error occurred",
"details": {
"original_error": "Session is for agent 'other-agent', cannot access 'my-agent'"
}
}
}
Next Steps
- Resolve Conflict to apply a resolution for one row in the report
- Recall to inspect memories directly