Removes one memory entry.
DELETE
/v1/m/knowledge/memory/{id}
const url = 'https://example.com/v1/m/knowledge/memory/example';const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request DELETE \ --url https://example.com/v1/m/knowledge/memory/example \ --header 'Authorization: Bearer <token>'Removes one memory entry. The declared read context gates a scoped entry exactly like a read (a session can only delete what it can see; mismatch is a 404, no existence leak), AND an entry classified ABOVE the caller’s clearance is equally invisible (E5 — “you can only act on what you can see” holds on the classification axis too, so a low-clearance writer cannot destroy an entry it may not read).
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ” id
required
string
Path parameter id.
Header Parameters
Section titled “Header Parameters ” X-Olivares-Tenant
string format: uuid
Target tenant id; required when the principal can act in more than one tenant.
Responses
Section titled “ Responses ”OK
Media type application/json
object
Example generated
{}Bad request
Media type application/json
object
Example generated
{}Unauthenticated
Media type application/json
object
Example generated
{}Forbidden
Media type application/json
object
Example generated
{}Not found
Media type application/json
object
Example generated
{}Conflict / setup required
Media type application/json
object
Example generated
{}Rate limited
Media type application/json
object
Example generated
{}