Skip to main content
POST
/
api
/
v2
/
agents
/
{agent_id}
/
conflicts
/
resolve
curl -X POST "http://localhost:8000/api/v2/agents/my-agent/conflicts/resolve" \
  -H "X-Session-Token: your_session_token" \
  -H "Content-Type: application/json" \
  -d '{
    "date": "2026-05-08",
    "conflict_index": 0,
    "action": "keep_new"
  }'

{
  "agent_id": "my-agent",
  "session_id": "sess_982287b6a5f5",
  "date": "2026-05-08",
  "action": "keep_new",
  "deleted": "abc-123",
  "status": "resolved"
}

​
Overview

Applies a resolution action to a single conflict identified by its index in the full conflict array for that agent and date (same ordering as the JSON report file). This uses the same resolution logic as the Memanto CLI conflict flow (updates Moorcheh memories and marks the row resolved in the report).

​
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.
​
Content-Type
string
required
Must be application/json

​
Path Parameters

​
agent_id
string
required
The unique identifier of the agent.

​
Body

​
conflict_index
integer
required
Zero-based index into the full conflicts list for that date (not only unresolved rows).
​
action
string
required
One of: keep_old, keep_new, keep_both, remove_both, manual.
​
date
string
Report date YYYY-MM-DD. Defaults to today on the server when omitted.
​
manual_content
string
Required when action is manual: replacement memory text (both conflicting memories are removed and this content is stored).
​
manual_type
string
Optional memory type for the manual replacement (defaults follow implementation when omitted).
curl -X POST "http://localhost:8000/api/v2/agents/my-agent/conflicts/resolve" \
  -H "X-Session-Token: your_session_token" \
  -H "Content-Type: application/json" \
  -d '{
    "date": "2026-05-08",
    "conflict_index": 0,
    "action": "keep_new"
  }'

{
  "agent_id": "my-agent",
  "session_id": "sess_982287b6a5f5",
  "date": "2026-05-08",
  "action": "keep_new",
  "deleted": "abc-123",
  "status": "resolved"
}
Invalid action, missing conflict report, out-of-range index, or missing manual_content for manual typically surface as 500 with details from the underlying resolver.

​
Next Steps