Skip to main content
GET
Memory Counts

Authorizations

Authorization
string
header
required

Enter your MeshAPI key (rsk_...) — sent as Authorization: Bearer <key>.

Headers

X-Mesh-Version
enum<string>
default:2026-08

Dated version of the API contract to pin this request to. Omit it and the request is served under 2026-08 — the oldest supported version, so an existing integration is never moved by a release. A malformed or unsupported value is rejected with 400 invalid_api_version rather than falling back silently. The version actually served is echoed as X-Mesh-Version on every response, including errors.

Available options:
2026-08

Response

Successful Response

Org-wide totals behind the dashboard's type rail (MESH-467).

Three different things get counted, because the rail and its subtitle answer three different questions and conflating them is how a nav badge starts lying:

  • items — rows of each type the caller can see.
  • expired_items — of those, how many are past expires_at. Still inside items: retention lapses on read, so the row is here to be seen and revived until the sweeper hard-deletes it. Guardrails are always 0 — they never carry a deadline.
  • memories_with — how many MEMORIES hold at least one item of the type, i.e. the length of the list the rail's own view will render.

memories is the total the "All memories" row shows. It counts memories, not items, which is why it is a separate field rather than a fourth key in items.

memories
integer
default:0
items
Items · object
expired_items
Expired Items · object
memories_with
Memories With · object