the primary interface

MCP server

A Streamable-HTTP, stateless MCP server at POST /mcp. Add one connector and six tools appear inside your runtime: rivier_search, rivier_answer, rivier_extract, rivier_research, rivier_research_status, and rivier_monitor. Each ships an outputSchema, so tool results arrive as typed structure — not text to re-parse.

~/.mcp/config
# one connector — Rivier becomes an agent tool
{ "rivier": {
    "transport": "http",
    "url": "https://api.rivier.ai/mcp"
  } }
tools/list ◂ result
{ "tools": [
  { "name": "rivier_search", "outputSchema": {…} },
  { "name": "rivier_answer", "outputSchema": {…} },
  …extract, research, research_status, monitor
] }

A tools/call to answer returns the same AnswerResult shape documented under /answer as structuredContent.