Resume (owner or admin): only paused to active, due now.
Send Authorization: Bearer <token>. The token is either a Clerk session JWT or a SmartMemory API key (prefix sm_live_, sm_test_, or legacy sk_).
In: header
Path Parameters
Response Body
application/json
application/json
curl -X PATCH "https://example.com/memory/adapters/string/resume"null{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}Restore Workspace
Restore (authority ``restore``) a hidden workspace before ``restore_until``. At or after it: 409.
Retire Ontology Type
Retire a workspace's own confirmed record class. Scope of this surface is deliberately narrow: `layer == "private"` AND `kind == "record"`, even though core's `retire_type` is kind-agnostic. Core resolves an identifier across the private -> domain -> public layers, so an unguarded route would let any authenticated caller retire an effective PUBLIC or pack class: retiring `decision` would disable a built-in memory type for the whole workspace, from a route whose stated job is retiring the workspace's own declared classes. Contract `record_lifecycle.retire_surface` authorizes confirmed PRIVATE record classes and nothing wider. Entity classes keep the curation queue (reject) as their review action. Widening this surface is a deliberate decision, not a default.