Documentation Index
Fetch the complete documentation index at: https://docs.maximem.ai/llms.txt
Use this file to discover all available pages before exploring further.
Where to start, depending on what you’re trying to do
- “I just want to try Synap without installing anything” — open the live playground and exercise the SDK from your browser.
- “I want to see Synap working in 10 minutes” — you’re on the right page. Stay here.
- “I want to wire Synap into a real FastAPI / Flask / Next.js / Django app” — head to Setup & Integration after you finish this page.
- “I want a complete end-to-end tutorial with an LLM, conversation routing, and graceful degradation” — go to First Integration. That tutorial assumes you’ve finished this Quickstart.
TL;DR — Hello World
If you already have an API key, this is everything you need to ingest one memory and read it back:hello_synap.py
Prerequisites
- Python 3.11 or later
- A Synap account (sign up at synap.maximem.ai)
piporpoetryfor package management
Install the SDK
Install the Synap SDK from PyPI:Verify the installation:
gRPC streaming is enabled by default — no extra install needed.
Set Up Your Client
A Client is your organization’s top-level account in Synap. Every instance belongs to a Client. You have two options:Create a new Client
- Log in to the Synap Dashboard
- Click Create Client, enter your organization name, and confirm
Skipping this step is not possible — every instance must belong to a Client. If you are unsure whether your organization already has one, check with your team before creating a new Client.
Create an Instance
An instance is an isolated memory environment for your agent. Each instance has its own storage, configuration, and scope hierarchy.
- In the Dashboard, navigate to Instances in the sidebar
- Click Create Instance
- Fill in the instance form:
- Name (required): A human-readable label, e.g.
"My First Agent" - Agent Type (required): Choose the type that best describes your agent (e.g.
B2B Customer Support,B2C Companion,Workflow Agent) - Description (optional): A short description of what this instance is for
- Use-Case Markdown (optional but recommended): Upload a
.mdfile describing your agent’s use case — see below
- Name (required): A human-readable label, e.g.

Use-Case Markdown
The Use-Case Markdown file tells Synap what your agent does, who it serves, and what it should remember. Synap uses it to generate an optimized Memory Architecture Configuration (MACA) for your instance — so the more detail you provide, the better your memory extraction and retrieval will be from day one.Click Download Template in the Create Instance form, fill in at least the three required sections (Agent Objective, Target Users, Task Examples), and upload the file (.md, .markdown, or .txt — max 512 KB) before clicking Create.For the full template and section-by-section guidance, see Writing a Use-Case Markdown File.Generate an API Key
- In the Dashboard, go to your newly created instance
- Open the API Keys section on the instance detail page
- Click Generate API Key
- Give it a label (e.g., “development”) and click Generate
- Copy the key immediately — it starts with
synap_
Initialize the SDK
Set your API key as an environment variable:Create a new Python file:That’s it. The SDK reads You should see
main.py
SYNAP_API_KEY from your environment automatically.Run the script:Synap SDK initialized successfully!On Windows,
python is sometimes intercepted by the Microsoft Store app execution alias and fails with "Python was not found". Use py (the Windows Python launcher) instead — it ships with every official Python installer. The same applies to pip: py -m pip install maximem-synap always works regardless of PATH configuration.Ingest Your First Memory
Now let’s send a conversation to Synap. The ingestion pipeline will automatically extract structured knowledge — facts, preferences, entities, and more.The SDK returns immediately with an ingestion ID. The pipeline processes the content asynchronously, extracting:
- Fact: User is located in San Francisco
- Preference: User loves warm weather
- Temporal event: User is planning a trip to Japan next month
- Entities: San Francisco, Japan (resolved and linked in the knowledge graph)
Ingestion is asynchronous by design. The
memories.create() call returns as soon as the content is accepted by Synap Cloud. Processing typically completes within a few seconds, but complex documents may take longer.Retrieve Context
Once memories are ingested and processed, you can retrieve relevant context. Synap searches across both vector and graph storage, ranks results by relevance, and respects scope boundaries.The ingestion above used Example output:You can now inject this context into your LLM’s system prompt or conversation history to create a personalized, context-aware experience.
Match the retrieval interface to the scope you ingested at. Synap has three scope-specific retrieval methods, and a memory is only returned through the one that matches how it was tagged:
A memory tagged with multiple identifiers is retrievable through any matching interface. Calling
| If you ingested with… | Retrieve via… |
|---|---|
user_id=... | sdk.user.context.fetch(user_id=...) |
customer_id=... (no user) | sdk.customer.context.fetch(customer_id=...) |
A conversation registered via record_message(...) | sdk.conversation.context.fetch(conversation_id=...) |
conversation.context.fetch with a brand-new, unregistered conversation_id returns empty results by design — there is no conversation row to anchor scope resolution. See Context Fetch for the full reference.user_id="user_123", so retrieve at user scope:Clean Up
Always shut down the SDK cleanly to flush any pending operations and release resources:The complete script looks like this:
main.py
Close the loop: retrieve → generate → ingest
A real agent doesn’t ingest in isolation. It fetches relevant context, calls the LLM with that context, and ingests the resulting turn back into memory. That is the atomic unit of using Synap. Here’s the minimum-viable version with OpenAI:For a fully-worked FastAPI + OpenAI app — including error handling, graceful degradation, and conversation routing — continue to the First Integration guide.
What’s next?
You’ve successfully ingested your first memory and retrieved context. Here’s where to go from here:Core Concepts
Understand the full Synap architecture — scopes, memory types, entity resolution, and the ingestion pipeline.
SDK Configuration
Configure the SDK for your production environment — timeouts, retries, logging, and credential management.
Memory Architecture
Learn how to configure what gets extracted, how it’s stored, and how retrieval ranking works.
Production Checklist
Security, performance, monitoring, and reliability best practices before going live.