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

# Core memory entries of the assistant’s bucket

> Lists the standing entries (persona, instructions, decisions, profile) of the bucket the assistant resolves for the given tenant/subtenant, plus the deployment caps. `enabled: false` (with no entries) when the assistant does not have the core memory tier on.



## OpenAPI

````yaml GET /v1/memory/assistants/{identifier}/core
openapi: 3.0.0
info:
  title: Devic.ai Public API
  description: >-
    Devic.ai is an AI platform that allows you to create, manage, and use AI
    agents for various tasks.
  version: 1.0.0
  contact:
    name: Devic.ai Support
    url: https://devic.ai
  x-logo:
    url: https://devic.ai/logo.png
    altText: Devic.ai Logo
  x-summary: Public API for interacting with Devic.ai platform
servers:
  - url: https://api.devic.ai
    description: Production server
  - url: https://staging-api.devic.ai
    description: Staging server
security:
  - bearerAuth: []
tags:
  - name: Projects
    description: Group agents, assistants, documents and costs into projects
  - name: Documents
    description: >-
      Knowledge base documents: create, version, attach and index markdown
      content for RAG
  - name: Document Folders
    description: Organise knowledge base documents into folders and attach them in bulk
  - name: Files
    description: Upload files and obtain shareable download URLs to attach to messages
  - name: Agents
    description: Endpoints related to AI agents and their operations
  - name: Assistants
    description: Endpoints for interacting with assistants and their specializations
  - name: Tool Servers
    description: Endpoints for managing tool servers and their tool definitions
  - name: Health
    description: API health check endpoints
  - name: Documentation
    description: Endpoints for retrieving markdown documentation
  - name: Integrations
    description: Connect third-party apps and turn them into tools
  - name: Triggers
    description: Start an agent or an assistant from an app event
  - name: Tenant Integrations
    description: Apps that each end user connects for themselves
  - name: Memory
    description: What an assistant remembers between conversations
  - name: Skills
    description: Reusable instruction packs for agents and assistants
  - name: Speech to Text
    description: Audio transcription
  - name: Tenants
    description: Tenants, subtenants and their usage
  - name: MCP Gateway
    description: One MCP endpoint over many servers, with visibility per user
  - name: Tenant Sessions
    description: Tokens that prove which end user is calling
paths:
  /v1/memory/assistants/{identifier}/core:
    get:
      tags:
        - Memory
      summary: Core memory entries of the assistant's bucket
      description: >-
        Lists the standing entries (persona, instructions, decisions, profile)
        of the bucket the assistant resolves for the given tenant/subtenant,
        plus the deployment caps. `enabled: false` (with no entries) when the
        assistant does not have the core memory tier on.
      operationId: listCoreMemory
      parameters:
        - name: identifier
          required: true
          in: path
          description: Assistant identifier
          schema:
            type: string
        - name: tenantId
          required: false
          in: query
          schema:
            type: string
        - name: subtenantId
          required: false
          in: query
          schema:
            type: string
        - name: includeArchived
          required: false
          in: query
          description: Also return archived (superseded/removed) entries
          schema:
            type: string
        - name: userUID
          required: false
          in: query
          description: >-
            Whose bucket to address when the assistant's memory owner is
            per-user (`owner: "user"`), ignored otherwise. Administrator
            principals — API keys among them — may name any user of the account,
            which is how an integration serves each of its end users; a person's
            own token always resolves to its own bucket.
          schema:
            type: string
      responses:
        '200':
          description: Success
        '401':
          description: Unauthorized - Invalid or missing token
        '429':
          description: Too Many Requests - Rate limit exceeded
        '500':
          description: Internal Server Error
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Use JWT token for authentication

````