# SEC EDGAR Filing Catalog (`bb-tradetec/sec-edgar-filing-catalog`) Actor

Find confirmed public EDGAR filings by CIK, accession, or bounded date window as canonical records with archive provenance.

- **URL**: https://apify.com/bb-tradetec/sec-edgar-filing-catalog.md
- **Developed by:** [BB](https://apify.com/bb-tradetec) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.05 / 1,000 filing records

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/platform/actors/running/actors-in-store#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

## SEC EDGAR Filing Catalog

`sec-edgar-filing-catalog` enumerates public SEC EDGAR filings as canonical `secFiling` records. It is for agents and applications needing bounded, provenance-backed filing metadata—not filing prose, advice, ticker resolution, or a sibling-Actor workflow.

Local release status is `READY_FOR_BETA`; the Actor is not deployed and its
Cloud lifecycle status remains `planned`.

### Use it for

- Filing discovery by exact CIK.
- Direct resolution of an exact SEC accession.
- A bounded `all` filed-date window (at most 31 days).
- Monitoring after a prior opaque cursor, where the source can prove a safe continuation.

Use C01 to resolve a ticker or company name first. Use C03/C04 for filing documents or content, and a form-specific Actor for semantic interpretation.

### Input and output

The executable schemas in [`.actor`](./.actor/) are authoritative. A minimal input is in [`.actor/examples/input-minimal.json`](./.actor/examples/input-minimal.json). Each query has a unique `requestId` and one identifier strategy: `cik`, exact `accession`, or `all` with `filedFrom` and `filedTo`.

A CIK query without filed dates starts with a cursor-anchored rolling ten-year window. When older SEC history exists, `SUMMARY.truncation.cursor` continues into the next older window without changing the query. Explicit CIK filed-date and report-period ranges require both bounds and may span at most ten years.

Hard limits are 20 queries, 10,000 output records, 1,000 SEC source requests, and 50 MiB. Validation occurs before the adapter constructs an SEC client. Input order does not change the stable natural record ID `sec-filing:<accession>`; matching request IDs are sorted and deduplicated.

The default Dataset contains only confirmed `secFiling` records. `SUMMARY` and `ERRORS` are always written to the default Key-Value Store for empty, partial, and global failed runs as applicable. Output links expose all three locations. Examples: [record](./.actor/examples/output-success.json), [empty summary](./.actor/examples/output-empty.json), and [partial summary](./.actor/examples/summary-partial.json).

### Sources and boundaries

Only the five inventoried public SEC paths are used: filing index, Company Submissions, Daily Index, Full Index, and Latest Filings. Every emitted record has confirmed SEC archive provenance. The Actor never accepts a user URL, contacts a third-party source, parses filing prose, resolves a ticker, or runs another Actor.

### Pricing status

The local planned pay-per-event configuration has **no events**. The adapter therefore makes no charge calls and records `chargedEvents: {}` plus exact `0.000000` estimated and maximum user charge in every `SUMMARY`. This is not a Cloud pricing configuration and does not authorize publication or a price change.

### Local development

Python 3.13 is required. `apify==2.7.3` is exactly pinned with its resolved runtime closure in `requirements.lock`; development tools are pinned in `requirements-dev.lock`. The Docker entry point is `python -m sec_edgar_filing_catalog`.

```bash
PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src:vendor \
  ../sec-8k-event-normalizer/.venv/bin/python -m pytest
apify validate-schema
```

The checked-in 8-K virtual environment is a read-only local runner, not an installation target. See [LOCKING.md](./LOCKING.md), [docs/product/interface.md](./docs/product/interface.md), and [docs/product/store-listing.md](./docs/product/store-listing.md).

# Actor input Schema

## `queries` (type: `array`):

One to twenty exact CIK, exact accession, or bounded all-filings queries. A CIK without filed dates starts with a rolling ten-year window.

## `maxResults` (type: `integer`):

Hard cap after global accession deduplication.

## `maxSourceRequests` (type: `integer`):

Hard run-wide SEC source request ceiling.

## `maxDownloadBytes` (type: `integer`):

Hard run-wide SEC download byte ceiling.

## `outputSchemaVersion` (type: `string`):

The supported public output contract version.

## `outputMode` (type: `string`):

Full or compact metadata representation.

## `cursor` (type: `string`):

Opaque older-history or monitoring cursor returned by a prior SUMMARY; never edit it.

## Actor input object example

```json
{
  "maxResults": 100,
  "maxSourceRequests": 100,
  "maxDownloadBytes": 26214400,
  "outputSchemaVersion": "1.0",
  "outputMode": "full"
}
```

# Actor output Schema

## `filings` (type: `string`):

Default dataset. One confirmed secFiling record per accession; local planned pricing has no charge event.

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

SUMMARY is written for successful, empty, partial, and failed runs.

## `errors` (type: `string`):

ERRORS contains bounded structured errors and is never chargeable.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("bb-tradetec/sec-edgar-filing-catalog").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("bb-tradetec/sec-edgar-filing-catalog").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 '{}' |
apify call bb-tradetec/sec-edgar-filing-catalog --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bb-tradetec/sec-edgar-filing-catalog"
        }
    }
}

```

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/rkHupZdYbQoab1evF/builds/qTegAJdQVVyrVh8Em/openapi.json