REST endpoints
Use familiar HTTP methods and JSON responses for financials, ratios, filings, peer comparisons, search, screening and workbook generation.
Use a model-agnostic MCP server or a plain REST API to bring structured EDGAR financials, ratios, peer comparisons, filing text and Excel-model generation into applications, scripts and agents.
Capabilities are grounded in the current EdgarStack product. Data availability depends on the issuer's SEC filings and reported XBRL tags.
Use familiar HTTP methods and JSON responses for financials, ratios, filings, peer comparisons, search, screening and workbook generation.
Expose research actions to MCP-compatible clients without coupling your product to a specific model provider.
Keep XBRL tags, period ends and accession references close to the data for downstream auditability.
Use an active EdgarStack subscription key in the X-API-Key header for REST requests.
Choose REST for application code or MCP when an AI client should call research tools directly.
EdgarStack supplies data access and research functions; you retain your application and model-provider choices.
Sample mode is immediate. Live requests use your EdgarStack API key.