-
Notifications
You must be signed in to change notification settings - Fork 0
http api
aniongithub edited this page May 19, 2026
·
1 revision
The HTTP server is the architecture/web-ui backend. Plain HTTP on 127.0.0.1:4242 by default. No TLS, no auth — it's a local-first tool.
| Method | Path | Returns |
|---|---|---|
GET |
/api/context |
{page_count, top_level_dirs, recent_pages} |
GET |
/api/pages |
List of pages, optional ?prefix=
|
GET |
/api/pages/{path...} |
Page with body, frontmatter, links, concepts/backlinks |
POST |
/api/pages |
Create page |
PUT |
/api/pages/{path...} |
Update page |
DELETE |
/api/pages/{path...} |
Delete page |
GET |
/api/search?q= |
FTS5 concepts/search |
GET |
/api/backlinks/{path...} |
Pages linking to this one |
GET |
/api/links |
All (source, target) edges — used by the architecture/web-ui
|
GET |
/api/settings |
Live config |
PUT |
/api/settings |
Update config |
Every HTTP endpoint maps to an equivalent architecture/mcp-server backed by the same architecture/wiki-engine method. Agents and humans see the same data, with the same semantics, at the same time.
graph LR
Browser -->|REST| HTTP
Agent -->|MCP stdio| MCP
HTTP --> Engine[Wiki engine]
MCP --> Engine
Engine --> DB[(SQLite)]
Engine --> FS[Files]