Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.gurubase.ai/llms.txt

Use this file to discover all available pages before exploring further.

End-User Memory lets your Guru tailor its answers to the person asking. You pass an end-user profile (name, plan, region, history, anything else useful) into Gurubase via the Upsert Profiles API. When that same user asks a question, the Guru uses the stored profile as context, so answers stay consistent across sessions, channels, and devices. This is the Memory-Powered Personalization feature surfaced as a first-class product capability.

​
What Memory Unlocks

Plan-Aware Answers

A Pro-plan customer asking about quotas sees Pro-plan limits; a Free user sees Free limits, automatically.

Cross-Session Continuity

The Guru remembers what was asked yesterday, last week, and last quarter without re-asking the user every time.

Per-User Refusals

Combine memory with source-level RBAC so the Guru only cites what each user is entitled to see.

​
How It Works

1

Identify the user

Generate or reuse a stable external_user_id for each end user in your application. This is the key Gurubase will use to look up the user’s memory.
2

Upsert the profile

Call POST /{guru_slug}/profiles/ with a JSON memory object. The structure is up to you - name, plan, region, account tier, recent activity, anything that helps the Guru answer better.
3

Pass the user into questions

When the user asks a question, include the same external_user_id in your Ask Question call. The Guru pulls the stored profile and grounds its answer with both the knowledge base and the user context.
4

Update over time

Re-upsert the profile whenever something changes (plan change, new permission, new context). The Upsert endpoint is idempotent, so you can safely call it on every relevant event.

​
Example Profile Payload

POST /{guru_slug}/profiles/
{
  "users": [
    {
      "external_user_id": "user-7f3a-9b21",
      "memory": {
        "name": "Sarah E.",
        "email": "[email protected]",
        "plan": "Pro",
        "region": "EU",
        "department": "Sales",
        "preferred_language": "English",
        "last_topics": ["pricing", "renewal"]
      }
    }
  ]
}
The memory object structure is fully open. Pass whatever your application knows about the user that the Guru should use as context.

​
Pairs Well With

Smart Triage

Triage uses memory to skip clarifying questions the Guru already knows the answer to.

Actions

Actions can use memory fields (e.g. customer_email, plan) as parameters when calling your APIs.

PII Masking

Mask personal data in answers and logs even while the Guru uses it as context internally.

Audit Logs

Every memory-informed answer is logged with the external_user_id that drove it.

​
API Reference