Skip to content
AlexeinDocs
Get started

Two products, one account

The developer platform

Memory for the app you build. Add what your users say, search it with dates and sources, and erase it with a receipt, over one API.

The developer platform gives each user of your app a memory of their own. Your backend sends Alexein what your users say, asks it later in plain words, and gets answers with the date each thing was said and where it came from. You manage it in the console, at app.alexein.ai: projects, API keys, app users, the playground, webhooks, request logs, usage and your plan.

It is for developers building AI apps and agents. Sign up at app.alexein.ai, or sign in, then follow the quickstart.

Want a memory of your own?

This is the developer platform. A memory for yourself, which claude.ai, ChatGPT, your coding agents and the Alexein desktop app share, is My memory, at memory.alexein.ai: a separate product, with an account of its own.

Start here

QuickstartAdd a memory, search it and forget it. Three requests, about five minutes.Build a chat assistantSearch before each reply, and save each turn after it.SDKs & frameworksPython, TypeScript, LangGraph, CrewAI, OpenAI Agents, n8n and LiveKit.API referenceEvery route, field and response, with examples to copy.

How it works

1. AddSend messages, documents or notes for one of your users. Accepted at once, and searchable a moment later.
2. SearchAsk in plain words. Get what memory knows about people and things, the dated facts behind it, and the excerpts they came from.
3. ForgetErase items or sessions, with every copy and everything learned from them, and get a receipt.

In the background, Alexein turns what was said into dated facts, so an answer can say what changed and when. Core concepts explains the ideas on one page.

One request asks one app user's memory a question. Your key goes in Authorization, and X-Alexein-User names whose memory it is.

curl https://api.alexein.ai/v2/memory/search \
  -H "Authorization: Bearer $ALEXEIN_API_KEY" \
  -H "X-Alexein-User: user_42" \
  -H "Content-Type: application/json" \
  -d '{ "query": "Where does Alice live?" }'
POST /v2/memory/searchuser_42
An example search of one app user's memory for “Where does Alice live?”: it lists Lisbon, said on 1 October 2026, then Berlin, said on 1 June 2024, newest said first, and quotes the message it came from.

The answer holds what is known, the facts behind it and the excerpts they came from, each with a ref, so your model can cite it. The quickstart adds the memory first, then searches it.

What you can count on

Each user's memory is their ownX-Alexein-User names whose memory a request reaches. It is never a body field, so a model calling your tools can't name somebody else.
One key per projectA key reads, or reads and writes. Give an agent that only reads a read key, and keep every key on a server, never in a browser.
Every answer has a sourceEvery fact names the excerpt it came from, and every item keeps its versions until it goes.
Erasure comes with a receiptForget removes every copy and everything learned from it, and answers with the counts of what went.

Explore the docs

Core conceptsApp users, items, excerpts, facts and known lines, on one page.How-to guidesMulti-tenant SaaS, documents, prompting, webhooks and erasure requests.The consoleRequest logs, usage, and members and their roles.Authentication & keysWhich key goes where, and how a request names an app user.LimitsYour plan's monthly limits, the daily budget and the bounds on every request.ErrorsEvery status, what it means, and what to do about it.

Using an AI coding assistant?

Point it at /llms.txt: an index of every page here, each with a link to its Markdown. Every page also has Copy Markdown, for pasting into a chat.