Skip to main content

​
What profiles are

Profiles are a convenience layer over memory. Instead of running multiple search calls to gather broad context, call a single endpoint:
This returns a pre-aggregated snapshot of the user’s knowledge base, useful for bootstrapping context at the start of a session.

​
Profile sections

The response has two sections:

​
When to use profiles

Profiles work well for:
  • Application startup - load broad user context in a single call
  • Personalization - tailor content or UI based on known preferences
  • Content generation - provide a persona or style guide derived from memory
  • Support systems - give agents background before the user explains anything
Use profiles for “who is this user?” and search for “what did they decide about X?”. Profiles follow the same scope isolation rules as search and list. A scoped profile never includes memories from another scope, and an unscoped profile only includes global/unscoped memories.

​
Scoping by scope and project

Pass a scope query parameter to build profile context from one isolated memory container only:
Omit scope to build a profile from unscoped/global memories only. You can also add project to narrow the profile inside that scope:
This returns only memories tagged with that project inside user_123.