Skip to content
Developer docs
Docs menu

Glossary

Markdown

The terms these docs use, each defined in one sentence and linked to the page that explains it.

TermDefinitionExplained in
SpaceThe boundary for permissions and paths, within which members, roles, and the file tree are kept, with one default Space per account.Core concepts
EntryThe stable identity of a source, such as a file, a URL, or a piece of text.Core concepts
VersionAn immutable record of an Entry's content, made each time the content changes.Core concepts
Knowledge stateThe processing progress of an Entry, reported in knowledge.state.Core concepts
MemoryA statement with a scope, a status, and a source, which is an account memory, a memory written as an Entry, or a fact distilled from an Entry.Memory
Memory scopeWhat a memory belongs to: project is one Space, agent is one Agent, and account is the account.Memory
Memory statusWhere a memory stands in review: candidate, confirmed, rejected, or superseded.Memory
PrincipalThe person (kind: human) or Agent (kind: agent) a request acts as; an API key belongs to a principal and is not one itself.Permissions
CapabilityPermission for one kind of operation, such as knowledge:read or knowledge:write.Permissions
API keyThe credential sent on every request as Authorization: Bearer mb_live_..., which can only narrow its principal.Authentication and API keys
AgentA principal of kind: agent, with its own permissions, memory, and audit identity.Permissions
Context packWhat context returns for a task: sources the service picked and packed within a token budget, with its choices explained in route.Retrieval and context
CitationThe [cN] id of one source in a context pack, which an answer uses to mark where a statement comes from.Retrieval and context
BranchA copy-on-write layer over a Space's main line, used as an Agent's workspace, whose paths become versions on main only when merged.Branches and mounts
CheckpointA record of a branch's own changes at one moment, which the branch can roll back to.Branches and mounts
SnapshotA record of every file's path and version in a Space at one moment, which copies no bytes.Sync, snapshots, and export
ProposalA write an Agent submits for a file owned by someone else, which becomes a new version only when a reviewer approves it.Files and versions
JobWork that cannot finish within the request, which returns 202 with a job_id that you poll until the status is final.API conventions
Read rootThe read_root the Space owner sets on a member, which limits reads to that directory and returns 404 for paths outside it.Permissions
Write rootThe write_root the Space owner sets on a member, which limits writes to that directory.Permissions
Idempotency keyThe Idempotency-Key header on a write, which lets you send the write again without running it twice.API conventions
CursorAn opaque string a list or the change feed returns, used to read the next page or continue.API conventions
ETagThe id of a file's latest version, used for conditional writes and reads.API conventions
Offline consolidationAn optional deployment feature that tidies existing memories while no Agent is working, without generating new content; each run is called a dream in the API.Memory

Next steps