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

# Rename or retype an entity

> A rename re-embeds the entity, since the embedding is computed from the name. It is
refused with 409 when another entity already owns that name key; use merge instead.
A retype must name an active vocabulary type.




## OpenAPI

````yaml /openapi.yaml patch /memory/entities/{id}
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/entities/{id}:
    patch:
      summary: Rename or retype an entity
      description: >
        A rename re-embeds the entity, since the embedding is computed from the
        name. It is

        refused with 409 when another entity already owns that name key; use
        merge instead.

        A retype must name an active vocabulary type.
      operationId: updateEntity
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                name:
                  type: string
                  example: PostgreSQL
                entityType:
                  type: string
                  example: technology
      responses:
        '200':
          description: Entity updated.
          content:
            application/json:
              schema:
                type: object
                properties:
                  ok:
                    type: boolean
                    example: true
        '400':
          $ref: '#/components/responses/ValidationError'
        '404':
          description: No such entity.
        '409':
          description: The new name collides with an existing entity.
components:
  responses:
    ValidationError:
      description: The request body failed validation. `issues` names each offending field.
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: string
                example: invalid request body
              issues:
                type: array
                items:
                  type: object
                  properties:
                    path:
                      type: string
                      example: query
                    message:
                      type: string
                      example: query must be a non-empty string

````