API Reference
Multiplist exposes a REST API for headless integrations alongside the MCP endpoint. All requests use bearer tokens and return a consistent response envelope with requestId, code, message, and timing metadata.
# Base URL
https://multiplist.ai/api
# Authentication
All API requests require a bearer token. Generate one in Settings → API Keys inside the Multiplist app.
Authorization: Bearer mp_live_...
API keys use the mp_live_ prefix, are SHA-256 hashed at rest, and support scoped permissions.
# Scopes
| Scope | What it grants |
|---|---|
seeds:read | Read seeds across the vault |
seeds:write | Create, update, delete seeds |
sources:read | Read sources and their content |
sources:write | Create, update, delete sources |
skills:read | Read extraction skills |
skills:write | Create, update, delete skills |
recall:search | Run vault searches and request research briefs |
extract:run | Trigger extraction jobs |
# Rate limiting
Rate limits are tiered by plan:
- Starter — 60 req/min
- Growth — 300 req/min
- Pro — 1,000 req/min
Exceeding the limit returns HTTP 429 with a Retry-After header.
# Response envelope
Every response — success or error — uses the same shape:
{
"requestId": "req_abc123",
"code": "OK",
"message": "Request completed",
"data": { },
"timing": { "durationMs": 42 }
}
On errors, code is a machine-readable string (NOT_FOUND, RATE_LIMITED, UNAUTHORIZED, etc.) and data may contain structured error details.
# Context Capsule endpoint
GET /api/context
Designed to be wrapped cleanly as an MCP tool. Returns a scoped context snapshot — recent seeds, top tags, category stats — that external AI agents can consume without understanding the full vault schema.
For full MCP access, use the MCP endpoint at https://multiplist.ai/mcp instead.
# Related
- MCP Tools Reference — the MCP equivalent of these endpoints.
- Authentication & API Keys — generating keys, OAuth 2.1 with PKCE.