Reference
Glossary.
One-line definitions of the terms used across these docs. PAMbase is “OAuth for AI memory”: each user has one memory store, and apps connect to it with scoped consent. Follow the links for the full treatment.
| Term | Definition |
|---|---|
| memory store | The single, auto-provisioned home for one user's memory — exactly one per user, shared across every connected app. |
| memory | A durable, natural-language fact about the user (a fact, preference, goal, etc.) — distinct from the raw event that produced it. |
| remember | Writing a natural-language memory via remember() (POST /v1/memories) — a content string plus a kind and scope. Any app can write; no LLM needed. |
| recall | Reading the memories most relevant to a query via recall(). Returns natural language for your LLM to interpret and act on. |
| signal | An ephemeral notification one app emits (emitSignal()) that fans out to subscribers — never stored as memory. |
| kind | An advisory structural hint on a memory (fact, preference, event, …). Free-form and not enforced — unlike scope, which is validated. |
| scope | A permission string like memory:read:fitness that gates what a connection may read or write — and the domain a memory lives in. |
wildcard | A * qualifier (e.g. health.* or *) that grants a whole namespace at once — see the Catalog. |
| intent | A named reason for reading context (e.g. coach) that GET /v1/context tailors its bundle to, gated by context:read:<intent>. |
| context bundle | The assembled payload for an intent: light identity, relevant memories, relationships, and adaptation suggestions. |
| brief | A prompt-ready one-paragraph summary of the user's assistant, cached 5 minutes, from GET /v1/identity/brief. |
| tone | The optional one-line personality note (personality.description) exposed under identity:read — the only personality data PAMbase surfaces. |
| connection token | The long-lived bearer credential your app gets after OAuth; sent as Authorization: Bearer … on every app request. |
client_id / client_secret | Your app's public identifier and private key, used at POST /v1/oauth/token to exchange a code for a connection token. Never expose the secret. |
| gateway | PAMbase's hosted-inference path (POST /v1/gateway/chat) that runs a model with the user's memory injected. |
hosted vs BYOK | Hosted = let the gateway run the model and meter tokens; BYOK (bring your own key/model) = you fetch context and call your own LLM. |
| proactive layer | Outbound delivery: PAMbase POSTs webhook events to apps that hold a subscription, so they can react without polling. |
| webhook / subscription | A webhook is the signed POST PAMbase sends; a subscription is the registered endpoint + signing secret that receives it. |
| scheduled trigger | A future-dated job created with POST /v1/schedule that delivers a schedule.fired webhook when it fires. |
| catalog | The shared vocabulary of standard scopes, event types, intents, and memory kinds that lets apps interoperate. |
standard vs custom | Standard names are in the catalog and recognized ecosystem-wide; custom names work identically but are only discoverable via the ecosystem view. |
importance / confidence / pinned | Per-memory signals: importance and confidence are 0–100; pinned forces a memory to always be considered. |
idempotency (X-PAMbase-Delivery) | The per-delivery id on every webhook; dedupe on it so retried deliveries are processed once. See Data model. |