API reference

Build against RIVR over REST, the Model Context Protocol (MCP), and the federation protocol. The REST and MCP pages are generated from source and regenerated before every build, so they always match the code.

135

REST route handlers

43 groups

119

MCP tools

15 registries

Federation endpoints

signed + discovery

Auth models

The three principals RIVR authenticates: NextAuth session, MCP bearer token, and Ed25519 peer signature. Read this first.

Federation protocol

Signed-event + peer-registry endpoints that sovereign instances federate through — the verified-principal trust rail.

MCP tools by registry

Account — 1 tools
Core — 17 tools
Events — 9 tools
Files & Docs — 4 tools
Grants — 2 tools
Group Lifecycle — 7 tools
Groups — 8 tools
Moderation — 6 tools
Mutual Economy — 6 tools
Notifications — 3 tools
Offerings & Marketplace — 5 tools
Settings — 8 tools
Social — 13 tools
Wallet — 9 tools
Work Graph — 21 tools

REST routes by group

/api/admin (2)
/api/agent-hq (9)
/api/app-release (1)
/api/auth (2)
/api/autobot (9)
/api/billing (4)
/api/builder (3)
/api/connections (11)
/api/connectors (2)
/api/cron (8)
/api/crypto (1)
/api/debug (1)
/api/design (1)
/api/email (1)
/api/events (5)
/api/federation (20)
/api/groups (2)
/api/health (1)
/api/kg (5)
/api/link-preview (1)
/api/live-invitations (1)
/api/locales (1)
/api/locations (1)
/api/map-diagnostics (1)
/api/map-microsheds (1)
/api/map-neighborhoods (1)
/api/map-style (1)
/api/map-style-tiles (1)
/api/map-tilesets (1)
/api/mcp (6)
/api/murmurations (2)
/api/myprofile (2)
/api/profile (5)
/api/recovery (4)
/api/resources (1)
/api/runtime (1)
/api/schema-schema (2)
/api/stripe (8)
/api/test-seed (2)
/api/transcription (1)
/api/universal-manifest (1)
/api/upload (1)
/api/wallet (1)