> ## Documentation Index
> Fetch the complete documentation index at: https://docs.memloom.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# List all active memories

> Every active memory, newest first. Use this to browse the store; use /memory/query
for relevance-ranked recall. Stale (superseded) memories are excluded.




## OpenAPI

````yaml /openapi.yaml get /memory/list
openapi: 3.1.0
info:
  title: memloom local API
  version: 0.1.0
  description: >
    The HTTP API served by the `memloom serve` daemon on your machine. The CLI,
    the MCP server,

    and the viewer all route through this API. The daemon is the single owner of
    the store, so

    every client shares one consistent view of your memories.


    No authentication: the daemon binds to `127.0.0.1` only and is reachable
    solely from your

    own machine. Browser clients on other localhost ports are allowed via CORS.
servers:
  - url: http://127.0.0.1:4319
    description: Local memloom daemon
security: []
paths:
  /memory/list:
    get:
      summary: List all active memories
      description: >
        Every active memory, newest first. Use this to browse the store; use
        /memory/query

        for relevance-ranked recall. Stale (superseded) memories are excluded.
      operationId: listMemories
      responses:
        '200':
          description: The active memories.
          content:
            application/json:
              schema:
                type: object
                properties:
                  memories:
                    type: array
                    items:
                      $ref: '#/components/schemas/Memory'
components:
  schemas:
    Memory:
      type: object
      properties:
        id:
          type: string
        ownerId:
          type: string
        status:
          type: string
          enum:
            - active
            - stale
        memoryType:
          type: string
          description: >-
            The kind of memory: one of `fact`, `preference`, `episode`,
            `procedure`. Recall results for ingested context chunks carry the
            sentinel `context` (see `kind`).
          example: fact
        canonical:
          type: string
          nullable: true
        content:
          type: string
        summary:
          type: string
          nullable: true
        assertedAt:
          type: string
          format: date-time
        createdAt:
          type: string
          format: date-time
        similarity:
          type: number
          description: >-
            Cosine similarity to the query (meaning signal alone). Present on
            recall results.
          example: 0.85
        rrfScore:
          type: number
          description: >-
            Fused reciprocal-rank-fusion score. Rank-based and small by design.
            Use it for ordering; it is not a percentage.
          example: 0.0328
        kind:
          type: string
          enum:
            - memory
            - context
          description: >-
            Whether this result is a saved memory or a chunk of an ingested
            context document.
        source:
          type: object
          description: >-
            Present on context-chunk results; describes where the text came
            from.
          properties:
            documentId:
              type: string
            title:
              type: string
              example: Deploy Guide
            path:
              type: string
            headingPath:
              type: string
              nullable: true
              example: Deploy Guide > Database
            page:
              type: integer
              nullable: true
              description: 1-based PDF page.

````