API reference

The REST interface to the Lore Index. Every route runs against the same governed, row-level-scoped services as the MCP tools, so scoping, ranking, authorization, and the append-only audit trail behave identically through either door.

Base URL & authentication

Base URL: https://api.loreindex.ca/v1. Browser calls ride the same-origin proxy; agents call the API host directly.
Authentication: a bearer credential in the Authorization header. Two forms are accepted — an API key (lore_sk_…; legacy compass_sk_… keys remain valid), carrying read / propose / write scopes, or an MCP-issued OAuth 2.1 access token. Generate keys on the Connect page.
Machine-readable: the full contract is published as an OpenAPI 3.1 document at /v1/openapi.json. The catalog below is rendered from it.

Loading the reference from /v1/openapi.json…

The scoping model

Org, team, role, and user scopes — and how narrow-first resolution decides what an agent sees.

MCP endpoint & tools

POST /mcp over streamable HTTP, OAuth or Bearer keys, the five tools, the bootstrap pack, and the skill.

Rules & priorities

MUST vs SHOULD vs context — what each priority means and how it shapes the pack.

Versioning & auditing

Append-only version snapshots and audit events on every change, and how to read them.

Drafting & approval

The entry lifecycle — how humans draft and submit, and how agents propose for review.

Keyboard & command palette

Go-to navigation, the Ctrl/⌘-K command palette, and the single-key shortcuts on the lore list.