---
title: "Resolve a concern or violation"
method: POST
path: "/agents/{agent_id}/resolve"
tags: ["Enforcement"]
---

# Resolve a concern or violation

`POST /agents/{agent_id}/resolve`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/agents/{agent_id}/resolve`
- Auth: HTTP bearer

## Path parameters

- `agent_id` string, required

## Request body

- object
  - `target_type` 'checkpoint' | 'trace', required
  - `target_id` string, required
  - `resolution_type` 'acknowledged' | 'allow_action' | 'add_value', required
  - `action_name` string: Required when resolution_type is allow_action
  - `value_name` string: Required when resolution_type is add_value

## Response `200`

Resolution created

- object
  - `resolution_id` string
  - `resolution_type` string
  - `resolved_by` string
  - `card_modified` boolean

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)