Skip to main content
MemoryOS exposes its current operating mode on every response so your app keeps running regardless of what’s happening with memory.

​
Modes

ModeMeaning
FULLNormal — reads and writes work as expected
PASSTHROUGHMemory context should be skipped — continue the LLM call without it
DEGRADED_RETRIEVERetrieval is reduced — fewer or zero memories may return
BLOCKEDWrites are blocked by quota governance

​
Response headers

HeaderMeaning
X-MemoryOS-Quota-ModeCurrent mode
X-MemoryOS-Budget-RemainingRemaining budget as a percentage
X-MemoryOS-Quota-ResetNext reset timestamp
X-MemoryOS-Circuit-StatusOverall dependency health
X-MemoryOS-Processingnormal or delayed

​
Handling passthrough

result = client.get(
    query=user_message,
    external_user_id="customer-123",
)

prompt_addition = "" if result.is_passthrough else result.system_prompt_addition
The rule is simple: always make the LLM call. Only skip MemoryOS context when passthrough is active.

​
Webhooks

Operational events include quota.warning, quota.critical, quota.exhausted, quota.reset, mode.changed, processing.delayed, and processing.recovered. See Webhooks for payload format and signature verification.