Developer guide
Give every customer a stable memory identity.
Your application owns user identities. Syntarus uses the ID you send to keep each customer’s memory private and consistent.
The simple rule
Create one opaque, stable user_id for each end user and reuse it on every write, search, export, and deletion request.
user_id = "customer_48291" # your internal ID, not an email address
What each identifier means
- Project: the security and billing boundary selected by the API key.
- user_id: one customer’s private memory namespace.
- conversation_id: an optional thread identifier for separating chats.
- agent_id: use when separate agents need separate memory within the same customer.
Use the same ID on every turn
memory.add(
user_id="customer_48291",
messages=[{"role": "user", "content": "I prefer dark mode."}],
)
memory.search(
user_id="customer_48291",
query="What interface does this customer prefer?",
)
Important: Syntarus does not create your application’s customer IDs. Your backend should map its authenticated customer record to this value. Never put a secret API key in browser or mobile code, and avoid using email addresses as IDs.
When a user deletes their account
Call the deletion endpoint with the same user_id. This removes that customer’s project-scoped namespace without affecting other customers.