# SEC Company Lookup — CIK, EIN & EDGAR Filings (`sourcerow/sec-company-lookup`) Actor

Resolve any US-listed or SEC-filing company to its official record — CIK, EIN, industry code, addresses, former names and filing history, from EDGAR, by ticker, CIK or name.

- **URL**: https://apify.com/sourcerow/sec-company-lookup.md
- **Developed by:** [SourceRow](https://apify.com/sourcerow) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 company resolveds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

Resolve a ticker, CIK or company name to its official SEC record: CIK, EIN,
industry code, addresses, former names and filing history. Data from EDGAR, the
SEC's own system.

### What it does

Every company that files with the US Securities and Exchange Commission has a
CIK, a ten-digit identifier that is the primary key for everything else the SEC
holds. This Actor turns the identifiers you have — tickers, CIKs, company names
— into that record.

One row per query, 34 fields on every row. Tickers and CIKs are exact lookups.
Names are resolved against EDGAR's complete name index.

### What you get

34 fields per row, including `cik`, `name`, `tickers`, `exchanges`, `ein`,
`sic`, `sic_description`, `entity_type`, `state_of_incorporation` and its
readable name, business and mailing addresses, `former_names_count`,
`filings_count`, `latest_filing` and `matched_by`.

The table view shows 15 of them; all 34 are in the JSON, CSV and Excel
downloads.

EDGAR uses its own codes for locations outside the US: `P7` is the Netherlands,
`L6` is Italy. Both the code and the readable name are returned, because the
codes look like US state abbreviations and are not.

### Input

| Field | Meaning |
|---|---|
| `tickers` | Stock tickers, for example `AAPL`. |
| `ciks` | CIK numbers, with or without leading zeros. |
| `names` | Company names to search. |
| `queriesText` | A pasted list of any of the above, one per line. |
| `maxCompanies` | Stop after this many. `0` removes the cap. |

```json
{
  "tickers": ["AAPL", "NVDA", "RACE"],
  "maxCompanies": 100
}
```

### Sample output

One complete record:

```json
{
  "query": "RACE",
  "matched_by": "ticker",
  "cik": "0001648416",
  "name": "Ferrari N.V.",
  "tickers": "RACE",
  "ein": null,
  "sic_description": "Motor Vehicles & Passenger Car Bodies",
  "state_of_incorporation": "P7",
  "state_of_incorporation_name": "Netherlands",
  "business_city": "MARANELLO",
  "business_state": "L6",
  "business_country": "Italy",
  "former_names_count": 1,
  "latest_filing": "2026-07-31",
  "issues": "no_ein"
}
```

### Pricing

| Event | Per 1,000 | Notes |
|---|---|---|
| Company resolved | $4.00 | Queries that find nothing are not charged |

There is no start fee and no per-row dataset fee. Searching by name costs
nothing extra, although it makes a run about four times longer: names are
resolved against EDGAR's complete name index, 40 MB and roughly a million
entries, fetched once per run and only when a name was actually supplied.

There is a faster way to turn a name into a CIK — EDGAR's full-text search.
This Actor does not use it, because it searches the contents of filings rather
than company names and would return the CIK of any company that merely mentions
the name.

### What it does not do

**US filers only.** EDGAR covers companies that file with the SEC. A European
company with no US listing is not in it. For those, use a national register.

**`filings_count` is not a total.** It counts the recent filing window EDGAR
returns, not a company's entire history. Treat it as an indicator of whether a
filer is active.

**No financial statements.** This returns the company record, not the numbers
inside the filings. Extracting figures from a 10-K is a different job.

**Foreign filers often have no EIN.** The field is `null` and `issues` reports
`no_ein`. It is a US tax identifier, and a foreign private issuer is not
required to have one.

**Names are not unique.** Companies share names across states. Rows found by
name deserve a check; `matched_by` states how each row was found.

### Notes

Send tickers or CIKs rather than names where available. They are exact and they
skip the 40 MB name index entirely, which is both faster and cheaper.

`former_names_count` above zero means the company has been renamed. That matters
when reconciling old records against current ones.

The SEC asks automated clients to identify themselves and limits requests to ten
per second. This Actor declares itself and stays below the limit.

### Support

Open the **Issues** tab with the exact query used and the `matched_by` and
`issues` values from the row.

### Licence and attribution

Company data from the US Securities and Exchange Commission EDGAR system. Works
of the US government are not subject to copyright under 17 U.S.C. 105. Anyone
can access and download this information for free.

# Actor input Schema

## `tickers` (type: `array`):

Ticker symbols, e.g. AAPL. Resolved instantly and exactly.

## `ciks` (type: `array`):

SEC Central Index Keys, with or without leading zeros.

## `names` (type: `array`):

Legal names. Using names makes the run fetch a 40 MB index once, so prefer tickers or CIKs when you have them.

## `queriesText` (type: `string`):

Paste a list here instead of the fields above. Mixed is fine: each line is sorted out automatically.

## `maxCompanies` (type: `integer`):

Stop after this many lookups. **0 removes the cap.**

## Actor input object example

```json
{
  "tickers": [
    "AAPL",
    "NVDA",
    "RACE"
  ],
  "ciks": [],
  "names": [],
  "maxCompanies": 100
}
```

# Actor output Schema

## `companies` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "tickers": [
        "AAPL",
        "NVDA",
        "RACE"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sourcerow/sec-company-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "tickers": [
        "AAPL",
        "NVDA",
        "RACE",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("sourcerow/sec-company-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "tickers": [
    "AAPL",
    "NVDA",
    "RACE"
  ]
}' |
apify call sourcerow/sec-company-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sourcerow/sec-company-lookup"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/a4XcpOVnbdd3hEhZt/builds/DD1WDlJ0enRQ8Stc4/openapi.json