@xfloor-memory-sdk
  1. Get Started
@xfloor-memory-sdk
  • Get Started
    • Overview
    • Quick Start
    • Authentication and Identification
    • Core Concepts (5-Minute Read)
    • What to Use First (API Map)
  • SDK
    • Overview
    • SDK Installation & Setup
    • Python SDK
    • JavaScript SDK
    • Typescript SDK
    • Java SDK
    • FAQ & Troubleshooting
    • Copy-Paste Debug Checklists
  • Core FloorMemory
    • Query (Primary API)
      POST
    • Create Event (Post Content)
      POST
    • Recent Events
      GET
    • Basic information of a floor
      GET
  • Floor Management
    • Edit floor
      POST
    • Make floor Private
      POST
    • Make floor public
      POST
    • Rename floor
      POST
  • Registration
    • Sign Up
      POST
    • Sign In with email ID
      POST
    • Sign In with Mobile number
      POST
    • Validation
      POST
    • Change Password
      POST
    • Reset Password
      POST
    • Change email ID
      POST
    • Change Mobile number
      POST
    • Send Validation code
      POST
    • External User Registration
      POST
  • SDKs
  • Schemas
    • PostAdd
    • QueryResponse
    • Media
    • UserDetails
    • SignUpResponse
    • BlockDetails
    • FloorInfo
    • Threads
    • EventResponse
    • 400ErrorCode
    • Remaining
  1. Get Started

Core Concepts (5-Minute Read)

This page explains the minimum concepts you need to use FloorMemory APIs correctly.

Floor#

A Floor is an isolated knowledge and conversation space.
Examples:
A college or institution
A course or subject
A company knowledge base
A personal assistant
All conversations, memory, and retrieval are scoped to a Floor.
A Floor is:
Not a folder
Not a database
A memory boundary

Content#

Content is added to Floors using Events.
Examples:
Posts
Announcements
Articles
Quizzes
This content becomes retrievable during conversations.

Conversation#

A conversation:
Belongs to a user
Is scoped to a floor
Persists across turns
Evolves over time
You do not manage conversation IDs manually.
FloorMemory handles this automatically.

Memory#

Memory is built from:
Past user messages
Past assistant responses
Relevant floor content
Each new query:
Loads relevant memory
Grounds responses in content
Updates memory

One Mental Model#

User → Floor → Content → Memory → Conversation
If this makes sense, you are ready to use the APIs.
Modified at 2026-01-21 09:43:05
Previous
Authentication and Identification
Next
What to Use First (API Map)
Built with