> ## 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.

# Find and fold duplicate entity spellings

> One resolution pass over the entity table. Spellings that are identical apart from
case and punctuation are folded without asking; uncertain pairs are written to the
conflicts queue for review. Idempotent and safe to re-run.

The queue is capped so entity folds cannot bury memory conflicts. Questions that did
not fit are reported as `deferred` rather than dropped silently, and a later pass
picks them up as answers come in.




## OpenAPI

````yaml /openapi.yaml post /memory/entities/resolve
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, so every client shares one
    consistent view of

    your memories.


    ## Owners


    One daemon can serve more than one owner. Every owner-scoped endpoint, reads
    as well as

    writes, acts for the owner named by the `X-Memloom-Owner` request header: a
    uuid, sent on

    every request by a client bound to that owner. A request without the header
    gets the

    daemon's own default owner (`MEMLOOM_OWNER_ID` in its environment, or the
    sentinel owner

    when that is unset), which is what a single-owner install has always used
    and what the

    browser-based Console gets. `GET /health` reports that default.


    A malformed header is refused with 400 rather than coerced. The three
    endpoints that also

    accept an `ownerId` in their body (`/memory/save`, `/context/add`,
    `/context/url`) refuse a

    body value that disagrees with the header, rather than silently preferring
    one.


    Store-wide endpoints carry no owner: the speech-model catalog, reconcile
    settings, the

    connector scopes, the ingest queue, and `/health`.


    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.
    The owner header

    is therefore a separation mechanism, not an authentication one: any process
    on your machine

    can name any owner. It keeps two agents or two people out of each other's
    memories; it is

    not a boundary between untrusted users.
servers:
  - url: http://127.0.0.1:4319
    description: Local memloom daemon
security: []
paths:
  /memory/entities/resolve:
    post:
      summary: Find and fold duplicate entity spellings
      description: >
        One resolution pass over the entity table. Spellings that are identical
        apart from

        case and punctuation are folded without asking; uncertain pairs are
        written to the

        conflicts queue for review. Idempotent and safe to re-run.


        The queue is capped so entity folds cannot bury memory conflicts.
        Questions that did

        not fit are reported as `deferred` rather than dropped silently, and a
        later pass

        picks them up as answers come in.
      operationId: resolveEntities
      parameters:
        - $ref: '#/components/parameters/OwnerHeader'
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                dryRun:
                  type: boolean
                  default: false
                  description: Report the plan without changing anything.
      responses:
        '200':
          description: What the pass did.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EntityResolutionResult'
components:
  parameters:
    OwnerHeader:
      name: X-Memloom-Owner
      in: header
      required: false
      description: >
        The owner this request acts for. Applies to every owner-scoped endpoint,
        reads as well

        as writes. Omit it and the daemon's own default owner answers (see `GET
        /health`), which

        is what a single-owner install has always used. A value that is not a
        uuid is refused

        with 400 rather than coerced.
      schema:
        type: string
        format: uuid
      example: 11111111-1111-4111-8111-111111111111
  schemas:
    EntityResolutionResult:
      type: object
      description: What one resolution pass did.
      properties:
        examined:
          type: integer
          description: Entities considered.
        pairs:
          type: integer
          description: Pairs that survived bucketing and were judged.
        merged:
          type: integer
          description: Folds applied without asking.
        queued:
          type: integer
          description: Uncertain folds written to the conflicts queue.
        deferred:
          type: integer
          description: >-
            Uncertain folds not written because the queue is already full.
            Reported rather than dropped silently, so "nothing queued" never
            hides "there was more to ask about". A later pass picks them up.
        skipped:
          type: integer
          description: Pairs already merged, queued, or settled as distinct.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.