The memory-pipeline measurement board: raw counters for a period, rates are derived by the consumer.
const url = 'https://example.com/api/memories/metrics';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/memories/metricsParameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Window in days, clamped server-side to 1..=90 (default 7).
Responses
Section titled “Responses”Memory-pipeline Messbrett counters for the workspace and period
One workspace’s memory-pipeline counters over a period. Every field is a raw
count; consumers derive: admission rate = (tier0_filed + distill_nothing +
distill_covered) / (that + admission_rejected), distillation success = distill_distilled /
(distill_distilled + distill_unavailable), inbox decision rate =
proposals_created_decided / proposals_created (BOTH sides are the items
created in the period — dividing the whenever-created proposals_decided
by proposals_created compares two populations and can exceed 100 %),
memories per injection =
injected_memories / injections, citations per injection = citations /
injections.
object
Tier-0 admission form-filter rejections in the period (audit-sourced — before #1228 a rejection left no durable trace at all).
[mem:<uuid>] citations recorded in the period.
#1228 slice 2 — distiller COVERED verdicts in the period: the run’s fact was
already stated by an existing memory the distiller was shown (NOOP <id>;
audit-sourced). Counts in the admission denominator beside NOTHING.
… of which the distillation succeeded.
Distiller NOTHING verdicts in the period (admitted by form, declined by substance; audit-sourced).
… of which the distillation degraded (the un-distilled summary was
filed, flagged unavailable).
The most frequent recorded reason among the degraded ones (03.09.2026), so
a 0 % tile can name whether it looks at a configuration backlog (stage: all
35 were the pre-fix provider 403) or at a broken distiller. null when
nothing degraded or no reason was recorded.
How many of the degraded rows carry that reason.
Total memories those injections carried.
Task context-block injections in the period (one per launched task that received a memory block).
The period actually used (after clamping to 1..=90).
Review items of ANY action created in the period.
Of the items CREATED in the period, how many are decided by now — the
cohort-consistent numerator for the decision rate (a subset of
proposals_created, so the quotient is bounded by 1).
Review items decided (approved or rejected) in the period, whenever they were created — inbox THROUGHPUT, not a rate numerator.
Review items pending RIGHT NOW (all-time inbox load, not a rate).
Tier-0 closeout_standard proposals filed in the period.
Examplegenerated
{ "admission_rejected": 1, "citations": 1, "distill_covered": 1, "distill_distilled": 1, "distill_nothing": 1, "distill_unavailable": 1, "distill_unavailable_reason": "example", "distill_unavailable_reason_count": 1, "injected_memories": 1, "injections": 1, "period_days": 1, "proposals_created": 1, "proposals_created_decided": 1, "proposals_decided": 1, "proposals_pending_total": 1, "tier0_filed": 1}Structured client error
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Authentication required
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Permission denied
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}Structured server error
The canonical JSON body of every error response — the single source of truth
the frontend binds to. Every AppError serializes as this exact shape, and
the generated OpenAPI component ApiErrorBody (with its ErrorCode enum) is
what the frontend error schema is generated from, so there is no hand-written
error schema on either end.
object
Machine-readable, stable error code.
Present only on a quota-exceeded 403 — the inline upgrade-CTA payload.
object
The entitlement feature key that was hit, e.g. apps.max_count.
The plan’s limit for this key.
Where to send the user to upgrade.
Current usage (count or bytes, per the key).
Human-readable message (the server’s English text; the client may localize
by code).
Example
{ "code": "not_found"}