Retract a memory
POST/v1/projects/:project_id/memories/:memory_id/retract
Retires a fact that stopped holding with nothing replacing it. The memory leaves the default listing, knowledge search and write deduplication, so restating the fact later lands as a new memory.
It is an invalidation with no successor, which is what tells it apart from a supersede: invalidated_at is set and superseded_by_memory_id stays null. The retraction is appended to the assertion ledger with outcome retracted, so who withdrew the fact is part of the record.
The memory stays readable by id, with its text and its assertions. DELETE remains the way to remove it outright.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 413
- 429
- 500
- 502
- 4XX
The retracted memory
The request was malformed or failed validation.
Unauthorized
Forbidden
Memory store or memory not found
The memory is already invalidated (MEMORY_ALREADY_INVALIDATED), or it has moved past the version this write read (VERSION_CONFLICT, with meta.current_version).
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Internal server error
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there