Skip to main content
Reference

FAQ

Frequently asked questions about memory

Generated fragments and profiles have no expiry date (unless you configured an expiry when creating the memory). You can delete unneeded memories anytime via console or API.
Memory storage and retrieval are isolated by entity (user_id). Different users' memories don't interfere. You can also create multiple memories for different business scenarios.
Memory is a full upgrade of the previous long-term memory. Key differences: memory is an independent management container, supports more flexible rule configuration, adds user profiles, and optimizes retrieval quality, cost, and latency.
Fragments suit specific events and info (e.g., "User went to Beijing last week"). Profiles suit structured attributes (age, occupation, preferences). Use profiles for fixed attributes, fragments for dynamic events. Both can be used together.
On the memory list page, click View details. The Memory details tab shows counts for fragments, profiles, and entities.
Test in the Memory search tab; adjust the similarity threshold (recommended 0.5~0.7); enable intent recall to avoid irrelevant searches; enable rewrite and rerank for accuracy; set max results appropriately.
The default memory cannot be deleted, but you can edit its name, description, and rules. It has a preset "Default project" fragment rule with 180-day expiry that you can modify or supplement.
All endpoints share a 3000 QPM limit (account level). Fragment add is 120 QPM, fragment search is 300 QPM. See Rate limits.
Pro enables Rerank (result reranking) for higher quality but higher cost. Lite disables Rerank for lower cost. Use Pro for accuracy-critical scenarios, Lite for high-frequency, cost-sensitive ones. Add call version is set by the rule's plan_version. Search call version is controlled by the request parameter plan_version. See Billing.
Add and Search free quotas are valid for 3 months from the commercialization date. 10,000 free storage entries have no expiry.
Yes. Edit the rule in the console to change the plan version, or use the UpdateProfileSchema API to modify the plan_version field. New writes follow the updated version; existing memories are unaffected.