> ## Documentation Index
> Fetch the complete documentation index at: https://docs.risos.co/llms.txt
> Use this file to discover all available pages before exploring further.

# RISOS developer platform

> Build on the same Products, intelligence, REST API, and MCP services used by RISOS.

RISOS exposes the same current business-intelligence model across the app, REST API, and MCP: **10 Research Products, six Signals, Projects, parent ResearchJobs, Living Deliverables, Ask, Explore, Monitor, Evidence, Entities, Opportunities, and Reports**.

Use REST when your application needs explicit HTTP resources and lifecycle control. Use MCP when an AI client should work with the same Workspace knowledge through a small, scoped tool surface.

> [card] [REST API](https://docs.risos.co/api/overview.md)
>
> Use scoped bearer keys with the current OpenAPI 3.1 contract.

> [card] [MCP](https://docs.risos.co/mcp/overview.md)
>
> Use six explicit tools, eight resource URIs/templates, and 10 Product prompts.

## Production endpoints

* REST base URL: `https://risos.co/api/rest`
* MCP endpoint: `https://risos.co/api/mcp`
* OpenAPI 3.1: `https://risos.co/openapi.yaml`

Create and revoke API keys from **RISOS → Developers**. Keys are Workspace-scoped and should be limited to the scopes each integration actually needs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.