What to Use First (API Map)

Here’s a clean rewrite of that section with the missing concept clearly communicated, without adding noise or changing your intent. I’ve only added what’s necessary to explain the default pod floor behavior.

Most applications do not need every FloorMemory API.

Start small.

Minimum APIs for Most Apps

You can build a complete assistant using just:

Query API

Conversational interaction with memory

Create Event

Add knowledge to a Floor

Get Conversations

Resume past conversations (optional)

Everything else is optional.

🚀 Important: Default Pod Floor (Auto-Created)

When a developer creates an App ID in the xFloor Developer Console, xFloor automatically creates a default Floor for that app.

This default Floor:

Is owned by the developer

Acts as the pod / memory container for that App

Requires no manual floor creation

Can immediately accept Create Event and Query calls

Is ideal for:

first-time integrations

prototypes

single-assistant applications

👉 In most cases, you do not need to create a Floor explicitly to get started.

You can start using FloorMemory APIs immediately with the auto-created pod floor.

When to Use Other APIs

API Group	Use When
Feed APIs	Showing recent activity
Registration APIs	You don’t manage users
Floor Management	Admin dashboards or multi-floor apps
Password APIs	xFloor-managed identity

Recommended First Build

Create an App ID (default pod floor is auto-created)

Add content using Create Event

Ask questions using Query API

Iterate on prompts and content

Do not start with:

Registration

Feeds

Advanced filters

Floor management APIs

Those come later—only if needed.

TL;DR

Create App → Get Pod Floor → Add Content → Ask Questions

That’s enough to build a useful assistant.

Minimum APIs for Most Apps#

🚀 Important: Default Pod Floor (Auto-Created)#

When to Use Other APIs#

Recommended First Build#

TL;DR#

Minimum APIs for Most Apps

🚀 Important: Default Pod Floor (Auto-Created)

When to Use Other APIs

Recommended First Build

TL;DR