Documentation Index
Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
Use this file to discover all available pages before exploring further.
Libraries & SDKs
Pick the surface 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 call the integration done.
Choose your surface
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 strongly typed API wrappers.
Rust SDK
Best for async and performance-sensitive services.
Hosted MCP
Best for coding agents and MCP-aware runtimes that need grounded investor workflows.
OMNI Agent CLI
Best when you want agent workflows from the terminal without opening a browser or wiring up an SDK.
REST API
Best when you want exact HTTP control or your own runtime wrapper.
Recommended sequence
Set the API key
Export
OMNI_DATASTREAM_API_KEY first. Every other surface will fail in ways that look less clear if auth is not in place.Verify one entity lookup
Confirm the surface can resolve a company or filer you already know, ideally through the identifier type you expect to use in production.
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.
Give this prompt to your agent
OMNI Agent CLI
The CLI connects to the same agent backend as OMNI Pulse. It speaks the same WebSocket protocol, uses the same auth token, and has access to the same skills, tools, and data.Installation
Usage
Read next
Auth and pricing
The auth model, version header, and plan posture.
MCP workflows
Hosted MCP setup and agent-facing usage patterns.
API Reference
Exact endpoint behavior when you need wire-level precision.