API reference

Build against this sovereign group instance over REST, the Model Context Protocol (MCP), and the federation protocol. Every API surface derives identity server-side — client-supplied identity, owner, signer, or wallet is never trusted to bypass server derivation.

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 this instance federates through — the verified-principal trust rail to the global hub.

MCP & REST surface

This instance exposes a Model Context Protocol tool surface over POST /api/mcp (advertised by /.well-known/mcp and /llms.txt) plus the REST route tree under /api/**. Every tool call runs in an act-as context and is written to the MCP provenance log. See Auth models for how callers authenticate.

The full per-tool and per-endpoint reference that the hosted global app generates from source is not built on this sovereign instance yet; the endpoints above are the source of truth in the meantime.