Core capabilities
- Ingest graph facts with
POST /api/GraphMemory/addv2, automatically extracting entities and relationships from structured JSON or text. - Query connected context using
POST /api/GraphMemory/searchv2to surface the most relevant paths for an assistant prompt. - Inspect the graph via
GET /api/GraphMemory/relationshipsto understand how nodes connect for a user or project. - Reset scope with
DELETE /api/GraphMemory/delete-all(Manager role) when you need to remove stale relationships.
Endpoint quick reference
| Use case | Endpoint | Method | Key inputs |
|---|---|---|---|
| Add entities and relationships | /api/GraphMemory/addv2 | POST | Body: data (JSON or text), optional user_id, project_id |
| Search graph for relevant paths | /api/GraphMemory/searchv2 | POST | Body: query, optional user_id, project_id, limit, threshold |
| List relationships for inspection | /api/GraphMemory/relationships | GET | Query params: userId, optional projectId, limit |
| Delete all relationships for a scope | /api/GraphMemory/delete-all | DELETE | Query params: userId, optional projectId (Manager key required) |
Before you start
- Generate an API key and choose the appropriate role. Contributor covers add/search; Manager is required for delete.
- Decide on scoping. Populate
user_idwhen graph data belongs to a specific resident or agent, andproject_idto isolate relationships per environment. - Structure your payloads. Consolidate related attributes into a JSON object under the
datafield so Recallio can detect entities and relations automatically.
Where to go next
Graph Memory Kick Start
Add your first graph payload and run a search with the v2 endpoints.
Graph Memory Deep Dive
Learn request schemas, tuning strategies, and maintenance workflows.

