---
title: "List reclassification history"
method: GET
path: "/agents/{agent_id}/reclassifications"
tags: ["Reclassification"]
---

# List reclassification history

`GET /agents/{agent_id}/reclassifications`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/agents/{agent_id}/reclassifications`
- Auth: none required

Retrieve the history of all checkpoint reclassifications for the specified agent. Each entry includes the original and reclassified type, reason, and score impact. Public: members of the agent's org see the full records; every other caller (including anonymous) sees a redacted view with `id`, `agent_id`, `before_verdict`, `after_classification`, `score_before`, `score_after` and `created_at` only. An unknown or deleted agent id returns 404, the same body as `GET /agents/{agent_id}`; a real agent with no records returns an empty list.

## Path parameters

- `agent_id` string, required

## Query parameters

- `limit` integer
- `offset` integer

## Response `200`

Reclassification history — a bare array of reclassification records, newest first.

- ReclassificationResult[]
  - `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

- `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)