Skip to main content

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.

​
First Request Flows

This page exists to get you to one clean success quickly. Do one real workflow, keep the request metadata, and only then widen the scope.

​
Start in three steps

1

Check platform posture

Confirm health and readiness before you spend time debugging auth or payload shape.
2

Resolve one issuer you know

Start with a company such as AAPL so you can tell whether the answer looks obviously wrong.
3

Pull one structured workflow

Fetch a latest filing, extract a section, or pull the all-statements bundle. That is enough to prove the integration is alive.

​
API first request

curl "https://api.secapi.ai/healthz"

curl -H "x-api-key: $OMNI_DATASTREAM_API_KEY" \
  "https://api.secapi.ai/v1/entities/resolve?ticker=AAPL"

curl -H "x-api-key: $OMNI_DATASTREAM_API_KEY" \
  "https://api.secapi.ai/v1/statements/all?ticker=AAPL&period=annual&limit=1"

​
CLI first request

omni-sec entities resolve --ticker AAPL --json
omni-sec filings latest --ticker AAPL --form 10-K --json
omni-sec sections get --ticker AAPL --form 10-K --section item_1a --json

​
OMNI Agent CLI first request

omni auth login
omni chat "Resolve AAPL and summarize the latest 10-K risk factors."
omni sessions list

​
MCP first request

entities.resolve

Confirm the hosted MCP path can resolve a known issuer.

filings.latest

Pull the latest filing for a known form and issuer.

sections.get

Extract one section so you validate a useful workflow, not just connectivity.

​
Keep this support packet

Interface used

Note whether the request came from REST, SDK, CLI, or MCP.

Endpoint or tool

Record the literal endpoint or tool name.

Request metadata

Keep Request-Id, the expected result, and the actual result.