Skip to main content

Prerequisites

Before getting your API key, configure your Memory Space Scenario Mode. It influences how memories are extracted and consolidated. Learn more in the Space Scenario Mode guide.
1

Install the SDK

2

Create a client

Never commit API keys to version control. Use environment variables in production.
3

Add memories

Store conversation messages into your Memory Space. Each message’s sender_id is the user the memory belongs to.
The call returns status: "queued" and extraction runs in the background on its own — you do not have to trigger it. Give it a few seconds before you read the memories back.For a deterministic write — in a test, say — pass async_mode=False. The call then returns the engine’s own result ("accumulated" or "extracted") instead of an acknowledgement.
client.flush(session_id) forces extraction for a session that is still open, but it only sees messages that have already landed. Called immediately after a default (queued) add it returns "no_extraction" — nothing has arrived yet. That is not an error, and the extraction still happens on its own moments later.
4

Retrieve memories

Fetch a user’s stored memories by type.
5

Search memories

Find relevant memories using vector, keyword, hybrid, or agentic retrieval.
The vector index lags extraction by a few seconds. To read back something you just wrote, use client.get(...) — it reads the stored memories directly and sees them as soon as they are extracted.

What’s Next?

Core Concepts

Understand the memory lifecycle, memory types, and how EverOS processes your data.

API Reference

Explore the full API with detailed parameter docs, request/response examples, and error codes.

Knowledge Bases

Ingest documents into a searchable topic library and query it alongside memory.

Console

Monitor quota usage, track API calls, and manage keys in the EverOS Console.
Need help? Join our community.