add() and get().
Current production choices
| Tenant domain | Status | Use for |
|---|---|---|
| General Engine | Available | Any AI product that needs durable user facts, preferences, goals, procedures, relationships, or expertise |
| EdTech Schema | Available | Tutoring, exam prep, learning apps, student dashboards |
| Customer Support Schema | Available | Support agents, support copilots, customer continuity, escalation context |
Upcoming domains
| Domain | Current docs posture |
|---|---|
| HR Tech | Coming soon; use the general engine for production HR products today |
| HealthTech | Coming soon; use the general engine for production healthcare products today |
| AgriTech | Planned |
Decision guide
Use the general engine when:- the product does not need domain-specific structured profiles
- you only need prompt-ready memory context
- you want the fastest integration path
- users are students, learners, teachers, tutors, or education admins
- the AI should remember weak topics, strong topics, grade level, curriculum, exams, or learning style
- you need student profile data for dashboards
- users are customers contacting support
- the AI should remember open issues, customer preferences, sentiment patterns, and escalation risk
- support admins need customer memory summaries or support stats
Activation
Check available domain choices:Integration rule
Do not branch your main model-call path by domain unless your product UI needs it.When to use profile endpoints
Use profile or tenant domain endpoints for dashboards and settings screens. Useget() for model calls.
| Need | API |
|---|---|
| Prompt context for an AI response | POST /v1/memories/retrieve or SDK get() |
| Store conversation memory | POST /v1/memories/add or SDK add() |
| Student profile UI | GET /v1/memories/edtech-profile |
| Support customer dashboard | GET /v1/tenant/customers |
| Support aggregate stats | GET /v1/tenant/support-stats |
| Tenant domain settings | GET /v1/tenant/domain-schema or PATCH /v1/tenant/domain-schema |