---
title: "Get AIP drift alerts"
method: GET
path: "/agents/{agent_id}/drift/aip"
tags: ["Drift"]
---

# Get AIP drift alerts

`GET /agents/{agent_id}/drift/aip`

## Request

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

## Path parameters

- `agent_id` string, required

## Response `200`

AIP drift alerts

- object
  - `alerts` DriftAlert[]
    - `alert_id` string
    - `agent_id` string
    - `session_id` string
    - `checkpoint_ids` string[]
    - `sustained_checks` integer
    - `severity` 'low' | 'medium' | 'high'
    - `drift_direction` string
    - `message` string
    - `detection_timestamp` string, date-time
  - `agent_id` string
  - `warnings` object[]: Present only when the response is DEGRADED. Each entry names a data source that could not be read, so a partial answer is never reported as a complete one. `code` is the PostgreSQL SQLSTATE when one is available (e.g. `42703`), otherwise `read_failed`.
    - `source` string, required
    - `code` string, required
    - `message` string, required

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