SurrealDB Agent Memory is a memory and knowledge layer for AI agents - a horizontally scalable application tier in front of SurrealDB, which holds every durable record (graph, vector, document, relational, geospatial) with ACID writes, first-class provenance and trust, graph-resident traces, and tri-temporal belief history. It aims for memory that associates related ideas and keeps straight what was said, what is true now, and what used to be true - much like people do, but queryable and auditable in software.
Use this hub to go from principles to running code, then dive into the product sections (memory & knowledge, integrations, cookbooks, reference).
SurrealDB Agent Memory was developed under the project name Spectron, and that name is retained throughout the shipped interface: the spectron and spectrond binaries, the SPECTRON_* environment variables, the spectron_* MCP tool names, and SDK packages such as @surrealdb/spectron. The rule of thumb is that prose uses the product name and anything you type or configure uses spectron. These names will be renamed in a future release.
Architecture
What SurrealDB Agent Memory is built to do, what it is not, and how retrieval, traces, and time work:
Welcome and quickstarts
What is SurrealDB Agent Memory? - product positioning in one pass.
Why agentic memory? - where naive context and pure-vector shortcuts fail.
The accuracy promise - provenance, reconciliation, and auditability.
How it works - end-to-end path from a turn to stored, retrievable state.
Quickstarts
Agent Memory on SurrealDB Cloud - Cloud API vs data plane, organisation roles, and your first context in SurrealDB Studio.
Hosted quickstart - SurrealDB Agent Memory Cloud, API key, first remember and recall.
Embedded library - HTTP, MCP, and SDK integration surfaces.
Building with AI coding tools? Start with Agent guide (AGENTS.md) - copy it into Cursor rules or a project skill so your agent can learn SurrealDB Agent Memory without reading the full docs.
Mental model
How isolation, sessions, categories, and provenance fit together:
Unified substrate and authority - authoritative versus experiential streams in one graph.
Supersession, decay, and forget - how beliefs change, fade, and are removed
Product sections
Memory & knowledge - authoritative and experiential ingest, unified retrieval, reasoning, operations, tuning.
Integrations - SDKs, MCP, framework adapters.
Cookbooks - end-to-end patterns.
Reference - REST, management API, CLI, configuration, errors.