Where should I start: API, MCP, or Playground?

Start with Playground for quick testing, then use API docs for production integration. Use MCP if your agent framework supports tool-calling workflows.

How do I authenticate API requests?

Pass your MemBrain API key in the request headers as documented in the API reference. Keep keys server-side in production.

Which endpoint stores a memory and is it synchronous?

Use the Store a memory endpoint. Ingestion is asynchronous and returns a job id that you can poll for completion status.

How do I search and traverse graph relationships?

Use search endpoints for semantic recall and graph endpoints for neighborhood expansion, path finding, and traversal across linked memories.

Where can I test requests before coding integration?

Use the Interactive Playground under Docs to run request flows and inspect responses before wiring your app.

Store a memory — MemBrain API Reference

MEMBRAIN

REST API

Store a memory

Store a new memory. This endpoint is asynchronous and returns 202 Accepted with a job_id.

POST/api/v1/memories

Body Parameters

application/json

contentstringrequired

The text of the memory

tagsstring[]

Dot-separated tags like type.preference or domain.ui

categorystring

Optional grouping label

ingestion_scopestring

Optional regex over tags that limits merge/link candidates during ingest only.

API Key

Stored locally, never sent to servers

Store a memory

const options = {  method: 'POST',  headers: {'X-API-Key': 'mb_live_xxx', 'Content-Type': 'application/json'},  body: JSON.stringify({"content": "User prefers dark mode and uses VSCode", "tags": ["type.preference", "domain.ui"], "category": "user-prefs"})};fetch('https://api.mem-brain.io/api/v1/memories', options)  .then(res => res.json())  .then(res => console.log(res))  .catch(err => console.error(err));

{
  "job_id": "job_abc123",
  "status": "queued",
  "message": "Memory queued for processing"
}