Introduction
What Clous is, the response envelope, entity resolution, and the agent-native design of the SEC/EDGAR filings API.
Clous
Agent-native SEC data infrastructure. Clous is a SEC / EDGAR filings API built for AI agents. It resolves filings to canonical entities and serves them through a single, consistent JSON envelope — with confidence and freshness on every enriched field — over REST and (soon) a hosted MCP server.
All data served by Clous is derived from public SEC EDGAR filings. Clous is an independent service and is not affiliated with, endorsed by, or sponsored by the U.S. Securities and Exchange Commission.
What's live today
Clous is rolling out one filing form at a time. Live in production right now:
- Form ADV — investment advisers
GET /v1/advisers— list and filter registered investment advisersGET /v1/advisers/{crd}— full adviser profile by CRD number
- Base URL:
https://api.clous.ai - Auth:
Authorization: Bearer clous_live_...
Everything else — 13F, Form D, Form 4, N-PORT, N-CEN, webhooks, watchlists, company-list upload, AI filing briefings, and the hosted MCP server — is on the roadmap and clearly labeled as coming soon throughout these docs.
The response envelope
Every Clous endpoint returns the same top-level shape, so an agent only has to learn it once:
{
"data": [ /* records */ ],
"page": {
"limit": 25,
"next_cursor": "eyJvIjoyNX0",
"has_more": true
},
"as_of": "2026-06-11T00:00:00Z",
"source": "SEC EDGAR — Form ADV",
"query_echo": { "state": "NY", "aum_min": 1000000000 },
"warnings": []
}| Field | Meaning |
|---|---|
data | The array of records for this response. |
page | Cursor pagination state: limit, next_cursor, has_more. |
as_of | Freshness timestamp — when this view of the data was current. |
source | Human-readable provenance string for the underlying SEC data. |
query_echo | The normalized, typed parameters Clous actually applied. |
warnings | Non-fatal notes (e.g. a filter that matched nothing). |
Entity resolution
SEC filings are messy: the same adviser, fund, or company appears under slightly different names and identifiers across forms and years. Clous resolves filings to canonical entities so that a CRD number, a name, or another identifier maps to a single record you can reliably join on.
Enriched (non-source) fields are returned as structured values rather than bare facts, so an agent can reason about how much to trust them and how fresh they are.
Agent-native by design
- Typed parameters, no query DSL. Filters are explicit query params with types and bounds — easy for a model to fill in correctly.
- Cursor pagination. No offset math and no 10,000-result ceiling. See Pagination, Errors & Rate limits.
- Explicit errors. A small, stable set of error codes:
empty_result,entity_unresolved,not_found,invalid_param,rate_limited. - Source links + confidence. Records carry provenance so agents (and humans) can trace any value back to a filing.
- LLM-readable docs. A machine-readable
llms.txtandllms-full.txtindex the API for agents.