---
title: "Reclassify a checkpoint violation"
method: POST
path: "/agents/{agent_id}/reclassify"
tags: ["Reclassification"]
---

# Reclassify a checkpoint violation

`POST /agents/{agent_id}/reclassify`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/agents/{agent_id}/reclassify`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`

Reclassify a previously recorded AIP checkpoint violation. This allows operators to correct false positives or adjust severity after manual review. The reclassification is recorded in the audit trail and can trigger a score recomputation.

## Path parameters

- `agent_id` string, required

## Request body

- ReclassificationRequest: Request to reclassify a checkpoint violation.
  - `checkpoint_id` string, required: Identifier of the checkpoint to reclassify
  - `reason` string, required: Human-readable justification for the reclassification
  - `card_amendment_id` string, nullable: Optional ID of an alignment card amendment that triggered this reclassification
  - `after_classification` 'clear' | 'review_needed' | 'boundary_violation': Verdict the checkpoint is reclassified TO (MNE-2156). Omit for a full exoneration ('clear', the historical behavior); send 'review_needed' or 'boundary_violation' when the review lowers the severity without clearing the agent. An unrecognized value is rejected with 400 — it is never coerced to 'clear'. This is deliberately a SUBSET of the checkpoint verdict enum: 'unverified' means the integrity control did not run, which the system assigns and a reviewer cannot choose.

## Response `200`

Reclassification result with score impact

- ReclassificationResult: Result of a checkpoint violation reclassification.
  - `reclassification_id` string: Unique identifier for this reclassification
  - `checkpoint_id` string: Identifier of the reclassified checkpoint
  - `agent_id` string: Agent whose checkpoint was reclassified
  - `original_type` string: Original violation type before reclassification
  - `new_type` string: New violation type after reclassification
  - `reason` string: Justification provided for the reclassification
  - `score_impact` object: Impact of the reclassification on the agent's score
    - `previous_score` number
    - `new_score` number
    - `delta` number

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `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)