Record types
Every memory record has a type that describes what kind of thing it is.
Each record also carries a provenance class, which records its origin and
governs how it is used. See Core concepts for the
full set of provenance classes.
Core objects
Memory record
The unit of memory. Carries its record type, provenance, domain, a content
summary, and an embedding, along with lifecycle fields such as whether it is
active and which record it supersedes.
Session
A conversation. Tracks its title, message count, and whether it is active or
archived, and can be associated with a project.
Project
A named workspace that groups sessions and sources, and can carry its own
custom instructions.
Instructions
Per-user global instructions such as display name, language, response style,
domain, and custom instructions.
Project source
An ingested document registered to a project, with a title, source type,
ingest status, and chunk count.
Conversation message
A single message in a session. Conversation messages are chat history and
are never eligible for retrieval into the SIP.
Field lists above name only the top-level attributes that matter for using the
API. The authoritative schema for every object lives in the
API Reference.