REST API Endpoints

For clients that don’t use MCP, HyperMemory exposes JSON endpoints under /api/v1/memory/* that invoke the same tool implementations as MCP for most (not all) tools.

Not available here: hm_upload_file, hm_list_files, and hm_list_orphans—use MCP, the hm CLI, or the dashboard file API below.

Authentication

Include one of:

API key: Authorization: Bearer hm_YOUR_KEY
OAuth token: Authorization: Bearer <supabase_jwt>

Base URL

https://api.hypermemory.io/api/v1/memory

Endpoints

Store

POST /api/v1/memory/store

Create a node. Maps to hm_store.

{
  "key": "fact_launch_date",
  "description": "Product launches on 2026-06-01",
  "node_type": "fact",
  "data": {"date": "2026-06-01"}
}

Recall

POST /api/v1/memory/recall

Hybrid search. Maps to hm_recall.

{
  "query": "launch date"
}

Update

POST /api/v1/memory/update

Update a node. Maps to hm_update.

{
  "key": "fact_launch_date",
  "description": "Product launch postponed to 2026-07-01",
  "data": {"date": "2026-07-01", "status": "postponed"}
}

Forget

POST /api/v1/memory/forget

Delete a node. Maps to hm_forget.

{
  "key": "fact_old_info",
  "cascade": true
}

Ingest

POST /api/v1/memory/ingest

Decompose text into entities. Maps to hm_ingest.

{
  "text": "Sarah joined as CTO in January...",
  "context": "Team update"
}

Overview

GET /api/v1/memory/overview

Graph stats. Maps to hm_get_overview.

Add relationships

POST /api/v1/memory/relationships

Create edges between existing nodes. Accepts a list of relationship objects, each with nodes (list of 2+ keys) and relationship (label string).

{
  "relationships": [
    {
      "nodes": ["person_alice", "project_phoenix"],
      "relationship": "Alice leads Project Phoenix"
    }
  ]
}

Get relationships

GET /api/v1/memory/relationships/{key}

List all edges connected to a specific node.

POST /api/v1/memory/find-related

Graph traversal. Maps to hm_find_related.

{
  "start_node": "person_alice",
  "query": "optional intent hint for strategy selection",
  "max_nodes": 50
}

Timeline

POST /api/v1/memory/timeline

Temporal recall. Maps to hm_timeline.

Timeline write

POST /api/v1/memory/timeline/write

Write a diary entry. Maps to hm_timeline_write.

Health

GET /api/v1/memory/health

Lightweight liveness check — returns {"status":"ok"} when the route is reachable (does not run full dependency checks).

Ready

GET /api/v1/memory/ready

Kubernetes-style readiness: runs internal hm_health dependency checks. Returns 503 if any check fails.

Export

GET /api/v1/memory/export

Export the full graph as JSON via internal hm_export_full (REST/CLI — not exposed as a public MCP tool).

Dashboard file API

Upload and list operations that correspond to MCP hm_upload_file / hm_list_files are exposed on the dashboard API (authenticated like the web app), not under /api/v1/memory:

Method	Path	Notes
POST	`https://api.hypermemory.io/api/files/upload`	Multipart form upload; requires dashboard session JWT
GET	`https://api.hypermemory.io/api/files`	List files for the active graph

Use these when integrating file storage over HTTP with a logged-in user. For agents and automation, prefer MCP (hm_upload_file with base64 content) or the hm CLI.