---
title: "Revoke an active exemption"
method: DELETE
path: "/agents/{agent_id}/exemptions/{exemption_id}"
tags: ["Agents"]
---

# Revoke an active exemption

`DELETE /agents/{agent_id}/exemptions/{exemption_id}`

## Request

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

Hard-deletes the exemption row (the governance audit log is the permanent record). Requires org `owner`/`admin`. Idempotency-Key required. Emits `agent.exemption.revoked` and recomposes the agent. See ADR-008. Authorization: the caller must be an owner/admin of the organization that owns `agent_id`, and `exemption_id` is fetched with `agent_id` bound, so an exemption under an agent the caller cannot access, or one belonging to a different agent, returns 404 and never another tenant's data.

## Path parameters

- `agent_id` string, required
- `exemption_id` string, required

## Headers

- `Idempotency-Key` string, required

## Response `200`

Exemption revoked; agent recomposed.

- object
  - `revoked` boolean
  - `exemption_id` string
  - `recomposed` boolean

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