Agent Hints
Domain-specific guidance that steers the extraction and retrieval models: custom terminology, extraction priorities, retrieval preferences. Agent hints are derived from your use-case file when Synap generates the Instance’s Memory Architecture. For example, a medical support agent’s use-case file would lead Synap to prioritize extracting medication names and dosages.API Key
The primary credential for SDK authentication. Generated from the Dashboard, prefixed withsynap_. Multiple keys can be active per instance. The raw key is shown only once at generation time; only the SHA-256 hash is stored server-side. See Authentication.
Client
The top-level organizational entity in Synap, representing your company or team. A client owns one or more instances and is identified by a client ID in the formatcli_<hex16>. All API keys, billing, and team management are scoped to the client level. See Clients and Instances.
Compaction
The process of condensing a conversation’s accumulated context into a shorter summary while preserving the most important information. Compaction reduces token usage when injecting context into LLM prompts. Strategies includeadaptive, aggressive, balanced, and conservative. See Context Compaction and the Context API.
Confidence Score
A numerical value between0.0 and 1.0 assigned to each extracted memory indicating how certain the extraction model is that the information is accurate and correctly categorized. The minimum confidence threshold is auto-tuned by Synap from your use-case file. Memories below the threshold are discarded during ingestion.
Context Budget
The maximum number of tokens allowed in a context response. The context budget prevents the retrieval system from returning more data than the downstream LLM can process. Auto-set per instance by Synap from your use-case file.Context Response
The structured output returned by the Context Fetch method. Contains ranked memories organized by type (facts, preferences, episodes, emotions), along with metadata about query performance and token usage.Correlation ID
A unique request identifier returned by the SDK on every response and surfaced on every error. The correlation ID traces a request through the entire Synap processing pipeline, including asynchronous jobs. Always include the correlation ID when contacting support. Format:syn_<instance_prefix>_<timestamp_ms>_<random> (e.g. syn_abc123_1706123456789_x7k9m2).
Customer
A scoping entity within a client that represents an end-customer or account. Memories scoped to a customer are accessible by all users within that customer but isolated from other customers. Part of the scope chain. See Scopes.Entity Resolution
The process of identifying and linking mentions of the same real-world entity across different conversations and documents. For example, “John”, “John Smith”, and “my manager” may all resolve to the same person entity. Synap uses semantic matching to resolve entities. Unresolved entities are auto-registered at the CUSTOMER scope. See Entities and Resolution.Episode
A memory type representing a narrative account of an event or interaction. Episodes capture “what happened” with temporal context. Example: “User described a frustrating experience trying to set up their printer last weekend.” See Memory Lifecycle.Emotion
A memory type representing an emotional state, sentiment, or feeling expressed in a conversation. Example: “User expressed excitement about their upcoming vacation.” See Memory Lifecycle.Fact
A memory type representing objective, factual information extracted from conversations. Facts are statements about the world, the user, or their circumstances. Example: “User works at Acme Corp as a senior engineer.” See Memory Lifecycle.Graph Store
One of two storage backends used by Synap. The graph store maintains entity relationships and traversal paths, enabling queries like “find all memories related to this person’s workplace.” Graph queries complement vector store similarity search for deeper contextual retrieval. See Storage Engines.Ingestion
The asynchronous pipeline that processes raw documents into structured memories. The pipeline has four stages: extraction (identifying memory-worthy content), categorization (classifying into memory types), entity resolution (linking entity mentions), and storage (writing to vector and graph stores). See Memory Lifecycle and the Ingestion SDK.Instance
An isolated memory store for a single AI agent, belonging to a client. Each instance has its own Memory Architecture (auto-generated by Synap from your use-case file), authentication credentials, and usage metrics. Instances are identified byinst_<hex16>. See Clients and Instances and Managing Instances.
MACA (Memory Architecture Configuration)
The per-instance configuration that controls how Synap processes, stores, and retrieves memories. Synap generates it automatically from the use-case file you upload at Instance creation; you do not author it by hand. To change behavior, re-upload an updated use-case file. See Customized Memory Architectures.Memory
A unit of structured knowledge extracted from a document during ingestion. Memories are typed as facts, preferences, episodes, emotions, or temporal events. Each memory has a confidence score, scope, and linked entities. See Memory Lifecycle.Memory Category
The classification of a memory into one of the supported types:fact, preference, episode, emotion, or temporal_event. Categories are determined during the categorization stage of ingestion. The set of active categories is configurable in MACA.
Memory Type
See Memory Category.Namespace
An isolated storage partition within the vector store or graph store. Each instance gets its own namespace to ensure memory isolation. Namespace identifiers are auto-generated based on the instance ID.Preference
A memory type representing a user’s opinions, likes, dislikes, or behavioral preferences. Example: “Prefers light roast coffee, especially pour-over method.” See Memory Lifecycle.Primary Scope
The most specific scope in the scope chain that a memory belongs to. Determines the default visibility of the memory. A memory withuser_id set has USER as its primary scope; with only customer_id, it has CUSTOMER scope.