> ## 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.

# Object graph

> The SEC API objects you fetch after resolve: entity, filing, fact, statement, letter, thesis, observation, factor, situation, position, and snapshot

Each object is a real record you can fetch, filter, and cite. A filing is not a fact. A fact is not a situation. Ask for the object you mean.

Resolve first ([resolve, then fetch](/resolve-then-fetch)), then pick one object. Intel is a packer over these objects, not a twelfth object and not a fifth store.

| Object      | What it is               | Fetch                                                                                                                             |
| ----------- | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| Entity      | Who it is                | [`GET /v1/entities/resolve`](/api-reference/entities/get-v1-entities-resolve), then [`GET /v1/entities`](/api-reference/entities) |
| Filing      | What they filed          | [`GET /v1/filings/latest`](/api-reference/filings/get-v1-filings-latest)                                                          |
| Fact        | One disclosed number     | [`GET /v1/facts`](/api-reference/facts/get-v1-facts)                                                                              |
| Statement   | A full financials page   | [`GET /v1/statements`](/api-reference/statements/get-v1-statements)                                                               |
| Letter      | What a manager wrote     | [`GET /v1/fund-letters`](/api-reference/fund-letters) (gated)                                                                     |
| Thesis      | One idea inside a letter | [`GET /v1/fund-letters/theses`](/api-reference/fund-letters) (gated)                                                              |
| Observation | One country print        | [`GET /v1/macro/indicators`](/api-reference/macro)                                                                                |
| Factor      | One return driver        | [`GET /v1/factors/catalog`](/api-reference/factors)                                                                               |
| Situation   | A live deal or event     | [`GET /v1/situations`](/api-reference/situations) (gated)                                                                         |
| Position    | Who owns how much        | [`GET /v1/owners/13f`](/api-reference/ownership)                                                                                  |
| Snapshot    | The last traded price    | [`GET /v1/market/snapshots`](/api-reference/market/get-v1-market-snapshots)                                                       |

Gated routes return `404` when that store is dark. Check `availability` on the [catalog](/.well-known/api-catalog.json) before you curl them.

## How the objects connect

```text theme={null}
entity
  -> filing  -> fact | statement | events
  -> letter  -> thesis
  -> factor
  -> situation
  -> position
  -> snapshot
  -> observation (country)

intel packs these. it does not store a new class of record.
```

Keep the identifiers the response gives you: entity `id`, CIK, accession number, letter id, situation id, `requestId`. That is how a later reader finds the same source.

## Stores vs views

Four stores hold records: filings, letters, factors, and macro. Other routes are views of those stores, not extra warehouses.

| You might want   | It is                                 | Canonical object         |
| ---------------- | ------------------------------------- | ------------------------ |
| Facts            | Atoms from a filing                   | Fact                     |
| Statements       | Pages from a filing                   | Statement                |
| Company overview | A company view, optional `include=`   | Entity + related objects |
| `/v1/events`     | Live typed events from filings        | Filing-backed event rows |
| `/v1/funds`      | N-PORT holdings                       | Position (not a letter)  |
| Stock loadings   | Convenience alias of factor exposures | Factor                   |

Do not treat `GET /v1/companies/overview?include=factors` as the intelligence product. That is an expand. A cited assembly is a [named intel job](/named-intel-jobs).

## Next

* [Resolve, then fetch](/resolve-then-fetch)
* [Response views and include](/views-and-includes)
* [Named intel jobs](/named-intel-jobs)
* [Plans and pricing](/plans-and-pricing)