简介

<p align="center"> <a href="https://brain.inite.ai"> <img src="https://brain.inite.ai/api/og?title=Memory%20with%20context&kind=brand" alt="INITE Brain — memory with context" width="100%"> </a> </p>

INITE Brain

<p align="center"> <b>Open-source memory for AI agents.</b><br> Facts, conversations, events and their evidence — connected across sessions.<br> Temporal history, domain memory models and grounded answers over REST and MCP. </p>

<p align="center"> <a href="https://github.com/inite-ai/inite-brain-service/actions/workflows/ci.yml"><img src="https://github.com/inite-ai/inite-brain-service/actions/workflows/ci.yml/badge.svg" alt="CI"></a> <a href="LICENSE"><img src="https://img.shields.io/badge/license-AGPL--3.0--or--later-blue.svg" alt="License: AGPL-3.0-or-later"></a> <a href="https://github.com/inite-ai/inite-brain-service/stargazers"><img src="https://img.shields.io/github/stars/inite-ai/inite-brain-service?style=flat" alt="Stars"></a> <a href="CONTRIBUTING.md"><img src="https://img.shields.io/badge/PRs-welcome-brightgreen.svg" alt="PRs welcome"></a> <img src="https://img.shields.io/badge/TypeScript-3178c6.svg" alt="TypeScript"> <img src="https://img.shields.io/badge/MCP-native-ffb938.svg" alt="MCP native"> </p>

<p align="center"> <a href="https://brain.inite.ai/en/app/keys"><img src="https://img.shields.io/badge/Claude%20Code-%2Fplugin%20install-d97757.svg" alt="Install in Claude Code"></a> <a href="cursor://anysphere.cursor-deeplink/mcp/install?name=brain&config=eyJ1cmwiOiJodHRwczovL2JyYWluLmluaXRlLmFpL21jcCIsInRyYW5zcG9ydCI6Imh0dHAiLCJoZWFkZXJzIjp7IkF1dGhvcml6YXRpb24iOiJCZWFyZXIgYnJhaW5fWU9VUl9BUElfS0VZIn19"><img src="https://img.shields.io/badge/Add%20to-Cursor-000000.svg" alt="Add to Cursor"></a> <a href="vscode:mcp/install?%7B%22name%22%3A%22brain%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fbrain.inite.ai%2Fmcp%22%2C%22headers%22%3A%7B%22Authorization%22%3A%22Bearer%20brain_YOUR_API_KEY%22%7D%7D"><img src="https://img.shields.io/badge/Add%20to-VS%20Code-0098ff.svg" alt="Add to VS Code"></a> <a href="https://registry.modelcontextprotocol.io/v0/servers?search=inite-brain"><img src="https://img.shields.io/badge/MCP%20Registry-io.github.inite--ai-ffb938.svg" alt="MCP Registry"></a> </p>

<p align="center"> <a href="https://brain.inite.ai">Website</a> · <a href="#architecture">Architecture</a> · <a href="#domain-packs">Domain Packs</a> · <a href="#quick-start">Quick start</a> · <a href="https://brain.inite.ai/en/docs">Docs</a> · <a href="AGENTS.md">Agent guide</a> </p>

Brain gives an agent memory between conversations: what was said, what changed, which entities are involved, and what supports an answer. A bitemporal graph stores structured facts and relationships; source episodes preserve context; scenes and beliefs capture events and evolving state. Domain Packs adapt that memory to a product's vocabulary and lifecycles without forking the engine.

Run Brain on your infrastructure or connect to the hosted service at brain.inite.ai. The web app provides memory search and exploration; REST and MCP provide the integration surface.

Remember something, then ask about it

Text in, facts out. Brain captures the turn, extracts entities and claims, and runs each one through bitemporal conflict resolution:

curl --fail-with-body -X POST "$BRAIN_URL/v1/ingest/mention" \
  -H "Authorization: Bearer $BRAIN_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Maria moved to Berlin in June and prefers morning appointments.",
    "userId": "user_42"
  }'

curl --fail-with-body -X POST "$BRAIN_URL/v1/search" \
  -H "Authorization: Bearer $BRAIN_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "where does Maria live", "userId": "user_42", "limit": 5 }'

Use your application's stable user ID on both writes and reads. Omit userId on both only for tenant-global memory. The userId is also who is speaking: a first-person turn ("I moved to Berlin") lands on the user's own entity, and "where do I live?" on /v1/synthesize is answered to them. The memory learns the user's name from them — "I'm Maria" becomes a name fact on their own entity — or from your onboarding write: /v1/ingest/fact with entityRef: { "vertical": "user", "id": "user_42" }, predicate: "name", the same userId. (A speaker anchor { "vertical": "user", "id": "user_42", "role": "speaker", "name": "Maria" } on a mention names them too.) To relay someone else's words under the user's scope, anchor that person as the speaker instead. Until a name is learned, workspace_status and /v1/users/:userId/profile say so — ask once, record it.