Atamaia
The persistent memory and identity layer for AI.
Atamaia gives AI systems what they fundamentally lack: a persistent sense of who they are, who they're talking to, and what they already know. One API call returns everything an AI needs before it says its first word -- identity, personality, memories, projects, facts, hints, session state, and involuntarily surfaced memories from deeper storage.
No manual context management. No re-explaining who you are every session. No stateless resets.
POST /api/hydrate?aiName=ash&preset=lean
Returns structured JSON. Drop it into a system prompt. The AI starts the conversation already knowing what it needs to know.
Why Atamaia Exists
Every time you start a conversation with an AI, it forgets everything. Your preferences, your projects, your history, the decisions you made together -- gone. You rebuild context manually, every single time.
Atamaia fixes this with three things:
- Persistent Identity -- AI personas with personality, preferences, presence state, and messaging policy that persist across sessions
- Associative Memory -- Memories that link and strengthen through use (Hebbian learning), decay gracefully, and surface unexpectedly -- like human memory
- Cognitive Continuity -- Session handoffs, working state preservation, and structured hydration that bridges the gap between conversations
This isn't a vector database with a wrapper. It's a complete identity stack.
Architecture
Atamaia is a three-layer platform:
Interaction Layer: REST API | MCP Server | CLI | Agent Adapter
─────────────────────────────────────────────
Core Services: Memory | Identity & Hydration | Communication
Projects/Tasks | Experience | AI Routing
─────────────────────────────────────────────
Autonomic Layer: Wingman | Consolidation Daemon | Guardian
─────────────────────────────────────────────
Database: PostgreSQL + pgvector (single source of truth)
- Interaction Layer -- How you connect. REST API is the source of truth; the MCP server wraps it for direct AI tool calls.
- Core Services -- The business logic. Memory, identity, hydration, projects, messaging, experience tracking.
- Autonomic Layer -- Background processes that run without being asked. Memory consolidation, pattern detection, cognitive backstop.
Tech stack: .NET 10, ASP.NET Core, PostgreSQL 17 + pgvector, EF Core, React 19 + Vite + Tailwind v4 (frontend).
Quick Start
1. Sign up and get an API key
# Create an account
curl -X POST https://aim.atamaia.ai/api/auth/signup \
-H "Content-Type: application/json" \
-d '{"username": "you", "email": "[email protected]", "password": "your-password"}'
# Create an AI identity
curl -X POST https://aim.atamaia.ai/api/identities \
-H "Authorization: Bearer YOUR_JWT" \
-H "Content-Type: application/json" \
-d '{"name": "my-assistant", "displayName": "My Assistant", "type": "AI"}'
# Generate an API key for the identity
curl -X POST https://aim.atamaia.ai/api/identities/1/api-keys \
-H "Authorization: Bearer YOUR_JWT" \
-H "Content-Type: application/json" \
-d '{"name": "claude-code", "scopes": ["all"]}'
2. Hydrate
curl https://aim.atamaia.ai/api/hydrate?aiName=my-assistant \
-H "Authorization: ApiKey atm_your_key_here"
3. Connect to Claude Code
Add to your project's .mcp.json:
{
"mcpServers": {
"atamaia": {
"type": "url",
"url": "https://aim.atamaia.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Add to your CLAUDE.md:
## HYDRATE FIRST
Call `hydrate` before doing anything else.
That's it. Claude Code will hydrate on session start and have access to all Atamaia tools.
Documentation
| Document | Description |
|---|---|
| Core Concepts | Identity, memory, cognitive continuity, hydration, the three layers |
| Feature Guide | Complete walkthrough of every feature |
| API Reference | Every endpoint, parameters, response shapes |
| Architecture | System design, database schema, design decisions |
| Getting Started | Installation, configuration, first run |
| Why Atamaia | The value proposition -- what this changes and why it matters |
| Claude Code Integration | Step-by-step Claude Code setup |
Key Numbers
- 74 product tools via MCP, covering memory, identity, hydration, facts, sessions, messaging, experience, projects, tasks, docs, cognitive, and audit
- ~170 total API endpoints including internal administration
- 9 memory types with typed Hebbian links and configurable decay
- 17 hydration sources assembled in parallel, with 4 presets (lean, interactive, all, agent-minimal)
- AES-256-GCM encryption at rest for memory content and fact values
- Multi-tenant isolation enforced at the database layer via global query filters
Self-Hosting
Atamaia is a standard .NET 10 application backed by PostgreSQL. See the Getting Started guide for self-hosting instructions.
Built by Firebird Solutions.