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

{
  "agent_id": "my-agent",
  "session_id": "sess_abc123",
  "date": "2026-05-08",
  "conflicts": {
    "status": "success",
    "json_path": "~/.memanto/conflicts/my-agent_2026-05-08_conflicts.json",
    "conflict_count": 2
  }
}

​
Overview

Runs the LLM conflict-detection pass over an agent’s session memories for a given date and writes the report that List Conflicts and Resolve Conflict read from. This is the same work Memanto’s scheduled daily job performs.

​
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.

​
Body

​
date
string
Date string YYYY-MM-DD. Defaults to today on the server when omitted.
curl -X POST "http://localhost:8000/api/v2/agents/my-agent/conflicts/generate" \
  -H "X-Session-Token: your_session_token" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-05-08"}'

{
  "agent_id": "my-agent",
  "session_id": "sess_abc123",
  "date": "2026-05-08",
  "conflicts": {
    "status": "success",
    "json_path": "~/.memanto/conflicts/my-agent_2026-05-08_conflicts.json",
    "conflict_count": 2
  }
}

​
Next Steps