Integration · Developer API

One memory layer, every interface

The MCP server is a thin wrapper over Kiomon's REST API. If your stack can't (or won't) run MCP, call the same memory operations directly over HTTP with a bearer token.

Authentication

All requests use a workspace API token. Create one in your dashboard and send it as Authorization: Bearer <token> alongside your workspace ID. Tokens are scoped to a workspace and revocable at any time.

Core endpoints

MethodPathWhat it does
POST /api/memories Draft or commit a memory (kind, title, body, workspace).
GET /api/search Hybrid search across memories and files in a workspace.
GET /api/workspaces List workspaces and their IDs.
GET /api/memories/:id Fetch a memory in full, with strength/stats and graph relations.
GET /api/memories/:id/graph Explore 1-hop graph relations (derived_from, supports, contradicts, …).
POST /api/memories/:id/manage Pin, archive, restore, forget, rate, approve, reject.

Endpoint paths mirror the MCP toolset one-to-one, so anything you build on REST keeps working if you later adopt MCP.

Use cases

  • Custom agent swarms and multi-agent pipelines that orchestrate memory centrally.
  • CI/CD hooks that commit project decisions to the graph on every merge.
  • Internal tools that surface searchable institutional knowledge.
  • Evals: script thousands of memory writes/reads for testing your prompts.

Get access

Create a free workspace to get your token, or reach out via contact for higher-rate plans and SLA-backed uptime.