---
title: "Delete a quarantine item without releasing"
method: DELETE
path: "/safe-house/quarantine/{quarantine_id}"
tags: ["Safe House"]
---

# Delete a quarantine item without releasing

`DELETE /safe-house/quarantine/{quarantine_id}`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/safe-house/quarantine/{quarantine_id}`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`
  - API key in cookie `mnemom_session`

Marks the item `deleted`. The underlying content hash is retained for audit. No refund of the original (blocked) prompt to the calling agent. Authorization: the caller must be authenticated, resolve to an organization and hold the owner, admin or member role in it (viewers and auditors are read-only and get 403), and `quarantine_id` is matched scoped to that org's own agents, so a record owned by another tenant returns 404 and no other tenant's item can be deleted.

## Path parameters

- `quarantine_id` string, required

## Response `200`

Deleted.

- object
  - `quarantine_id` string
  - `status` 'deleted'

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