sec-api

Retrieve SEC filings and convert XBRL data to JSON via proxy endpoints.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/EternisAI/agent-sandbox --skill sec-api-eternisai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sec-api
Source: https://github.com/EternisAI/agent-sandbox/tree/main/skills/sec-api
Command: npx skills add https://github.com/EternisAI/agent-sandbox --skill sec-api-eternisai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve SEC filings and related data via HTTP requests to the backend SEC proxy. Use when users ask for SEC filings content, forms, sections, or filing-derived datasets.

Core Features & Use Cases

  • Proxy-backed retrieval of a wide range of filings and data via HTTP endpoints that map to forms and sections.
  • End-to-end workflow: ticker/CIK resolution → query → extractor → xbrl-to-json for structured statements.
  • Comprehensive form support: 8-K, 10-K, 10-Q, 13F, 13D/13G, S-1, 424B, DEF 14A, 144, 20-F, 6-K, N-PORT, Form D, and more.

Quick Start

Ask the SEC proxy to retrieve the latest Form 10-K for a company and extract its key sections.

Frequently Asked Questions about sec-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve SEC filings content without direct vendor API calls?

You can retrieve SEC filings content by routing HTTP requests through a backend SEC proxy. This approach maps standardized endpoints to specific forms and sections, avoiding direct vendor API calls while ensuring secure and reproducible data extraction.

What is the process for converting XBRL data from a 10-K filing into JSON?

Converting XBRL data into JSON involves an end-to-end workflow: resolve the ticker or CIK, query the 10-K filing, and apply the xbrl-to-json endpoint. This extracts structured statements and transforms them into standardized JSON format.

Can I extract ownership data from 13F and 13D SEC forms using a proxy?

Yes, you can extract ownership data from 13F and 13D/13G SEC forms using a proxy. The system supports comprehensive form retrieval, allowing you to query and extract institutional and activist ownership data through standardized HTTP endpoints.

Does the SEC proxy support S-1 and 424B4 filing extraction workflows?

Yes, the SEC proxy supports S-1 and 424B4 filing extraction workflows. It handles a wide range of forms including 8-K, 10-Q, DEF 14A, 144, 20-F, 6-K, N-PORT, and Form D, ensuring precise query constraints and URL-based extraction.

What are the limitations when enforcing precise query constraints for SEC filings?

Precise query constraints require accurate ticker or CIK resolution and exact URL-based extraction parameters. Limitations arise if query parameters are too broad or malformed, which can prevent the proxy from mapping to the correct forms and sections.

How do I resolve a ticker to a CIK before querying SEC filings?

To resolve a ticker to a CIK before querying SEC filings, use the mapping endpoint in the end-to-end workflow. This translates the ticker into the central index key required to enforce precise query constraints and retrieve the correct filings.