InsiderCat Developer Portal
Build agents, dashboards, alerts, notebooks, and research workflows with InsiderCat congressional trading, corporate insider trading, portfolio, sentiment, stock ownership, and market activity data. These developer resources collect the stable URLs agents and developers need for API keys, OpenAPI discovery, MCP setup, and support.
API keys
Sign in on the API page to generate a bearer token for authenticated data endpoints.
OpenAPI
Use the typed OpenAPI spec for operation IDs, parameters, response schemas, and function-calling integrations.
API reference
Read endpoint descriptions, filters, pagination, response shapes, and code samples.
MCP server
Connect AI assistants to InsiderCat tools through the Streamable HTTP MCP endpoint.
Getting started with InsiderCat API
Generate your API key on the API and MCP page, copy it once, and start calling InsiderCat endpoints directly with plain JSON over HTTPS.
InsiderCat MCP: Connect your AI assistant to InsiderCat
Connect InsiderCat data directly to your AI assistant in minutes. The MCP setup guide covers Claude Desktop, Cursor, VS Code, Windsurf, ChatGPT, and Gemini CLI, so you can ask things like "What are Congress members buying this week?" right from your assistant.
# InsiderCat Developer Portal Use InsiderCat developer resources to build agents, dashboards, research workflows, and monitoring jobs around U.S. congressional trading data, corporate insider filings, portfolio holdings, performance history, and stock-level ownership signals. ## Start here - Create or manage an API key from the API and MCP page after signing in. - Read the API reference for endpoint descriptions, query parameters, response schemas, and example calls. - Use the sandbox test token `ic_test_subscribed` in non-production environments where the server permits test-mode API auth. - Connect the MCP server at `/api/v1/mcp` with a bearer token when an AI assistant supports Streamable HTTP or `mcp-remote`. - Use `/api/v1/public/capabilities` without auth to discover public resources and integration entry points. - The API is versioned in the URL path (`/api/v1`). See the versioning and deprecation policy before building long-lived integrations. ## Links - [Developer portal](/developers) - [API and MCP overview](/api-mcp) - [API reference](/api-mcp/docs) - [Versioning and deprecation policy](/api-mcp/versioning) - [OpenAPI JSON](/openapi.json) - [OpenAPI YAML](/api/openapi.yaml) - [MCP manifest](/.well-known/mcp.json) - [llms.txt](/llms.txt)