# SEC Section 16 Ownership (`bb-tradetec/sec-section16-ownership-normalizer`) Actor

Normalize public Forms 3, 4, and 5 into individual holdings, transactions, owner relationships, and amendment links.

- **URL**: https://apify.com/bb-tradetec/sec-section16-ownership-normalizer.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 section 16 entries

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 Section 16 Ownership Normalizer

Planned SEC Complete Data Suite actor for public Forms 3, 4, and 5. It emits one
provenance-backed Section 16 holding, transaction, or owner-relationship entry
per XML table path, without netting positions or inferring market value.

Package 4 adds a native Apify lifecycle adapter around the bounded, stateless
source layer: it validates input before constructing an HTTP client, writes
only validated entries to the default Dataset, and always persists validated
`SUMMARY` and sanitized `ERRORS` records to the default Key-Value Store. It
does not make charge calls. Package 3 added the source layer itself: exact
identifier resolution, SEC archive attachment location, Insider Transactions
bulk-dataset discovery, streaming HTTPX download accounting, the shared
eight-RPS limiter, bounded retries and allowlisted redirects, and a scope-bound
cursor. Runtime requests remain limited to the two public SEC sources in the
source inventory. Ticker/company-name resolution is pure and receives an
already obtained official catalog; it does not add a third runtime endpoint.

The XML parser continues to receive caller-provided `ParseContext`; IDs, XML
anchors, reconciliation diagnostics, amendment links, partial failures, and
global deduplication remain deterministic. The adapter is covered only by
offline fake Actor/service lifecycle tests; no Cloud action or live SEC request
has been made.

### Local development

Python 3.13 is required. Runtime and development dependencies are exact-pinned
in `requirements.lock` and `requirements-dev.lock`. The container entry point
is `python -m sec_section16_ownership_normalizer`.

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

# Actor input Schema

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

One to twenty exact Section 16 lookup requests.

## `filedFrom` (type: `string`):

Inclusive filing-date lower bound.

## `filedTo` (type: `string`):

Inclusive filing-date upper bound.

## `includeAmendments` (type: `boolean`):

Include Forms 3/A, 4/A and 5/A.

## `includeFootnotes` (type: `boolean`):

Retain referenced footnote IDs.

## `maxFilings` (type: `integer`):

Run-wide source filing ceiling.

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

Run-wide normalized entry ceiling.

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

Hard SEC request ceiling.

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

Hard cumulative SEC download-byte ceiling.

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

Requested public output schema.

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

Full or compact public output mode.

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

Opaque stateless continuation cursor.

## Actor input object example

```json
{
  "includeAmendments": true,
  "includeFootnotes": true,
  "maxFilings": 50,
  "maxResults": 1000,
  "maxSourceRequests": 200,
  "maxDownloadBytes": 52428800,
  "outputSchemaVersion": "1.0",
  "outputMode": "full"
}
```

# Actor output Schema

## `entries` (type: `string`):

Default dataset; one unnetted Section 16 XML table row or owner relationship per entry.

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

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

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

ERRORS is not a result dataset item.

# 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-section16-ownership-normalizer").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-section16-ownership-normalizer").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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-section16-ownership-normalizer --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=bb-tradetec/sec-section16-ownership-normalizer",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/FHlv6wrfa6sg8tbHZ/builds/2ujStcb81L3B51Hrr/openapi.json