Introducing Memory Policies

As out platform continues to grow and captures more of an AI workload. There will always be new features & improvements we can make. This is one of those, we've always had and seen a need in the platform to direct and instruct our memory generation layer. This is what memory polices offers - the ability to guide Mnexium's memory layer.

Why Memory Policies?

Not every app wants to memorize everything. Some teams need strict extraction rules for compliance, quality, or cost. Others need per-workflow behavior, like high-signal extraction in support chats and minimal extraction in casual chats.

Memory Policies let you define those rules once, then apply them automatically with scope-aware resolution.

API Endpoints

Memory Policies are now available on the v1 API surface and our UI

GET    /api/v1/memory/policies
POST   /api/v1/memory/policies
GET    /api/v1/memory/policies/:id
PATCH  /api/v1/memory/policies/:id
DELETE /api/v1/memory/policies/:id
GET    /api/v1/memory/policies/resolve

SDK Example

Default policies are automatically applied

// npm: @mnexium/sdk
import { Mnexium } from "@mnexium/sdk";

const mnx = new Mnexium({
  apiKey: process.env.MNX_KEY,
  openai: { apiKey: process.env.OPENAI_API_KEY },
});

const alice = mnx.subject("user_123");
const response = await alice.process({
  content: "Remember that I prefer concise weekly summaries.",
  model: "gpt-4o-mini",
  learn: true,
  recall: true,
  memory_policy: "mem_pol_support_assistant",
});

console.log(response.content);

What This Enables

Memory Policies give teams a practical control plane for extraction quality. You can tune behavior once and keep it consistent across chat/completions, responses, messages, and Gemini routes.

The result: cleaner memory, lower noise, and more predictable assistant behavior over time.

Get Started

Memory Policies are available now in both SDKs and the REST API. Create a policy, set scoped defaults, or pass memory_policy per request. Your assistant will start extracting cleaner, higher-signal memory immediately.

Blog

Docs