Skip to content

API

HTTP API

Know the local daemon surfaces that the CLI, MCP connector, plugin, and local tools call under the hood.

Qi-Xuan LuUpdated 5 min read

At a glance

01

The daemon listens locally on 127.0.0.1:7878 and owns the HTTP API.

02

Most users should use the plugin, MCP tools, or CLI; the HTTP API explains what those clients call underneath.

01

Local daemon boundary

origin-server is the local API boundary. Clients do not write the database directly; they ask the daemon to store, search, recall, distill, confirm, or diagnose memory.

The default bind address is 127.0.0.1:7878. That local-only default is part of the product boundary: one machine owns the memory layer unless you deliberately change daemon networking.

02

Main surfaces

The server README groups the public surfaces into health/status, setup, memory ingest/search, review, pages, and model/key setup.

These are implementation-level routes, not a stability promise for third-party SDKs. For normal use, prefer the CLI or MCP tools.

Daemon routes

/api/health
/api/status
/api/setup/status
/api/memory/store
/api/memory/search
/api/chat-context
/api/memory/list
/api/memory/confirm/{id}
/api/distill
/api/pages
/api/pages/search
/api/pages/{id}/sources
/api/on-device-model
/api/setup/anthropic-key

03

Client mapping

Claude Code slash commands and MCP tools are product workflows over these routes. /brief and context ask for a context bundle. /capture and capture store one durable memory. /distill triggers page synthesis. doctor checks daemon and setup state.

The CLI uses the same daemon for status, doctor, search, recall, store, list, model, key, MCP config, and spaces.

04

What not to build against yet

Origin is not positioning the HTTP API as a hosted memory SDK. It is primarily the local daemon contract for first-party clients and local tools.

If you need automation, start with the CLI or MCP connector. They carry the current product semantics better than hand-written HTTP calls.

05

Diagnostics

If a client cannot reach memory, check daemon health first with origin doctor or the MCP doctor tool. Then inspect whether the client is launching origin-mcp and whether port 7878 is occupied by an old daemon.

For bug reports, include the client, operating system, command you ran, expected result, actual result, and redacted doctor output.

Next

API Examples

Use the local daemon HTTP API from scripts when the CLI or MCP tools are not the right fit.

Read next