---
title: "Delete Domain"
method: DELETE
path: "/api/v1/memory/domain/{domain}"
tags: ["memory"]
---

# Delete Domain

`DELETE /api/v1/memory/domain/{domain}`

## Request

- Base URL: `https://core.mnemoverse.com`
- URL: `https://core.mnemoverse.com/api/v1/memory/domain/{domain}`
- Auth: one of:
  - API key in header `X-Api-Key`
  - HTTP bearer

Delete all atoms in a domain. Hebbian edges are left untouched.

Tenant-scoped: only deletes atoms in the calling org's scope.
Hebbian edges are not swept — see `delete_atom` above for why there
is no such thing as an orphan edge here. Wiping one domain therefore
leaves every association learned over other domains' atoms intact.

Secret-atoms (the caller's Vault) are immutable via this endpoint
(Design 13): they are filtered out before delete, never wiped, and
the count excluded is reported as `skipped_secrets`.

Like `delete_atom`, a wipe that breaks supersession chains says so — as
`superseded_predecessors_left_hidden_count` (an int; `delete_atom` returns
the ids themselves, hence the different name for the different shape),
because a domain can hold arbitrarily many. A predecessor living INSIDE the
wiped domain is deleted alongside its successor and is therefore not "left
hidden"; only predecessors in other domains are.

## Path parameters

- `domain` string, required

## Response `200`

Domain cleared.

- unknown

## Other responses

- `400`: Validation error
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not found
- `422`: Validation Error
- `429`: Rate limited
- `500`: Internal server error
- `503`: Engine not initialized

---

[API](https://skmtc.dev/mnemoverse/apis/mnemoverse-core.md) · [All operations](https://skmtc.dev/mnemoverse/apis/mnemoverse-core/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemoverse/apis/mnemoverse-core/revisions/1f5e0048f017?raw)