Skip to main content

​
Libraries & SDKs

Pick the integration that matches your runtime. Then prove it with one real entity lookup, one filing workflow, one structured result, and one traceable source-backed read before you move to production.

​
Choose Your Integration

JavaScript SDK

Best for TypeScript services, apps, scripts, and product integrations.

Python SDK

Best for research notebooks, data workflows, and backend services.

Go SDK

Best for lightweight backend services and command-line tools.

Rust REST Guide

Best for async and performance-sensitive services using direct HTTP calls.

Hosted MCP

Best for coding agents and MCP-aware runtimes that need grounded investor workflows.

SEC API CLI

Best when you want quick REST calls from the terminal without wiring up an SDK.

REST API

Best when you want exact HTTP control or your own runtime wrapper.
1

Set the API key

Export SECAPI_API_KEY first. Authentication failures are easier to debug before adding SDK, CLI, or MCP layers.
2

Verify one entity lookup

Confirm your integration can resolve a company or filer you already know, ideally through the identifier type you expect to use in production.
3

Verify one filing workflow and one semantic intelligence workflow

Pull a filing or statements bundle, then prove one-call market/macro/factor/intelligence output before you call the integration complete.
4

Preserve the metadata

Keep requestId, provenance, freshness, materialization metadata, and trace references in your logs or downstream artifacts.

​
Give this prompt to your agent

Copy this SEC API prompt for your agent.

​
SEC API CLI

The public CLI package name is @secapi/cli, with the secapi binary. Use it for quick REST calls from a terminal.

​
Installation

npm install -g @secapi/cli
Or install via Homebrew: 
brew tap secapi-ai/tap
brew install secapi

​
Usage

export SECAPI_API_KEY=your_key_here
secapi entities resolve --ticker AAPL --json
secapi filings search --ticker AAPL --form 10-K --limit 3 --json
secapi intelligence query --ticker AAPL --json
Prefer direct REST commands for production examples. Use hosted MCP for agent workflows that need tool discovery.

Auth and pricing

The auth model, version header, and plan state.

MCP workflows

Hosted MCP setup and agent-facing usage patterns.

API Reference

Exact endpoint behavior when you need wire-level precision.